Skip to content
Get a quote

How long does a CRM migration take?

Short answer

Moving the data takes hours to a few days. The full project takes longer, because the audit, mapping review, sample run and automation rebuild happen around the load. At FlitStack AI, most CRM migrations under 1M records go live in 48–72 hours; ones heavy on custom objects take 5–7 days.

By

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

PhaseWhat happensWhat drives the time
AuditCount objects, fields, custom objects, automationsHow messy the source is and how many systems feed it
MappingField and picklist mapping, pipeline design, history cutoffSign-off from sales, finance and support
Sample runLoad a slice and compare it with the sourceHow many fixes the sample turns up
Full runBulk load of records, activities and filesVolume, attachments, API rate limits
CutoverDelta sync, switch users overWhether a delta exists or you need a data freeze
Process rebuildWorkflows, reports, integrationsHow 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

  1. Agree on the history cutoff and owner mapping in week one.
  2. Create users and the schema in the destination before any records go in.
  3. Run the sample early, and fix the mapping instead of fixing data afterwards.
  4. Do the bulk load ahead of time, then a delta at cutover.
  5. 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.

Questions, answered

A few useful answers.

What slows a CRM migration down the most?

Decisions, not data. Waiting on sign-off for picklist mappings, pipeline design or history cutoffs adds more calendar time than record volume does.

Do API rate limits matter?

For large volumes, yes. Every CRM limits API calls, so millions of activities or large attachment sets stretch the load. Batch and bulk endpoints help, and so does running the bulk load before cutover with a delta at the end.

Can we migrate over a weekend?

The final load and delta, yes, if mapping and the sample run are done beforehand. Doing the whole project in a weekend is how mapping mistakes reach production.

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