Run time vs. project time
When someone asks how long a migration takes, they usually mean one of two things. Run time is how long the data takes to move. That depends on record volume, activities, attachments and the destination’s API limits. Project time runs from the first audit to the day users stop opening the old CRM. That depends mostly on how fast you can make decisions.
Phase by phase
| Phase | What happens | What drives the time |
|---|---|---|
| Audit | Count objects, fields, custom objects, automations | How messy the source is and how many systems feed it |
| Mapping | Field and picklist mapping, pipeline design, history cutoff | Sign-off from sales, finance and support |
| Sample run | Load a slice and compare it with the source | How many fixes the sample turns up |
| Full run | Bulk load of records, activities and files | Volume, attachments, API rate limits |
| Cutover | Delta sync, switch users over | Whether a delta exists or you need a data freeze |
| Process rebuild | Workflows, reports, integrations | How many automations the source had |
What native tools do / where they stop
HubSpot doesn’t publish record-volume speeds for Smart Transfer and says only that a transfer can take several hours. HubSpot’s paid CRM Data Migration service lists a delivery window of up to 60 days. Salesforce’s Data Import Wizard caps each import at 50,000 records. Larger loads go through Data Loader, which adds the time to prepare files and load them in batches. None of these timelines includes rebuilding automations.
How to keep it short
- Agree on the history cutoff and owner mapping in week one.
- Create users and the schema in the destination before any records go in.
- Run the sample early, and fix the mapping instead of fixing data afterwards.
- Do the bulk load ahead of time, then a delta at cutover.
- Rebuild the automations you need on day one first. The rest can follow.
Where FlitStack AI fits
The 48–72 hour figure covers FlitStack AI’s discovery, mapping review, sample run and cutover. Migrations heavy on custom objects typically take 5–7 days. For an estimate on your data, see the CRM migration checklist or book a scoping call.