Pricing and costs

9 Things That Set Your Salesforce to HubSpot Migration Cost (2026)

Nine things set a Salesforce to HubSpot migration cost: record volume, archived activities, files, custom objects, price books and more. What to count.

Ayush BothraFounding Member, MigrateX

Published 7 min read

Salesforce and HubSpot logos above a large 9 with the words things that set your migration cost and count them before you ask for a quote, for a Salesforce to HubSpot migration cost guide
On this page

A Salesforce to HubSpot migration cost is set by nine things you can count in your own org: record volume by object, activities older than 365 days, files, custom objects, contacts without an email, price books, contact roles, the history you want kept, and the integrations left running during the move. Count them before you ask for a quote.

This list is for revenue operations leads and Salesforce admins who have chosen HubSpot and are comparing ways to get there. It contains no prices. It shows what a quote is built from, so two quotes can be compared line by line. For the object mapping itself, see the Salesforce to HubSpot migration page.

What should you count before asking for a quote?

Scope: how much moves, and how much of it needs a decision first. Each driver below makes the job larger or smaller.

The nine drivers and what to count for each:

#DriverScope grows withCount this in Salesforce
1Record volume by objectObjects in scope, converted LeadsRecords per object, open and converted Leads
2Activities older than 365 daysYears of history keptTasks, Events and emails, including archived
3FilesNumber, size and versionsFiles linked to records in scope
4Custom objectsObjects that must stay objectsCustom objects still in use, your HubSpot tier
5Contacts without an emailBlank and shared emailsContacts and Leads with no email
6Price books and line itemsPrice books, products on dealsActive price books, Opportunities with products
7Contact roles and extra accountsDistinct roles, multi-account contactsRole values in use, your HubSpot tier
8Dates and field historyHistory you need on the recordTracked fields, reports using created date
9Integrations during the moveApps sharing the API limitsInstalled packages, the HubSpot sync

1. Record volume by object

What it is. The number of Accounts, Contacts, Leads and Opportunities that move, counted per object, not as one total.

Scope grows when. More objects move. Salesforce's API limits reference gives an Enterprise Edition org 100,000 API calls per 24 hours plus 1,000 per Salesforce licence, and calls from installed managed packages count against the same limit, so a large read takes more days.

Scope shrinks when. Converted Leads stay behind. Salesforce's Lead reference says a converted Lead is read-only, and the Account, Contact and Opportunity it became already carry its data.

Count. Records per object, with open and converted Leads counted separately.

2. Activities older than 365 days

What it is. Tasks, Events and emails on your records. Salesforce archives Events that ended more than 365 days ago and closed Tasks due more than 365 days ago.

Scope grows when. You keep every year of history. It also needs the most care: HubSpot cannot update existing emails, meetings, notes or tasks by import, so the activity mapping is proven on a sample before the full load.

Scope shrinks when. You set a cutoff date, for example all activities on open Opportunities and a fixed number of years for the rest.

Count. Not from a report: Salesforce Help says archived activities are not included in reports. Ask your admin for a queried count that includes archived rows, per year.

3. Files

What it is. Salesforce Files attached to Accounts, Contacts and Opportunities, and their versions.

Scope grows when. Files are many, large or versioned. A Salesforce file can be up to 2 GB through a REST multipart request, and HubSpot's file documentation accepts up to 2 GB on paid plans.

Scope shrinks when. Only the latest version moves, or only files on records in scope.

Count. Files through the records they are linked to. Salesforce warns that queries on ContentDocument and ContentVersion without an ID do not return every file a user can reach.

4. Custom objects and the HubSpot tier they need

What it is. Business-specific Salesforce objects, with their own fields and lookups.

Scope grows when. They must remain objects. HubSpot's knowledge base lists custom objects under Enterprise subscriptions only, and each custom association type gets an account-specific ID that has to be looked up.

Scope shrinks when. A custom object is no longer used, or holds a few fields that fit as properties on a company, contact or deal.

Count. Custom objects with record counts and last-modified dates, and the HubSpot subscription you have bought.

5. Contacts without an email address

What it is. Contacts and Leads with a blank, shared or placeholder email.

Scope grows when. Each one needs a key. HubSpot matches a contact on Email, Record ID or a unique-value property. Its import documentation says that in a multi-object import, identical rows with no unique identifier are treated as one record.

Scope shrinks when. The data is deduplicated before the move, or those contacts are left out.

Count. Contacts and Leads with no email, and emails used by more than one record.

6. Price books and line items

What it is. Products on Opportunities. Salesforce's reference says each OpportunityLineItem requires a PricebookEntryId, so price books and their entries sit behind every line.

Scope grows when. You run several price books or currencies. HubSpot's developer docs say a line item belongs to one single parent object and links to a product by hs_product_id, so one price per product has to be chosen.

Scope shrinks when. Deals only need their amount, with no product lines.

Count. Active price books, products, and the share of Opportunities that have line items.

