CRM migration

Migrating from HubSpot to Salesforce: what it costs and what breaks

The record transfer is the quick part. The cost sits in everything that quietly depends on how HubSpot shaped your data.

The short answerA HubSpot to Salesforce migration for a mid market team usually takes six to twelve weeks, and implementation partners commonly quote $15,000 to $50,000. The time goes into redesigning the object model, rebuilding automation that does not translate, and reconnecting every integration. Migrate when the object model genuinely cannot represent how you sell. If the pain is configuration, rebuild in place.

When the move is worth it

Three situations justify it. Your products, pricing or entity structure have outgrown what HubSpot objects can represent, usually multi entity accounts, complex quoting or heavy custom objects. A parent company or acquirer is standardizing on Salesforce. Or you need cross object reporting and approval logic that HubSpot cannot model without workarounds.

The move also assumes somebody will own Salesforce afterwards. It is built for an organization with an administrator, and without one the new org drifts faster than the old portal did.

If the complaint is messy data, reps avoiding the CRM or reports nobody trusts, those travel with you. A migration carries the existing data model across unless somebody redesigns it, so the same problems arrive on a new platform with a new bill. The migrate or fix it page has the full test.

How the objects map

Most of the design work is a handful of decisions about where each HubSpot record should land. The biggest one is people: HubSpot has one person object, Salesforce has two.

HubSpot to Salesforce, object by object
HubSpotSalesforceThe decision to make
ContactsLeads and ContactsWhich people arrive as unqualified Leads, and which go straight to Contacts on an Account
CompaniesAccountsParent and child structure, and which domain becomes the matching key
Deals and pipelinesOpportunities, sales processes and record typesWhether each pipeline becomes a record type or the pipelines merge
Lifecycle stageLead Status plus Opportunity StageWhere the stage history lives once it is split across two objects
TicketsCasesWhether support moves at all, or stays where it is
Custom objectsCustom objectsRebuild only the ones a report or process actually reads
Owners and teamsUsers, roles and queuesMatch by email, and decide the role hierarchy before the load
Emails, calls, meetings, notesTasks and EventsHow much history to bring, and against which record

Associations need their own decision. HubSpot lets a contact sit on several companies. Salesforce gives a contact one primary account, and relating it to others needs the contacts to multiple accounts feature turned on.

What breaks in the move

  • Workflows. HubSpot workflows do not migrate. Each one has to be rebuilt, usually as a Salesforce flow, which is the right moment to retire the ones nobody can explain.
  • Source and lifecycle history. HubSpot keeps original source and stage history on the contact. Salesforce needs fields designed to hold them, or the history is gone on day one.
  • Forms and tracking. If marketing stays in HubSpot, forms keep posting there, and the connector becomes the most important integration you own.
  • Reports and dashboards. None of them come across. Rebuild only the ones somebody opens, against the new definitions.
  • Every integration. Each tool that writes to HubSpot today needs rewiring and retesting, and that list is usually longer than anyone expects.
  • Duplicates. Anything duplicated in HubSpot arrives duplicated in Salesforce, and Salesforce will not stop it unless duplicate rules are switched on before the load.

Keeping HubSpot for marketing

Many teams move sales to Salesforce and keep Marketing Hub. That works well when the handoff is designed on purpose: one system owns each field, the inclusion list decides which contacts cross, and original source is written once into a field reps cannot overwrite. When it is not designed, the sync quietly drops source and two dashboards stop agreeing. The sync page covers the settings that decide it.

A realistic timeline

Eight to ten weeks for a mid market org with reasonably clean data
WeeksWorkWhat you decide
1 to 2Inventory and design: object model, field map, the Leads and Contacts ruleHow you sell, written down
3 to 5Sandbox build: objects, record types, validation rules, flowsStage exit criteria
6 to 7Data load: deduplicated first, owners mapped, associations and activitiesHow much history comes across
8Integrations and the reports people actually useWhich tools stay
9 to 10Parallel run, cutover in an agreed window, trainingThe cutover date

Most overruns come from the data load. Deduplicate and archive in HubSpot before you move anything, because paying to migrate records nobody will open is the most avoidable cost in the project.

Questions

How long does a HubSpot to Salesforce migration take?

Six to twelve weeks for most mid market teams, depending on data volume, custom objects and how many integrations need rewiring. The data load and the integrations take longer than the build.

How much does a HubSpot to Salesforce migration cost?

Implementation partners commonly quote $15,000 to $50,000 for a mid market migration. Sapwood handles migrations inside the $4,000 a month retainer.

Should HubSpot contacts become Salesforce leads or contacts?

Decide by qualification. People who have not met your qualified definition usually arrive as Leads, and people already tied to an open opportunity or a customer account go straight to Contacts on that Account.

Can we keep HubSpot for marketing after moving sales to Salesforce?

Yes, and many teams do. It works when the connector is configured on purpose: one owner per field, a tight inclusion list, and original source written once into a field reps cannot overwrite.

Do HubSpot workflows migrate to Salesforce?

No. Each workflow has to be rebuilt, usually as a Salesforce flow. It is a good moment to retire the ones nobody can explain.

Want to talk it through?

Leave an email and I will reply myself, usually the same day. No sequence, and no calendar link unless you ask for one.

One reply from a person. Nothing else.

Got it. You will hear from hello@sapwood.io.

Would rather just book time? Here is the calendar.