Data Migration Validation for Business Users

Keep this: job aid

Migrated data validation card

• Know your objects and their order: config, master data, open documents, open items, balances.
• Review mapping values for fields you own before the first full load.
• Freeze source counts and totals at the same cut-off as the extract.
• Per object: count by group, control total or field profile, random plus targeted sample.
• Compare samples with the legacy source, not the load file.
• Finance: AR, AP and inventory tie to G/L; migration offset accounts net to zero.
• Log every difference: check, expected vs actual, records, impact, cause, owner, status.
• Fix causes (source, extract, mapping, config), not symptoms; re-validate in the next load.
• Sign acceptance per object with exceptions listed; it feeds go/no-go.
• Turn accepted exceptions into hypercare items with owners and dates.