The record transfer is the quick part. The cost sits in everything that quietly depends on how HubSpot shaped your data.
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.
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 | Salesforce | The decision to make |
|---|---|---|
| Contacts | Leads and Contacts | Which people arrive as unqualified Leads, and which go straight to Contacts on an Account |
| Companies | Accounts | Parent and child structure, and which domain becomes the matching key |
| Deals and pipelines | Opportunities, sales processes and record types | Whether each pipeline becomes a record type or the pipelines merge |
| Lifecycle stage | Lead Status plus Opportunity Stage | Where the stage history lives once it is split across two objects |
| Tickets | Cases | Whether support moves at all, or stays where it is |
| Custom objects | Custom objects | Rebuild only the ones a report or process actually reads |
| Owners and teams | Users, roles and queues | Match by email, and decide the role hierarchy before the load |
| Emails, calls, meetings, notes | Tasks and Events | How 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.
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.
| Weeks | Work | What you decide |
|---|---|---|
| 1 to 2 | Inventory and design: object model, field map, the Leads and Contacts rule | How you sell, written down |
| 3 to 5 | Sandbox build: objects, record types, validation rules, flows | Stage exit criteria |
| 6 to 7 | Data load: deduplicated first, owners mapped, associations and activities | How much history comes across |
| 8 | Integrations and the reports people actually use | Which tools stay |
| 9 to 10 | Parallel run, cutover in an agreed window, training | The 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.
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.
Implementation partners commonly quote $15,000 to $50,000 for a mid market migration. Sapwood handles migrations inside the $4,000 a month retainer.
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.
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.
No. Each workflow has to be rebuilt, usually as a Salesforce flow. It is a good moment to retire the ones nobody can explain.
Leave an email and I will reply myself, usually the same day. No sequence, and no calendar link unless you ask for one.
Would rather just book time? Here is the calendar.
We use browser storage to run the site and to understand how it is used. You can accept all or necessary only. See our privacy notice.