Skills / Run It in Production / Change & delivery
Run It in Production

Data Migration & Cutover

Scopes the migration, plans the mapping, and runs cutover through three gates: correctness, rollback and decommission.

Private skill · shared by invitation · How access works

Illustrative output of Data Migration & Cutover: Scopes the migration, plans the mapping, and runs cutover through three gates: correctness, rollback and decommission.
Illustrative output with sample data.
The challenge

The new system went live two years ago. The old one is still running.

No definition of correct

Go-live happens before anyone agreed what a good load looks like.

Rollback with no owner

Nobody holds the decision, or the deadline, at 3am.

Legacy never retires

Dual running becomes permanent.

Rehearsals cut

A fast, complete-looking plan tempts teams to skip rehearsal.

How it works

From first question to finished output.

Scope on four factors

Quantity is sources × fields, not rows. Then choose Big Bang or incremental.

Profile and map

Profile the source first, then map target to source, field by field.

Gate correctness

Counts, control totals and business assertions, agreed before go-live.

Cut over

A runbook with owners and clock times, a rollback trigger and a decommission milestone.

What you get

  • Four-factor scoping and the Big Bang versus incremental decision
  • Three-layer correctness gate: counts, control totals, business assertions
  • Cutover runbook, rollback trigger and decommission milestone

What goes in

Source and target inventories, profiling output, business downtime tolerance.

Time to answer

As a consulting engagement10 weeks3 people · 30 consultant-weeks
Running the skill2–4 hoursone sitting, start to finished output

What it still needs from you

The rollback call at 3am, and the politics of switching the old system off.

Also in Run It in Production

See where this fits in the sequence →

See Data Migration & Cutover in action.

Thirty minutes with Harveer, on your own data problem.