Migration validation
Checking that data moved to a new CRM is complete and correct before the team switches over.
What it is
Migration validation is the last step before go-live. It proves the import did what it was supposed to do, so nobody discovers missing deals a month after the old system is switched off.
What to check
- Counts. Records per object in the source match the target, minus anything you chose to drop.
- Relationships. People link to the right companies, and deals link to the right funds or accounts.
- Field types. Dates, currencies, and selects arrived as the right type, not as text.
- History. Notes and activity sit on the right records with the original timestamps where possible.
- Process state. Every record landed in the right list and stage.
- Duplicates. The import did not create new ones.
How to do it
- Export record counts from the source before migrating.
- Compare them against the target after each import step.
- Spot-check a sample of records end to end, starting with the ones the team uses most.
- Have the people who know the data best review their own pipelines.
- Keep the source system read-only until sign-off.
Why it matters
A migration is only as good as the team’s trust in the new data. One missing deal is enough for people to keep a spreadsheet on the side.
On this site