Direct answer: A data migration readiness assessment should inspect source structure and quality without changing production data, map each source field to a target rule, preview accepted and rejected rows, and reconcile record counts and important totals. The result is an evidence pack and go, correct or stop decision—not a claim that live migration occurred.
Profile the source without changing it
Record file or table counts, required fields, duplicates, invalid formats, missing relationships and sensitive fields. Keep the assessment read-only and work from an approved copy or safe query.
Map fields and rejection rules explicitly
For each target field, state the source, transformation, default, validation and rejection reason. Preview rejected rows so the owner can correct, exclude or accept a documented exception.
Reconcile counts and business totals
Compare source, accepted, rejected and target-preview counts. Reconcile important quantities and money totals exactly, record unexplained differences and require approval before any separate live migration project.
Sources reviewed
These sources support the category wording or external method referenced above. SystemLineage’s workflow and limits are stated separately.
Review Data Migration Readiness Assessment, then decide which records, limits and setup apply to your work.
See Data Migration Readiness Assessment