7. Contact roles and contacts linked to several accounts

What it is. OpportunityContactRole records, which name the role a person plays on a deal, and AccountContactRelation records, which link one Contact to more than one Account.

Scope grows when. There are many distinct roles. In HubSpot a record has only one primary company, and roles become association labels: up to 50 per object pair, and importing them needs Professional or Enterprise.

Scope shrinks when. Roles are few, or a role stored as a contact property is enough.

Count. The role values in use, the number of Contacts with a second Account, and your HubSpot tier.

8. Original dates and field history

What it is. Created dates and the stage or field changes Salesforce tracked over time.

Scope grows when. You need history on the record. HubSpot's knowledge base says Create date is read-only for all objects except deals, so other original dates go into their own properties. Salesforce History objects are read-only, so field history can move as a note or a property, not as live history.

Scope shrinks when. Current values are enough.

Count. Reports that depend on created date, and fields with history tracking on.

9. Integrations and the HubSpot-Salesforce sync during the move

What it is. Everything else that uses the same API limits while data moves.

Scope grows when. Both CRMs stay connected. HubSpot's Smart Transfer article warns that using it and the Salesforce integration at the same time creates duplicate records in both systems. HubSpot's daily API limit for private apps, 625,000 calls on Professional and 1,000,000 on Enterprise, is shared across all apps in the account.

Scope shrinks when. The sync is paused for the load and other integrations are quiet.

Count. Whether the HubSpot-Salesforce integration is installed, and which packages and apps call each API every day.

Our recommendation: count first, then ask

Count drivers 1, 2 and 3 first, because they decide how much data moves. Then settle 4 and 7 with your HubSpot subscription in hand, since both depend on the tier. Put the answers in one table and send the same table to every provider you compare.

Two things to ask each provider in writing. First, whether rebuild work is inside the quote: Flows, Apex triggers, validation rules, reports and dashboards are configuration, not records, and are rebuilt in HubSpot. Second, whether a sample on your own records comes before you sign. Our guide to writing a data migration RFP covers the rest of the brief.

Facts checked November 15, 2026 from Salesforce: API Request Limits and Allocations, Salesforce Help: Work with Archived Activities, Salesforce Object Reference: ContentVersion, Salesforce REST API: insert or update blob data, Salesforce Object Reference: Lead, Salesforce Object Reference: OpportunityLineItem, Salesforce Help: Export Backup Data from Salesforce, HubSpot: Format import files, HubSpot: Import records for multiple objects, HubSpot: Create and edit custom objects, HubSpot: Create and use association labels, HubSpot: Edit a property value for a record, HubSpot: Supported file types and sizes, HubSpot developer docs: Line items, HubSpot developer docs: API usage guidelines and limits and HubSpot: Transfer data from other apps using HubSpot Smart Transfer. No vendor paid for this article. How we research

Salesforce to HubSpot migration cost FAQ

Why can't I get a Salesforce to HubSpot migration price without record counts?

Because the price follows what moves out of Salesforce. Two orgs with the same number of users can differ by years of archived activities, files and custom objects. The nine counts above come from your own org, your admin can pull them, and with them a quote can be fixed instead of estimated.

Do I need HubSpot Enterprise to migrate from Salesforce?

Only for some data. HubSpot's knowledge base lists custom objects under Enterprise subscriptions, so Salesforce custom objects that must stay objects need that tier. Association labels, which hold contact roles, need Professional or Enterprise. Accounts, Contacts, Opportunities, activities and files do not depend on Enterprise.

Does moving fewer years of history make the migration smaller?

Yes, it reduces what moves. Decide the cutoff per object, starting with activities. One option is to keep every Account, Contact and open Opportunity, and limit closed Opportunities and activities to a set number of years. What stays behind can be kept as an export file.

How do we pull these counts out of Salesforce?

Your admin can count records per object with queries, and must include archived rows for activities. For a rough row count, the built-in Data Export also works. Each export route, and what it leaves out, is compared in 4 ways to export Salesforce data.

Can the HubSpot Salesforce integration do the migration instead?

HubSpot positions it for ongoing use of both CRMs. Its Smart Transfer article points ongoing Salesforce use to that integration and warns that running both creates duplicate records. If you plan to switch Salesforce off, a one-time migration with a reconciliation report is the cleaner route.

Send your nine counts, get a fixed quote within 24 hours

MigrateX is a managed data migration service on its own AI migration platform, SOC 2 Type II, GDPR and HIPAA compliant. Send us the table of counts. You get 100 of your own records in HubSpot, free, so you can check deals, contact roles, activities and files before you commit, and a fixed quote within 24 hours. Send your counts. Scope for each side is on the Salesforce and HubSpot platform pages. Going to Microsoft instead? Read Salesforce to Dynamics 365 Sales: objects, owners and history.

Written by

Ayush Bothra

Founding Member, MigrateX

Ayush writes about ITSM platforms, pricing and what it takes to move a service desk to a new platform without losing its history.