---
title: "How long does a CRM migration take? A realistic schedule for a small team"
description: "A 10–30 person team with clean data typically takes 4–8 weeks to move off HubSpot. Here's the schedule, what slows it down, and how to time it to your renewal."
pubDate: "2026-11-15T00:00:00.000Z"
vertical: "general"
mode: "playbook"
tags: ["crm-migration","hubspot","small-business","data-migration","timeline"]
author: "Isai Guerrero"
question: "How long does a CRM migration take?"
answer: "A 10–30 person team with clean data typically takes 4–8 weeks to move its records, history and daily screens. Whole projects run 1–6 months, depending on size. The team keeps working in the old CRM until the numbers match, so nobody stops selling. If you're leaving HubSpot, start about 90 days before renewal."
readTime: "10 min read"
draft: false
seoTitle: "How long does a CRM migration take?"
tldr: "A 10–30 person team with clean data typically takes 4–8 weeks to move its records, history and daily screens. Whole projects run 1–6 months. Your team keeps working in the old CRM while the new one is built and checked. If you're leaving HubSpot, start about 90 days before your renewal date."
keyTakeaways: ["A 10–30 person team with clean data typically takes 4–8 weeks to move its records, history and the screens it uses every day.","Whole migration projects take 1–6 months. More people, more connected tools and messier data push toward six months.","There's no downtime. The team keeps working in the old CRM while the new one is built, and both run side by side until the numbers match.","Records export from HubSpot in minutes. Notes, calls and email history need HubSpot's API, and workflows have to be rebuilt. History is what sets the schedule.","HubSpot contracts renew automatically and can't be cancelled mid-term. Count back about 90 days from your renewal date and turn off auto-renewal first.","The real-estate company I moved off HubSpot ran both systems for more than eight months on purpose, so nobody lost a record."]
faq: [{"q":"How long does it take to move a small business to a new CRM?","a":"A 10–30 person team with clean data typically takes 4–8 weeks to move its records, history and daily screens. Whole projects take 1–6 months, depending on the size of the team, the number of connected tools and how messy the data is."},{"q":"Will my team have downtime during a CRM migration?","a":"No. The new CRM is built next to the old one while the team keeps working. Records are moved and checked, and both systems run side by side until the numbers match. The team switches on a day you pick."},{"q":"When should I start a HubSpot migration before my renewal?","a":"About 90 days before your renewal date. HubSpot contracts renew automatically and can't be cancelled mid-term. Turn off auto-renewal early, so a slipped schedule doesn't lock you in for another year."},{"q":"What takes the longest in a CRM migration?","a":"Activity history and automation. Contacts, companies and deals export from HubSpot as spreadsheets. Notes, calls and logged emails need HubSpot's API, and workflows, sequences and reports have to be rebuilt in the new system."},{"q":"What happens to HubSpot workflows after you downgrade?","a":"If you downgrade all Professional and Enterprise subscriptions, workflows are turned off at once and deleted 90 days later. Sequences are also deleted after 90 days. Document or rebuild them before your renewal date."}]
audience: "owner-operator"
icp_segment: "general"
funnel_stage: "consideration"
intent: "informational"
format: "long-form"
content_stage: "intermediate"
summary: "A 10–30 person team with clean data typically takes 4–8 weeks to move CRMs, and whole projects run 1–6 months. The team keeps working in the old CRM until the numbers match. HubSpot users should start about 90 days before renewal."
citation_source: "https://knowledge.hubspot.com/import-and-export/export-records"
confidence_score: 0.85
topic_cluster: "crm-migration"
parent_topic: "leaving-hubspot"
related_ids: ["should-you-leave-hubspot","crm-migration-cost-small-business"]
entities: [{"name":"CRM migration","type":"Service","relevance":"primary"},{"name":"HubSpot","type":"Organization","relevance":"primary"},{"name":"Data migration","type":"Concept","relevance":"primary"},{"name":"Salesforce","type":"Organization","relevance":"secondary"}]
url: "https://advisorylabs.xyz/blog/how-long-crm-migration-takes/"
source: "https://advisorylabs.xyz/blog/how-long-crm-migration-takes.md"
---


Most owners who ask how long a CRM move takes have two worries. The first is that the team
stops selling while it happens. The second is that years of customer history get lost on the
way over. Behind both sits a date: the day HubSpot renews for another year.

I move small companies off HubSpot and onto CRMs they own. This post gives you the schedule I
work to, what makes it longer, and how to fit it before your renewal. All figures are as of
November 2026.

