Migration Validation: Check Imported Data Before You Operate From It
Question: What should a team verify after bringing data into a new operational workspace?
Imported does not mean correct
An import can create records, but it does not prove that each record is complete, correctly mapped, safe to use, or ready for customer communication. Treat migrated information as needing structured review before it becomes the operational source of truth.
Validate a safe sample
- Identify the record types that were brought in.
- Review representative non-sensitive records using approved test or anonymized examples.
- Check that relationships make sense: customers, leads, jobs, tasks, and related records.
- Compare field meaning, not only field names.
- Look for duplicates, missing owners, and unexpected statuses.
- Record issues with a named reviewer and next action.
- Do not bulk-change or contact people until the approved validation is complete.
Never use screenshots or exported files containing live customer information to document a public migration discussion.
For migration fundamentals, see Migration Hub: Bring Data Across Without Losing Track of the Source. For duplicates, see Duplicate Records.
Boundaries
This guide explains a validation process. It does not prove import completeness, data accuracy, permissions, mapping quality, retention, consent, security, compliance, successful cutover, or readiness for production operations. Confirm those separately.