# CRM Migration Checklist | Data, Testing and Cutover > Prepare a CRM migration with data discovery, cleaning, mapping, sample imports, reconciliation, user testing, cutover and rollback decisions. Migration is not a single upload. It is a sequence of discovery, cleaning, mapping, sample testing, reconciliation, user acceptance and cutover decisions for a particular source and destination. ## The migration evidence chain 121 migration methodology. No source, object, volume, timing or service inclusion is assumed. ## Capabilities explained ### Import and export Moves supported records through structured files, with mapping and validation needed before relying on the result. **How it works:** Stores or organises supported business data under configured fields, permissions and record rules. **Why a business would use it:** Supports controlled migration and operational extracts when the data is prepared and reconciled. **Limitations:** The platform does not make imported, duplicated or incomplete data accurate without review. Bulk migration requires mapping and reconciliation; do not treat a completed import as proof of accuracy or reversibility. **Human responsibility:** A data owner must define the record model and resolve quality, ownership and access exceptions. ### Custom fields Adds structured fields to supported record types so a business can capture information it actually needs. **How it works:** Stores or organises supported business data under configured fields, permissions and record rules. **Why a business would use it:** Replaces important notes and spreadsheet columns with searchable, reusable data. **Limitations:** The platform does not make imported, duplicated or incomplete data accurate without review. **Human responsibility:** A data owner must define the record model and resolve quality, ownership and access exceptions. ### Duplicate management Uses account rules and review steps to reduce or resolve repeated contact records. **How it works:** Stores or organises supported business data under configured fields, permissions and record rules. **Why a business would use it:** Keeps teams from following up with the same person through conflicting records. **Limitations:** The platform does not make imported, duplicated or incomplete data accurate without review. **Human responsibility:** A data owner must define the record model and resolve quality, ownership and access exceptions. ### Bulk actions Applies supported updates or actions to a selected group of records rather than one at a time. **How it works:** Stores or organises supported business data under configured fields, permissions and record rules. **Why a business would use it:** Saves administrative effort while retaining a review point before a large change. **Limitations:** The platform does not make imported, duplicated or incomplete data accurate without review. **Human responsibility:** A data owner must define the record model and resolve quality, ownership and access exceptions. ## Identify the authoritative source before changing it. Create a dated inventory and a protected source copy so the migration can be explained and checked later. ### Accounts and access Confirm source owner, export permissions, credentials, formats, limits and any supplier assistance required. ### Objects and relationships List contacts, organisations, opportunities, activities, notes, attachments, users, consent and relationships separately. ### Source evidence Retain agreed counts, sample records, export date and integrity checks without leaving unnecessary copies accessible. ## Resolve meaning before transforming values. A technically valid import can still be operationally wrong when fields or stages mean different things. ### Quality profile Measure missing identifiers, duplicates, stale records, inconsistent formats and unsupported content. ### Mapping specification Record source, destination, type, transformation, default, exclusion and exception owner for each field. ### Stage and owner decisions Map opportunities and responsibilities using explicit rules; route ambiguity to a person rather than guessing. ## Use a representative test to prove more than record count. The sample should exercise relationships, duplicates, dates, permissions and exceptions as well as ordinary rows. ### Controlled sample Include each object type, edge case and important relationship in a reversible import. ### Reconciliation Compare counts, key fields, linked records, exclusions, errors and destination behaviour against the source evidence. ### Journey testing Ask users to find, update and progress representative records using intended permissions and workflows. ## Plan final change, fallback and source retention together. A completed import still needs operating ownership and a documented decision about the old system. ### Freeze and final export Agree the last-write point, data captured after the sample, import order and connection changes. ### Go/no-go and fallback Name the decision owner, blocking checks, repair route and conditions for returning to the protected source. ### Post-cutover review Reconcile again, monitor exceptions, close temporary access and document retention or deletion responsibilities. ## Frequently asked questions ### Can a CRM migration be lossless? Do not assume so. Products differ in fields, relationships, history, attachments, permissions and workflow behaviour. Define and accept known exclusions explicitly. ### Why run a sample import first? A sample reveals mapping, format, relationship, duplicate, permission and workflow problems while the scope is still controlled and reversible. ### What should be reconciled? Check object counts, key values, relationships, exclusions, errors and representative user journeys—not only whether the import job reports success. ### When should the old system be deleted? Only after contractual, legal, operational and evidence needs are resolved. The customer should approve retention, access and disposal responsibilities. ## Related CRM pages - [/crm/guides](https://121.direct/crm/guides) - [/crm/switch](https://121.direct/crm/switch) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.