Mock load strategy
Plan at least three mock loads: one to prove the tooling, one to prove the data and one full dress rehearsal timed for the cutover window.
Reconciliation checks
- Record counts source vs target per object
- Field-level value checks on a sample
- Financial balances: trial balance, AR, AP, assets, inventory
- Error log reviewed and resolved
Ownership and sign-off
Every migration object needs a business data owner who signs off the reconciliation. Without that signature the object is not ready.
Frequently asked questions
How many mock data loads are needed?
Three is common: technical, data quality and a timed dress rehearsal. Complex programmes often run four or five.