Migration preparation guide
Use a fictional order example to plan identifiers, relationships and meaningful checks. Includes a brief for a first review.
Read the guideResources
Decide what must match before the import.
Good preparation makes it easier to distinguish a successful move from a new set of hidden inconsistencies.
Are matching row counts enough?
No. Counts can match while values or relationships are wrong. Include important totals and record-level examples that reflect how the data is used.
Should every duplicate be merged?
No. Agree what identifies the same entity and preview uncertain matches. Keep separate inquiries or transactions when they represent different events.
Can the old system be removed immediately?
That depends on verification, retention requirements and the recovery plan. Treat retirement as an explicit decision after the destination is checked.