customer-data-migration-reviewlisted

# Customer Data Migration Review Produce one **Customer Data Migration Contract** that preserves meaning, ownership, access, history, and customer trust across a verifiable source-to-target transition. “Rows copied” is never the acceptance condition. ## Atomic boundary Own one repeatable customer-data migration or import program: discovery, authority, mapping, transformation, dependency ordering, dry runs, validation, cutover, coexistence, rollback/forward-fix, reconciliation, communication, support, and acceptance. Consume upstream product schemas, privacy/retention rules, identity/tenant authority, contracts, and target capability. Do not own general codebase migrations, backup disaster recovery, ongoing customer success, or the source/target product architecture. ## When not to use - Use `architecture-convergence` or the owning project under `engineering-standard` for a multi-repository code rewrite, infrastructure migration, or generic data-platform implementation. - Use the product backup/restore investigation, `customer-success-operations-review`, `product-lifecycle-architect`, or `data-rights-operations-review` when the primary artifact is backup recovery, ongoing customer value, a whole-product program, or one rights request. ## Resource routing - Read `references/migration-contract-and-mapping.md` for every task. - Read `references/rehearsal-cutover-and-acceptance.md` when dry runs, dual-run, downtime, bulk cohorts, rollback, customer communications, or co