← michaelnocito.github.io

The Data Migration Toolkit

You start the migration with the paperwork already designed, and the reconciliation catches a silent multiply before the client finds it.

Read the toolkit (PDF) 9 pages · built from a worked engagement

The idea it is built on

Every argument late in a migration is about something agreed early. Someone says the exclusion list never covered those records. Someone else remembers the field map differently. Nobody can produce the moment it was decided.

So the work is split into eight stages, and each one ends at a gate: a short written sign-off naming what was agreed, who agreed it, and where the evidence sits. A stage does not open until the one before it is signed. That single rule is what turns a dispute in month five into a lookup instead of an argument.

Kickoff and scope. Gate: the scope is signed. Nothing else starts until it exists.
Profile the source. Gate: the profiling report is accepted, so you both agree what the data really looks like.
Map the fields. Gate: the mapping is signed off and the version is frozen.
Clean and de-dupe. Gate: the exception list is closed, or formally accepted as is.
The dry run. Gate: a clean reconciliation in the sandbox, on real volume.
User acceptance testing. Gate: the client signs off. The people who use the data confirm it is right.
Freeze, cutover and bridge. Gate: go-live accepted, and the work created mid-migration is accounted for.
Hypercare and close. Gate: the project is closed and the handoff is accepted.

What is in the workbook

Tab	What it does
Migration Plan	56 tasks across the eight stages, with predecessors and real dates.
Overview	Percent complete per stage, rolled up from the plan.
Action Log	Open items, owner, due date, and how each was closed.
Change Requests	Scope changes with the decision and its date.
Field Mapping	Source field, target field, transform rule, and who approved it.
Exception Sheet	Records that did not load, why, and what was done about them.
Reconciliation	Row counts and control totals, source against target.
Linkage Check	Whether parent and child records still point at each other.
Gate Sign-off	The eight gates: what was signed, by whom, when, and the evidence.

Owners are roles, not names, so a team swaps in its own people. The plan tab imports into Smartsheet: header on row 1, no merged cells, real dates.

Everything in it is invented

The worked example follows a fictional provider, Northwind Care Services, moving off a fictional platform mid-cutover. Every client, system, identifier and number is made up. No real engagement is described here.

Who made it

I am Michael Nocito. I spent about ten years as an implementation and data migration analyst, most recently as a Senior Implementation Analyst at RLDatix, moving client data onto contract and compliance platforms. This is the set of sheets I kept rebuilding from scratch on every engagement, built once and properly.

More of my work is at michaelnocito.github.io, and the eight stages are each written up in full in the Analyst Prep Kit.

See the whole thing

One Migration, Start to Finish walks a single engagement day by day: the email that closed each gate, the four change requests, and what it cost to say no to one of them. It is the closest thing here to watching me run a job.

The Python that generates both workbooks and this PDF is public at github.com/michaelnocito/migration-toolkit. Every gate date is read off the plan rather than typed a second time, which is the constraint the whole build is designed around.