How long does a Salesforce to HubSpot migration take? Timelines by object count

The question usually arrives with a date attached. A Salesforce renewal is four or five months out, the decision to move to HubSpot has been made, and somebody needs to know whether the migration fits inside the window. The useful answer is not one number. It is a range, and a short list of things that decide where in the range you land.

Every HubSpot limit quoted below was read on HubSpot's own knowledge base on 1 October 2026. INSIDEA's timelines are the ones it publishes on its migration timelines page and in its Salesforce to HubSpot migration playbook. Where a figure is an estimate and not a measurement, the text says so.

How long does a Salesforce to HubSpot migration take?

Six to twelve weeks for most mid-market companies, from kickoff to cutover and hand-off. A clean org with standard objects finishes near six. INSIDEA's published standard plan is about twelve weeks, because it assumes Apex and Flows to translate and includes three weeks of training and hand-off. Heavily customised orgs run longer.

The two numbers describe the same method at different scopes. The playbook gives six to twelve weeks and says the driver is the state of the Salesforce data and the number of connected systems, not the number of HubSpot Hubs. The standard plan on the Salesforce to HubSpot migration page is written at twelve weeks because most Salesforce orgs that have been lived in for a few years carry custom automation.

Does the number of records change the timeline?

Less than most buyers expect. Loading data is the short part of a migration. A paid HubSpot account imports files of up to 512 MB and 1,048,576 rows, up to 10,000,000 rows per day, and up to 80,000,000 rows per day through the imports API. A typical mid-market CRM fits inside one day's allowance many times over.

Those limits are on HubSpot's import file requirements page, read on 1 October 2026. The same page lists the free-tier limits, which are much lower: 20 MB files and 500,000 rows per day.

Here is the worked example. A financial technology company moved 63,017 records from Salesforce to HubSpot with INSIDEA: Leads, Contacts, Accounts and Opportunities, with every object relationship and the full history of emails, calls, tasks and meetings kept. 63,017 rows is about 6 percent of a single import file's row limit. On mechanics alone the load is an afternoon. The project took just under three months, against a Salesforce contract that was expiring. The weeks went into the audit, the mapping, rebuilding reports and workflows, and validating the result, not into moving rows.

Record count matters in three narrower ways:

• Activity history. Emails, calls, notes and meetings usually outnumber the records they belong to several times over, and each one must land on the right record with the right owner and date.
• Deduplication. The more records, the longer the clean-up before mapping. This is audit time, and it is cheaper before the import than after.
• Sync during the parallel run. HubSpot's Salesforce integration uses Salesforce API calls, and HubSpot's integration documentation (read 1 October 2026) says a single contact sync can take up to four calls per record. A large first sync is paced to stay inside the org's daily allowance.

How does the timeline change with the number of objects in scope?

Every object you add needs a mapping decision, a build in HubSpot, an import step and a validation check, so object count is what moves the date. Standard objects only sits at six to eight weeks. Adding line items, Cases and Campaigns brings it to eight to twelve. Custom objects with Apex and Flows mean twelve weeks or more.

Read this table as a planning guide, not as measured averages. The twelve-week and ten to fourteen week figures are INSIDEA's published plans. The first two rows split the playbook's six to twelve week range by scope; INSIDEA has not published a per-object average, and the audit in the first two weeks is what turns a range into a date.

Three objects deserve a note. The Lead object has no HubSpot equivalent; a lead becomes a contact at an early lifecycle stage, so conversion logic and routing are rebuilt, not copied. Opportunity products do not backfill through the native sync, so past line items are imported as their own step. And custom objects need a HubSpot tier that supports them and a schema that is designed, not copied one to one.

What does each week of a 12-week migration cover?

Four phases. Weeks 1 to 2 are the audit and plan. Weeks 3 to 7 are the build in a HubSpot sandbox. Weeks 8 to 9 are cutover in three waves under a 24 to 48 hour freeze. Weeks 10 to 12 are training and hand-off. The build is the longest phase on every Salesforce migration.

After week twelve there are 30 days of post-cutover support with weekly check-ins. The broader HubSpot build that often runs beside a migration is laid out on the implementation timeline page.

What makes a Salesforce migration take longer than planned?

Four things, and only one of them is build time: automation that has to be translated because it cannot be copied, integrations that must be rebuilt, data that needs cleaning before it can be mapped, and decisions or access arriving late from the customer side. The last one is the most common delay.

Apex, Flows and validation rules are read one by one, mapped to a HubSpot workflow or a programmable workflow, and tested. AppExchange apps are reviewed individually; some have native HubSpot replacements and some need a custom integration. None of that is visible from a record count, which is why a quote given before an audit is a guess.

On the customer side, three things keep a plan on its dates: one named person who can decide what a lead, a stage and closed won mean, Salesforce admin access in week one, and a team that will accept a short data freeze at cutover.

When should you start if your Salesforce contract is ending?

Work back from the renewal date and leave room for the parallel run. A twelve-week plan plus 30 to 90 days of Salesforce in read-only mode means starting five to six months before the contract ends. Starting three months out is possible for a standard-object org, and tight for anything custom.

The parallel run is the part buyers leave out. INSIDEA typically keeps Salesforce in read-only mode for 30 to 90 days after cutover so the team can check historic data, and sunsets it once nothing is found missing. If the contract ends the week of cutover, that safety net is gone.

Sometimes the overlap is longer by choice. At nOps, a cloud cost optimisation company, INSIDEA ran Salesforce and HubSpot in parallel for six months to see how reps used Salesforce before recommending consolidation, then moved every contact, company, deal and historical activity and retired it.

And sometimes the answer is not to migrate yet. If the org carries five or more years of complex Apex, depends on AppExchange apps with no HubSpot equivalent, or is locked in by a procurement or regulatory commitment for the next year, staying on Salesforce and syncing it to HubSpot is the better call.

What does it cost, and who does the work?

INSIDEA scopes a Salesforce to HubSpot migration as a fixed fee, from $2,000, with the number, the scope and the timeline written down before work begins. HubSpot-certified experts do the audit, the build and the cutover. The customer supplies decisions, access and a data freeze.

The fee follows the same drivers as the timeline: objects in scope, automation to translate, integrations to rebuild. The implementation cost page has the breakdown, and the implementation cost post walks through the cost drivers.

A small, clean org with few integrations can be moved in-house with HubSpot's import tool. The case for a partner grows with custom objects, connected systems and how much the reporting depends on history.

Where INSIDEA fits

INSIDEA is an Elite HubSpot Partner, rated 4.99 across 500+ verified reviews, and holds HubSpot's CRM Data Migration Accreditation, which HubSpot grants after reviewing delivered migration work. What that credential means, and how to check it on any partner's directory listing, is on the CRM Data Migration Accreditation page.

On a Salesforce migration that looks like an audit before a quote, a build in a sandbox before any data moves, cutover in three waves with same-day rollback, and 30 days of support afterwards. If your renewal date is already on the calendar, bring it to the first call. The plan is built backwards from it.