---
title: "CRM migration checklist: plan, steps and best practices"
description: "A step-by-step CRM migration plan: audit, mapping, destination setup, sample run, cutover and validation, with the native-tool limits that catch teams out."
url: "https://flitstack.ai/guides/crm-migration-checklist"
---

# CRM migration checklist

Short answer

A CRM migration plan has eight stages: audit the source, decide what moves, map objects and fields, build the destination, back up and test with a sample, migrate in dependency order, cut over with a delta for late changes, then validate and rebuild automation. FlitStack AI runs the data stages for you, with validation and one-click rollback.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Have it done for you ](https://flitstack.ai/contact) [Back to the hub →](https://flitstack.ai/migrations/crm)

******What we handle 5

- Back up the source
- Map objects and fields
- Keep relationships
- Keep history and dates
- Test before the full run

## What the native tool does, and where it stops

| Task                           | Native tool                                                                                                                                      | With FlitStack AI                                                              |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------ |
| Back up the source             | Salesforce Data Export Service (files deleted 48 hours after the email); HubSpot record exports per object (links expire after 30 days).         | Reads the source through its API, with no download windows to chase.           |
| Map objects and fields         | Spreadsheet mapping by hand; importers match column names to fields.                                                                             | AI-proposed field-level mapping you review and override before any data moves. |
| Keep relationships             | Load parents first, export new IDs, look them up into child files.                                                                               | Rebuilds associations from source IDs automatically, in dependency order.      |
| Keep history and dates         | Salesforce needs Create Audit Fields enabled; HubSpot sets contact Create date automatically; activity dates default to import time if unmapped. | Preserves timestamps and user attribution on records and activities.           |
| Test before the full run       | Import a small file and check by eye.                                                                                                            | Sample run on a representative subset, including custom objects.               |
| Cut over without a long freeze | Re-export and re-import whatever changed after the first export.                                                                                 | Delta migration captures records changed in the source during cutover.         |
| Validate and undo              | Error files and row counts. No rollback.                                                                                                         | Field data-type validation, hash checks on every record, one-click rollback.   |

Most CRM migrations that go wrong fail before any data moves: an object nobody listed, a picklist nobody mapped, an export that left the emails behind. This checklist puts the decisions in order. Each stage has a short list of checks, and where a native tool has a documented limit that changes the plan, it is called out.

## What should a CRM migration plan include?

| Stage                    | Output                                                          | Owner                         |
| ------------------------ | --------------------------------------------------------------- | ----------------------------- |
| 1. Audit the source      | Inventory of objects, record counts, fields, users, automations | CRM admin                     |
| 2. Decide scope          | What moves, what’s archived, what’s dropped                     | Sales ops plus leadership     |
| 3. Map                   | Object, field, picklist and owner mapping, signed off           | CRM admin plus migration lead |
| 4. Build the destination | Properties, pipelines, users, labels, permissions               | Destination admin or partner  |
| 5. Back up and test      | Full backup, sample run, sign-off                               | Migration lead                |
| 6. Migrate               | All objects loaded in order, with history                       | Migration lead                |
| 7. Cut over              | Delta of late changes, source set read-only                     | Migration lead plus admins    |
| 8. Validate and rebuild  | Reconciliation report, automation and reports rebuilt           | Admin plus process owners     |

## Stage 1: What should I audit in the old CRM?

- **Every object in use,** standard and custom, with record counts.
- **Every field** per object, with fill rate. Fields under a few percent filled are candidates to drop.
- **Picklist and dropdown values,** including retired ones still on old records.
- **Relationships:** which objects link to which, and any many-to-many links or relationship types.
- **Activity history:** emails, calls, meetings, tasks and notes, with counts per type.
- **Files and attachments,** with total size.
- **Users and owners,** including inactive users who still own records.
- **Automations, reports and integrations** that touch the CRM.
- **What the export leaves out.** Some exports skip whole data types. Zendesk Sell’s export, for example, can’t include emails, call logs or activity history.

## Stage 2: How do I decide what to migrate?

- Keep everything open: live deals, open tickets, active accounts.
- Keep history customers or auditors may ask about.
- Keep data your reports depend on, such as closed-won history for forecasting.
- Archive the rest in a searchable backup instead of deleting it.
- Agree the duplicate rules: which field identifies a duplicate, which record wins.
- Write the scope down and get it signed off.

## Stage 3: How do I map objects and fields?

- **Map objects first.** Data models differ: Salesforce has separate leads and record types; HubSpot uses lifecycle stages and pipelines; Zoho has modules and sub-forms.
- **Map fields with types.** A text field can’t land in a number field. Dates need one format.
- **Map picklist values** one by one, including stages and statuses.
- **Map owners by email** to users in the destination.
- **Decide where original dates go.** HubSpot sets the contact Create date automatically, so carry the source date into a custom property. Salesforce lets API tools set Created Date and Created By once an admin enables Create Audit Fields.
- **Flag fields the destination can’t create on the fly.** Zoho’s Migration Wizard, for example, can’t create Formula or Autonumber fields and creates at most 50 new fields during migration.

## Stage 4: What do I set up in the new CRM first?

- Users, roles, teams and permissions.
- Custom fields and properties, with dropdown values matching the mapping.
- Pipelines and stages.
- Custom objects and their associations.
- Association labels or relationship types. HubSpot needs custom labels to exist before import, and they require Professional or Enterprise.
- Duplicate rules and validation rules, switched off for the load if they would reject historical data.
- Automations left off until the data is in, so old records don’t trigger emails or tasks.

## Stage 5: How do I back up and test?

- **Take a full backup of the source.** In Salesforce, the Data Export Service includes attachments if you select them; its zip files are deleted 48 hours after the email, so download them straight away.
- **Run a sample** that covers every object, including custom objects, records with many activities and records with attachments.
- **Check samples in the UI,** not just counts: open ten records and compare them field by field with the source.
- **Have users sign off** the sample before the full run.

## Stage 6: What order do I migrate in?

1. Users (or owner mapping).
2. Companies or accounts.
3. Contacts and leads.
4. Deals or opportunities, with line items.
5. Tickets or cases.
6. Custom objects, parents before children.
7. Activities: emails, calls, meetings, tasks, notes, each linked to its parent records.
8. Files and attachments.

Loading out of order is the most common cause of orphaned records: a contact loaded before its company has nothing to attach to.

## Stage 7: How do I cut over with minimal downtime?

- Pick a cutover window and tell users.
- Capture records created or changed in the source since the main run, and migrate that delta.
- Set the old CRM to read-only for users.
- Repoint integrations, forms and email sync to the new CRM.
- Switch automations on in the new CRM.

## Stage 8: How do I validate the migration?

- Compare record counts per object, source against destination.
- Compare totals that matter: pipeline value, closed-won by year, open ticket count.
- Spot-check records with the most activities and attachments.
- Check owners, create dates and stage values on a random sample.
- Rebuild workflows, reports and dashboards, and test them with real records.
- Keep the old system read-only, or keep the backup, until finance and sales sign off.

## What are CRM migration best practices?

- **Freeze the schema, not the users.** Lock field and pipeline changes during the project, but use a delta to keep users working.
- **Migrate history with the record,** not as a later phase that never happens.
- **Test on the hardest records,** not the cleanest.
- **Make it repeatable.** You’ll run the migration more than once. A manual process that can’t be rerun is a risk.
- **Keep a way back.** Know how you would undo the load before you run it.

## When to bring in FlitStack AI

FlitStack AI is a data-migration platform sold as software plus a done-for-you service. It covers stages 3 to 8 for the data: AI-proposed mappings you review, a sample run, migration in dependency order with timestamps and owners kept, delta migration for cutover, validation on every record and one-click rollback. The [CRM implementation service](https://flitstack.ai/services/crm-implementation) handles the destination build and automation rebuild.

Estimating budget? Read [what drives CRM migration cost](https://flitstack.ai/guides/crm-migration-cost). Browse routes on the [CRM migration hub](https://flitstack.ai/migrations/crm), or [book a free scoping call](https://flitstack.ai/contact).

![Aditya Kumar](https://flitstack.ai/images/authors/aditya-kumar.webp)

About the author

[Aditya Kumar](https://flitstack.ai/about/aditya-kumar)

Founder, FlitStack AI

Aditya Kumar is the founder of FlitStack AI and Jetstack AI, both built at Ambrstack. FlitStack AI migrates CRM and business data between platforms; Jetstack AI is the AI platform HubSpot partners and RevOps teams use to audit portals, build implementations and reuse their best setups across portals. He writes about CRM data, migrations, HubSpot architecture and automation from the work of building them.

[More from Aditya](https://flitstack.ai/about/aditya-kumar) [LinkedIn](https://www.linkedin.com/in/aditya-ambrstack/)

On this page

Questions, answered

## A few useful answers.

How long does a CRM migration take?

Planning and destination setup usually take longer than moving the data. On FlitStack AI, most CRM migrations under 1 million records go live in 48 to 72 hours, including mapping review, sample run and cutover; custom-object-heavy migrations typically take 5 to 7 days.

How many years of CRM data should I migrate?

Move everything that is open, everything a customer could ask about, and history your reports or compliance rules need. Archive the rest in a backup you can search. Cutting history saves little if it is migrated by a tool, but it saves a lot if it is cleaned and loaded by hand.

Should I clean data before or during the migration?

Decide the rules before, apply them during. Agree how duplicates are merged, which records are dropped and how picklist values change, then apply those rules in the migration so you aren't cleaning twice.

Do workflows and automations migrate with the data?

Not as data. Workflows, validation rules, flows and reports have to be rebuilt in the destination, because every CRM's automation model is different. Inventory them before migration so the rebuild is planned.

## Related

### [CRM migration](https://flitstack.ai/migrations/crm)

[Read →](https://flitstack.ai/migrations/crm)

### [How much does a CRM migration cost, and what drives the price?](https://flitstack.ai/guides/crm-migration-cost)

[Read →](https://flitstack.ai/guides/crm-migration-cost)

### [What does the HubSpot importer keep, and what does it drop?](https://flitstack.ai/guides/hubspot-import)

[Read →](https://flitstack.ai/guides/hubspot-import)

### [Salesforce Data Loader vs Data Import Wizard vs dataloader.io: which should you use?](https://flitstack.ai/guides/salesforce-data-loader)

[Read →](https://flitstack.ai/guides/salesforce-data-loader)

### [How does the Zoho CRM Migration Wizard work, and what are its limits?](https://flitstack.ai/guides/zoho-crm-import)

[Read →](https://flitstack.ai/guides/zoho-crm-import)

### [CRM implementation services: data migration and process setup in one project](https://flitstack.ai/services/crm-implementation)

[Read →](https://flitstack.ai/services/crm-implementation)

## Sources

1. [Trailhead: Import Data (prepare, clean, map, test)](https://trailhead.salesforce.com/content/learn/modules/lex_implementation_data_management/lex_implementation_data_import)
2. [Trailhead: Export Data (Data Export Service)](https://trailhead.salesforce.com/content/learn/modules/lex_implementation_data_management/lex_implementation_data_export)
3. [Salesforce Help: Enable the Create Audit Fields permission](https://help.salesforce.com/s/articleView?id=000386699\&type=1)
4. [HubSpot KB: Set up your import file](https://knowledge.hubspot.com/import-and-export/set-up-your-import-file)
5. [HubSpot KB: Export your records](https://knowledge.hubspot.com/import-and-export/export-records)
6. [Zoho CRM: Migrating data from other CRMs](https://help.zoho.com/portal/en/kb/crm/data-administration/data-migration/articles/migrating-data-from-other-crms)
7. [Zendesk: Announcing the retirement of Zendesk Sell (export contents)](https://support.zendesk.com/hc/en-us/articles/9591462550042-Announcing-the-retiring-of-Zendesk-Sell)

Get a quote

## Rather have it done for you?

FlitStack AI maps, validates and migrates your data, sets up the process in the new system, and keeps a one-click rollback.

[Get a quote](https://flitstack.ai/contact)
