Skip to content
Get a quote

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.

By

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

StepNative helpGap
AuditHubSpot Smart Transfer audits supported sourcesOnly for apps on its list; custom objects aren’t supported
SchemaSmart Transfer and Zoho’s Migration Wizard create some fieldsZoho can’t create autonumber or formula fields during migration
Sample runA small import you can delete afterwardsNo field-by-field comparison against the source
DeltaNot offered by file importersChanges made during cutover are lost unless you re-export them
Process rebuildSalesforce’s switch plan lists “rebuild workflows” as a stepIt’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.

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.

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