Migration That Doesn't Break

It's the Thursday before cutover. You're "90% done." You've been 90% done for two weeks.

The object tracker says most records mapped. The field mapping doc says most transformations are defined. The project plan says you're on schedule — but the project plan hasn't been updated since the stakeholder meeting where everyone nodded and no one mentioned the 47 validation rules that haven't been tested yet.

You know the pattern. Migrations don't fail at cutover. They fail three weeks before cutover, when someone discovers that the legacy system stores phone numbers in four different formats, the reference data doesn't match, and the "simple" field mapping has 23 edge cases nobody discussed.

This template is built for the messy middle — the part between "kickoff meeting" and "go-live email" where most migrations quietly go wrong. **The Object Tracker maps every data object across the full lifecycle — from source analysis through field mapping, transformation logic, validation rules, and post-migration verification. Nothing gets marked "done" until it's actually done. **The Dependency Map surfaces blockers before they surface themselves. Which objects depend on which? What has to migrate first? Where are the circular references hiding? **The Validation Dashboard tracks every rule that needs to pass before cutover — with real-time pass/fail status so you know your actual readiness, not your hoped-for readiness.

Five tasks walk you through the full cycle: discovery, mapping, transformation, validation, and go-live. Each one is scoped to prevent the drift that turns a 6-week migration into a 6-month one.

Open it. Map your objects. Find the problems while you can still fix them cheaply.