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.
- Scope. List the objects, set a history cutoff for each one, and pick a cutover date.
- 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.
- 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.
- 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.
- Mapping. Map each field and each picklist value. Write down what gets transformed, such as Salesforce Leads becoming HubSpot contacts with a lifecycle stage.
- Source IDs. Add a field for the legacy ID on every object. Reruns, deltas and audits all depend on it.
- Sample run. Load a slice that covers every object type, association and activity type, then compare it field by field.
- Automation freeze. Turn off destination workflows during the load so they don’t send emails or change data.
- Full run and validation. Reconcile counts per object, check associations, and spot-check timestamps and owners.
- Cutover and delta. Catch records that changed in the source during the run, then switch users over.
- Process rebuild. Rebuild automations, reports, dashboards and integrations in the destination.
- 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.