## A small team with clean data takes 4–8 weeks

A 10–30 person team with clean data typically takes **4–8 weeks** to move its records, history
and the screens it uses every day. Whole projects run **1–6 months** from start to switch-over,
depending on size.

Those two numbers measure different things. The 4–8 weeks covers the core move: your
customers, deals and history, plus the daily screens your team works in. The 1–6 months covers
everything a project can include, from the first look at your CRM to the day the old one is
switched off.

Other firms quote similar ranges for the core move. Agencies quote 4–6 weeks for a small, clean
HubSpot account with fewer than 25,000 records
([Coffee.ai](https://www.coffee.ai/articles/how-to-migrate-from-hubspot)). They quote 6–8 weeks
for teams under 20 reps
([LOW/CODE](https://www.lowcode.agency/blog/custom-crm-migration-from-hubspot)).

Two things add time on top of the core move. Rebuilding years of marketing automation takes
longer. So does moving a website that runs on HubSpot's CMS. I quote both separately, because
they vary so much from one company to the next.

## The schedule, phase by phase

Every migration I run follows the same five phases, in the same order. The length of each one
depends on your data, so the table shows what happens and how you know a phase is done.

| Phase | What happens | Your team | Done when |
|---|---|---|---|
| 1. Map | I map your CRM, your data and how your team works. A sample export shows how messy the history is. | Keeps working in the old CRM. | Every record type, tool and workflow is marked rebuild, replace or drop. |
| 2. Build next to it | The new CRM is built next to the old one. It follows the steps your team already uses. | Keeps working in the old CRM. | The daily screens are ready to use. |
| 3. Move and check | Records and history are moved. Then they're checked against the old CRM. | Keeps working in the old CRM. | Counts match and spot checks pass. |
| 4. Run side by side | Both systems run at once until the numbers match. | Starts using the new CRM. | Nothing important still goes to the old CRM. |
| 5. Switch off and hand over | The old CRM is switched off. You get the software, the data and a written guide. | Works only in the new CRM. | You own every account and the guide. |
| **Total** | **Typically 4–8 weeks** for a 10–30 person team with clean data. | | |

Phase 1 sets the real schedule. Before anyone commits to a date, export the full history of
about 50 typical contacts. How messy that sample is tells you more than any estimate
([LOW/CODE](https://www.lowcode.agency/blog/custom-crm-migration-from-hubspot)). Salesforce
gives the same advice for its own imports. It recommends importing a small test file first, to
check the source data is ready
([Salesforce Trailhead](https://trailhead.salesforce.com/en/content/learn/v/modules/lex_implementation_data_management/lex_implementation_data_import)).

Don't skip phase 4. It's where you find the field that didn't come over, or the report that
counts deals twice.

## Your team keeps working the whole time

There's no downtime in a migration done this way. Your team keeps selling in the old CRM while
the new one is built and checked.

The new CRM goes up next to the old one. Records come over and get checked against the
original. Then both systems run side by side until the numbers match. You pick the switch day,
once your team trusts the new screens.

The cost of running both is mostly people's time. Reps reconnect their inboxes, rebuild their
sequences and check two screens for a while. Plan for a few weeks of that. It's the price of
never having a day when nobody can find a customer.

## History takes longer to move than records

Contacts and deals come out of HubSpot quickly. Activity history needs extra work, and
automation has to be rebuilt by hand. That's why the history sets your schedule. The full
list of what exports and how is in [how to export everything from HubSpot](/blog/export-everything-from-hubspot/).

HubSpot's data falls into three groups:

1. **Exports from the screen.** Contacts, companies, deals and tickets export as spreadsheets,
   with their current values and the links between them. You can run up to 300 exports in 24
   hours, three at a time, and download links expire after 30 days
   ([HubSpot](https://knowledge.hubspot.com/import-and-export/export-records)).
2. **Needs HubSpot's API.** Record exports don't include notes, calls, meetings or logged emails.
   HubSpot points you to contact-level exports, activity reports or its engagements API to get
   them ([HubSpot](https://knowledge.hubspot.com/import-and-export/export-records)).
3. **Has to be rebuilt.** Workflows, sequences, templates, forms, reports and dashboards don't
   transfer to any other CRM. Someone has to rebuild each one.

On a 10–30 person team, the records part might take days. The history part is what stretches
into weeks. On the real-estate project I ran, support conversations and escalation logs needed
their own export and import steps. Duplicate contacts had to be found and merged before anything
else could be checked.

## Five things push a migration toward six months

More people, more connected tools and messier data are what move a project from weeks toward
months. Each one adds work in phases 3 and 4.

- More users means more screens, more roles and more people to move over.
- Email, calendar, e-signature, texting and billing each need to be reconnected and tested.
- Duplicate contacts and years of half-filled fields have to be cleaned before the numbers can
  match.
- Years of marketing workflows and sequences take time to rebuild and test.
- If HubSpot hosts your website, the site has to move too.

Data quality is the one most teams underestimate. In a survey by Validity, 44% of respondents
said they lose over 10% of annual revenue to low-quality CRM data
([Validity](https://www.validity.com/resource-center/the-state-of-crm-data-management-2022/)).
The same bad data that costs you sales also slows the move. Salesforce tells customers to remove
duplicates, delete unneeded data and fix spelling errors before any import
([Salesforce Trailhead](https://trailhead.salesforce.com/en/content/learn/v/modules/lex_implementation_data_management/lex_implementation_data_import)).

If your data is clean and your team uses a handful of tools, you sit at the short end. If you
have years of automation, a dozen integrations and a HubSpot website, expect the long end.

## Start 90 days before your HubSpot renewal

Count back about 90 days from your renewal date. HubSpot contracts can't be cancelled mid-term,
so the schedule has to finish before the next term starts.

Three contract rules drive this date:

- HubSpot contracts renew automatically for the same term, up to a year. You can't cancel or
  downgrade mid-term, and prepaid fees aren't refunded
  ([HubSpot Customer Terms](https://legal.hubspot.com/terms-of-service)).
- Downgrades need notice at least five business days before renewal. Some order forms require
  more, so read yours
  ([HubSpot](https://knowledge.hubspot.com/account/how-do-i-cancel-my-hubspot-account)).
- When you downgrade every Professional and Enterprise subscription, workflows are turned off at
  once and deleted 90 days later. Sequences are also deleted after 90 days
  ([HubSpot](https://knowledge.hubspot.com/account-management/downgrade-a-paid-subscription)).

After a paid term ends, only Marketing Hub Professional and Enterprise customers can request
their data. They have 30 days to ask
([HubSpot Product Specific Terms](https://legal.hubspot.com/product-specific-terms)). Your
records usually stay in the free HubSpot account. Don't count on that alone.

Here's how the five phases fit a 90-day countdown:

| Days before renewal | What to do |
|---|---|
| 90–75 | Find your notice deadline in the order form. Turn off auto-renewal now. |
| 75–60 | Map everything: workflows, sequences, reports, forms, integrations, connected inboxes. Mark each one rebuild, replace or drop. |
| 60–45 | Export a 50-contact sample with full history. Use it to set the real schedule. |
| 45–15 | Build next to HubSpot, move records in order, check counts and run both systems. |
| 15–0 | Switch the team over. Take a final full export, including activities from the API. Keep the free account as an archive. |

Turning off auto-renewal first is the safety net. If the move slips, you aren't locked in for
another full year by accident.

If your renewal is less than 90 days away, you still have options. Moving during the paid term
is fine. What matters is that every export is done before the term ends.

## How to keep from losing data during the move

Most data loss in a migration comes from a few predictable mistakes. Each one has a check you
can run before the switch.

- **Custom fields that silently drop.** If a field doesn't exist in the new CRM, many imports
  skip it without warning. Create every field before importing.
- **Duplicates merged into the wrong record.** A bad merge attaches one customer's history to
  someone else. Merge duplicates before the move.
- **Deals that lose their company.** Import companies first, then contacts, then deals, then
  activity. That order keeps the links between them.
- **Old leads getting "welcome" emails.** Imported contacts can trigger new-lead automations to
  real people. Keep automations off until the import is checked
  ([LOW/CODE](https://www.lowcode.agency/blog/custom-crm-migration-from-hubspot)).
- **Old and new numbers mixed in reports.** On the real-estate project, sales reports only count
  from a set cutoff date, April 1, 2026. Half-moved data never shows up beside clean numbers.
- **Code that still writes to HubSpot.** On the same project, an automated test fails if any code
  tries to call HubSpot again.

The final check is simple to state. Count the records in both systems, then open a sample of
records side by side. When the counts match and the samples agree, you're ready to switch.

## Two real switches, and how long they ran

In both case studies, the two systems ran side by side before HubSpot was switched off. The
length depended on the size of the system.

**The real-estate marketing company** replaced HubSpot and an outside software agency at once.
History came over first: contacts, deals, tickets, conversations and support logs were exported,
imported and checked. The first full HubSpot export was in late 2025. Then both systems ran side
by side, with the new one keeping HubSpot in sync while the team moved over. HubSpot's last
scheduled jobs were switched off in August 2026. That's more than eight months of both systems
running, and it was deliberate. Nobody lost a record mid-switch, and the old records stay
readable.

That's a large system, and a 10–30 person team is unlikely to need one that size. It shows what
the long end looks like when a company replaces several tools at once.

**The home-equity lender** took a different route. Deals, contacts, meetings and tasks came over
from HubSpot in a one-time import, then got checked. The team kept working while the new CRM
took over piece by piece. Each week we checked what was still going to HubSpot. Once nothing
important was left, the lender ended its HubSpot contract in 2026. It had paid about $3,000 a
month for HubSpot. Its own CRM costs under $300 a month to run.

The weekly check is the part worth copying. It gives you a clear, shrinking list of what's left,
and it tells you when you're done.

## How to get a realistic number for your own team

The fastest way to a real schedule is a look at your data. Write down three things first:

1. Your HubSpot renewal date and the notice period in your order form.
2. Every tool connected to your CRM today.
3. How many workflows, sequences and reports your team relies on.

Those answers decide most of the timeline. Here's [what a migration costs and what drives the
price](/blog/crm-migration-cost-small-business/), and how to decide
[whether to leave HubSpot at all](/blog/should-you-leave-hubspot/).

To see how a full switch went from first export to HubSpot switched off, read the
[real-estate case study](/work/real-estate-marketing/).

If you'd like a schedule for your own team, [book a free one-hour call](/book/teardown/). Bring
your renewal date. You'll leave knowing roughly how long a move would take and whether it fits
before renewal. Most switches start at $2,500 and take 1–6 months, and your team keeps working
the whole time. If your CRM only needs fixing, I'll tell you that.


## TL;DR

A 10–30 person team with clean data typically takes 4–8 weeks to move its records, history and daily screens. Whole projects run 1–6 months. Your team keeps working in the old CRM while the new one is built and checked. If you're leaving HubSpot, start about 90 days before your renewal date.

## Key Takeaways

- A 10–30 person team with clean data typically takes 4–8 weeks to move its records, history and the screens it uses every day.
- Whole migration projects take 1–6 months. More people, more connected tools and messier data push toward six months.
- There's no downtime. The team keeps working in the old CRM while the new one is built, and both run side by side until the numbers match.
- Records export from HubSpot in minutes. Notes, calls and email history need HubSpot's API, and workflows have to be rebuilt. History is what sets the schedule.
- HubSpot contracts renew automatically and can't be cancelled mid-term. Count back about 90 days from your renewal date and turn off auto-renewal first.
- The real-estate company I moved off HubSpot ran both systems for more than eight months on purpose, so nobody lost a record.

## FAQ

### How long does it take to move a small business to a new CRM?

A 10–30 person team with clean data typically takes 4–8 weeks to move its records, history and daily screens. Whole projects take 1–6 months, depending on the size of the team, the number of connected tools and how messy the data is.

### Will my team have downtime during a CRM migration?

No. The new CRM is built next to the old one while the team keeps working. Records are moved and checked, and both systems run side by side until the numbers match. The team switches on a day you pick.

### When should I start a HubSpot migration before my renewal?

About 90 days before your renewal date. HubSpot contracts renew automatically and can't be cancelled mid-term. Turn off auto-renewal early, so a slipped schedule doesn't lock you in for another year.

### What takes the longest in a CRM migration?

Activity history and automation. Contacts, companies and deals export from HubSpot as spreadsheets. Notes, calls and logged emails need HubSpot's API, and workflows, sequences and reports have to be rebuilt in the new system.

### What happens to HubSpot workflows after you downgrade?

If you downgrade all Professional and Enterprise subscriptions, workflows are turned off at once and deleted 90 days later. Sequences are also deleted after 90 days. Document or rebuild them before your renewal date.

## Related Links

- [should-you-leave-hubspot](https://advisorylabs.xyz/blog/should-you-leave-hubspot/)
- [crm-migration-cost-small-business](https://advisorylabs.xyz/blog/crm-migration-cost-small-business/)