Preserve the application identity.
Keep your existing primary key and map it to the returned token. The migration guide describes a parallel table that holds both values.
CUSTOMER DATABASES
Keep the application.
Move the customer profiles.
Introduce Databunker Pro through a staged migration: backfill records, store returned references, update application paths, and verify before cutting over.
BACKFILL → REFERENCE → INTEGRATE → VERIFY
Every change has a place in the plan.
The application database stays in your stack. Access to migrated profiles moves through the vault API.
Application databaseSAMPLE PROFILE
id1024nameAlex Morganemail[email protected]user_tokenNot stored yetYour migration code
Migration worker
Backfill profiles.
Map returned references.
Databunker Pro
Encrypted customer profile
The migration worker creates a vault record and receives its reference.
Customer #1024name · email · profile fields
a21fa1d3-8b4c-…Vault → encrypted record databaseAttached files → file backend
Your application
Existing database reads
Credential: authorized vault API callsHistorical copies still exist.Original fields, old tables, logs, replicas, and backups are not erased by storing a vault token.
The migration worker and application call the vault API. The table illustrates an intermediate migration state: original fields remain until you deliberately cut over and clean up.
01INTERACTIVE EXAMPLE
Backfill into the vault.
Export the profiles selected for migration and create their vault records. Preserve the existing application identifier so returned tokens can be mapped correctly.
Illustrative migration using sample data. The demonstration does not connect to, modify, or delete a database.
Original profileReturned referenceAPI access credential
Change the application paths.
Backfill alone does not change what your application reads. Update the relevant reads and writes, account for new records, and exercise the full workflow.
Separate verification from cleanup.
Reconcile the result before cutting over. Then apply a documented plan to old tables and historical copies, with a rollback approach appropriate to each stage.
BUILD THE FIRST WORKFLOW
Prove the pattern on one service.
Pick a bounded profile flow and work through it end to end. Databunker’s migration guide covers backfill, verification, application changes, and the table swap.
Read the SQL migration guide ↗- Prepare the vault and mapping.Confirm capacity, credentials, application identifiers, and a backup of the source.
- Backfill and reconcile.Create vault records in batches, store returned references, and resolve errors.
- Exercise new reads and writes.Run the application with the new paths before performing the cutover.
- Cut over deliberately.Verify schema relationships and rollback options; schedule the remaining cleanup separately.
Explore another workflow
Explore KYC records and files Bring the documents along.
LESS SPRAWL. MORE CONTROL.
Give sensitive data
a proper home.
Walk through your architecture with a Databunker engineer.
Find the right place to start.