05 — Database migration
Move the data. Keep the proof.
A migration is finished when the applications agree with the new store, the differences are explained, and you know the minute you would go back.
Come with the database you are afraid to touch, and the application that quietly depends on it.
Scroll and this stack opens.
Watch it happen
What we offer
-
01
Readiness
Schemas, jobs, copies, and the applications that read them. Including the report someone runs from a laptop.
-
02
A mapped transfer
Fields, types, and the rows that should be archived instead of moved. Decisions are written down before the first rehearsal.
-
03
Validation you can show
Counts, samples, and the exceptions. Not a green checkbox. A list a sceptical operator can check.
-
04
A rollback you have tried
A named point of return, rehearsed. If the new store misbehaves, the path back is a procedure, not a hope.
How a migration is run
-
01
Inventory what must move.
Databases, scheduled jobs, downstream readers, and stale copies. We mark what is live, what is archive, and what nobody can explain.
You see: a dependency map. -
02
Map the fields and the leftovers.
What converts, what is dropped, and what is kept only for audit. The awkward columns get a decision, not a surprise on cutover night.
You see: a field map and an archive rule. -
03
Rehearse and reconcile.
We run the transfer, compare counts and samples, and fix the differences. A second rehearsal proves the fix. Where the business needs it, we plan a short dual-run.
You see: a reconciliation, with the gaps closed. -
04
Cut over, with a way back.
A window, a checklist, and a point where you return to the old store if the checks fail. After that, the readers point at the new one.
You see: a cutover note and a tested rollback.
What the migration is made of
-
Dependency maps
Jobs, applications, and people who query the data directly. The hidden reader is usually the risk.
-
Reconciliation
Row counts, key samples, and totals that must match. Exceptions are listed, not averaged away.
-
Rehearsal
The transfer is run before the night it matters. Timing and failures show up while you can still change the plan.
-
A written rollback
The condition that sends you back, who calls it, and the steps. Practiced once, so the first time is not the incident.