---
title: "How long does a CRM migration take?"
description: "Moving the data takes hours to days; the full project takes longer. What drives CRM migration time, phase by phase, and how to keep it short."
url: "https://flitstack.ai/answers/how-long-does-a-crm-migration-take"
---

# 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.

![](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)

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

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](https://flitstack.ai/guides/crm-migration-checklist) or [book a scoping call](https://flitstack.ai/contact).

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

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.

## 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. [HubSpot: Transfer data from other apps using HubSpot Smart Transfer](https://knowledge.hubspot.com/integrations/transfer-data-from-other-apps-using-hubspot-smart-transfer)
2. [HubSpot Product and Services Catalog: Consulting services (CRM Data Migration)](https://legal.hubspot.com/hubspot-product-and-services-catalog/consulting-services)
3. [Salesforce Trailhead: Import data (Data Import Wizard and Data Loader)](https://trailhead.salesforce.com/lex_implementation_data_management/lex_implementation_data_import)

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)
