A CRM move fails quietly when records are lost, duplicated or mapped to the wrong field, and the problem surfaces months later in reports. This plan sets out what moves and how it is mapped, how duplicates are cleaned, how trial loads are reconciled, and how cutover, rollback and training run. Every step has an owner, and the go or no-go call has written criteria.

The sample is for Umberfield Cloud, a fictional software company moving 42 million records from a legacy CRM over a weekend freeze. Its figures, thresholds and dates are sample data, including 0.06 percent duplicates after cleansing. Replace the systems, objects and thresholds with your own, and agree the reconciliation limits with your data owners before the first trial.