---
title: "What a CRM migration checklist should include"
description: "The CRM migration checklist in order: scope, data audit, users, mapping, sample run, validation, cutover and process rebuild, plus the items native guides skip."
url: "https://flitstack.ai/answers/what-should-a-crm-migration-checklist-include"
---

# What should a CRM migration checklist include?

Short answer

A CRM migration checklist should cover eight stages in order: scope and cutoff, a source audit, users and owners, schema and field mapping, a sample run, the full run with validation, cutover with a delta sync, and rebuilding automations and reports in the destination. The steps people most often miss are users-first, source IDs and the automation freeze.

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

[Ask us about your migration ](https://flitstack.ai/contact) [Read the full guide →](https://flitstack.ai/guides/crm-migration-checklist)

## The checklist, in order

Vendor checklists are written for their own importer. This one is platform-neutral, and the items in bold are the ones that cause rework when they’re skipped.

1. **Scope.** List the objects, set a history cutoff for each one, and pick a cutover date.
2. **Source audit.** Count records per object, find duplicates, and list custom fields, custom objects, picklists and attachments. List every automation, report and integration as well.
3. **Users and owners first.** Create the users in the destination before any records go in. Owner fields, activity authors and, in Zoho CRM, attachments all depend on users that already exist.
4. **Schema.** Create custom fields, picklist values, pipelines and association types in the destination. Some importers can create fields; none of them create every field type.
5. **Mapping.** Map each field and each picklist value. Write down what gets transformed, such as Salesforce Leads becoming HubSpot contacts with a lifecycle stage.
6. **Source IDs.** Add a field for the legacy ID on every object. Reruns, deltas and audits all depend on it.
7. **Sample run.** Load a slice that covers every object type, association and activity type, then compare it field by field.
8. **Automation freeze.** Turn off destination workflows during the load so they don’t send emails or change data.
9. **Full run and validation.** Reconcile counts per object, check associations, and spot-check timestamps and owners.
10. **Cutover and delta.** Catch records that changed in the source during the run, then switch users over.
11. **Process rebuild.** Rebuild automations, reports, dashboards and integrations in the destination.
12. **Decommission.** Keep the source read-only and archived until your retention policy allows deletion.

## What native tools do / where they stop

| Step            | Native help                                                   | Gap                                                             |
| --------------- | ------------------------------------------------------------- | --------------------------------------------------------------- |
| Audit           | HubSpot Smart Transfer audits supported sources               | Only for apps on its list; custom objects aren’t supported      |
| Schema          | Smart Transfer and Zoho’s Migration Wizard create some fields | Zoho can’t create autonumber or formula fields during migration |
| Sample run      | A small import you can delete afterwards                      | No field-by-field comparison against the source                 |
| Delta           | Not offered by file importers                                 | Changes made during cutover are lost unless you re-export them  |
| Process rebuild | Salesforce’s switch plan lists “rebuild workflows” as a step  | It’s a manual project                                           |

## Where FlitStack AI fits

FlitStack AI covers steps 5–10 in the platform: AI-proposed field mapping you review, a sample run, hash-based validation, one-click rollback and delta sync. The done-for-you service can cover the rest. The full version is in the [CRM migration checklist guide](https://flitstack.ai/guides/crm-migration-checklist).

![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.

Who should own the checklist?

One person on the business side, usually a RevOps or sales ops lead, plus whoever runs the migration. Sales, finance and support each sign off on their own objects.

How long before go-live should we freeze changes to the source?

With a delta sync you don't need a hard freeze. Without one, freeze schema changes (new fields, picklist values) at least a week before cutover, and freeze data edits only for the final load.

Is rebuilding workflows part of the migration?

It's part of the project but not part of the data load. Automations don't move between platforms as data, so list them during the audit and rebuild them in the destination.

## Related

### [CRM migration checklist: what to do before, during and after the move](https://flitstack.ai/guides/crm-migration-checklist)

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

### [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)

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

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

### [Data migration services for CRM, help desk, ERP, PM and HR systems](https://flitstack.ai/services/data-migration)

[Read →](https://flitstack.ai/services/data-migration)

## Sources

1. [Salesforce: Switching from Zendesk Sell (six-step migration plan)](https://www.salesforce.com/small-business/sales/zendesk-sell/)
2. [HubSpot: Understand HubSpot's CRM migration process](https://knowledge.hubspot.com/integrations/understand-hubspot-s-crm-migration-process)
3. [Zoho CRM: Data migration FAQs](https://help.zoho.com/portal/en/kb/crm/faqs/data-administration/data-migration/articles/faqs-data-migration)
4. [HubSpot Community: migration from in-house CRM (data audit, lifecycle automation, integrations)](https://community.hubspot.com/t/hubspot-migration-from-in-house-crm-data-audit-lifecycle-automation-and-integrations/144912/4)

A closer look

## Tell us what you’re moving.

Share your source, destination and rough record counts. We scope the migration and the process work with you and send you a quote.

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