Salesforce to HubSpot: migrate, integrate or stay
Migrate, integrate or stay put, and a straight answer on which.
If your team uses a small part of Salesforce and needs an admin for every change, moving to HubSpot usually makes sense. If Salesforce is built deeply around how you operate, keep it and connect HubSpot to it, with a written field map that says which system owns each field. We do both, and we will tell you which one fits.
We have been a HubSpot partner since 2015 and a Diamond Partner since 2019, and we have worked with 300+ businesses. Your PM is your builder: the person who scopes your migration or integration is the person who builds it and trains your team. Below is how we decide, what moves, how the sync works, and what it costs.
Last checked October 2026.
Should you migrate to HubSpot, integrate the two, or stay on Salesforce?
Most people searching HubSpot vs Salesforce are really asking one of three questions. A Salesforce renewal is a good moment to answer it properly, before the contract decides for you.
| Migrate to HubSpot | Integrate both | Stay on Salesforce | |
|---|---|---|---|
| Usually fits when | Your team uses a small part of Salesforce, changes need an admin, or marketing already runs in HubSpot | Sales lives in Salesforce, marketing lives in HubSpot, and both are worth keeping | Salesforce is heavily customised, tied into other platforms and run by people who know it well |
| What we do | Map every object, field, owner and stage on paper, migrate with history, rebuild the reports people still open | Agree which system owns each record and field, set the sync to respect it, test on your own records | Tell you so, and connect HubSpot where marketing needs it |
| What you end up with | One system your own people can run | Two systems that agree on every customer | No migration you did not need |
| HubSpot tier to check | Enterprise if you rely on Salesforce custom objects | Professional or Enterprise on at least one hub | The same as integrate, if you connect |
We are a HubSpot partner, so ask us to show our working. Our longer comparisons are HubSpot vs Salesforce for 60 to 200 people, which includes where Salesforce genuinely wins, and HubSpot or Salesforce at 100 people.
What moves in a Salesforce to HubSpot migration?
Every Salesforce object gets a HubSpot home on paper before anything moves. Records bring their calls, meetings, tasks and notes with them, and how much logged email comes across is agreed per migration. Reports and automations do not copy across, so we rebuild the ones your team still opens and leave the rest behind.
| In Salesforce | In HubSpot | What to watch |
|---|---|---|
| Accounts | Companies | Duplicate accounts merged before they arrive |
| Contacts and leads | Contacts | HubSpot matches contacts on email, so two people sharing one address need a decision first |
| Opportunities | Deals, in a pipeline | Stages mapped to how your team sells today |
| Users and owners | Users and record owners | Owners matched person by person, so nobody loses their book |
| Notes, tasks and calls | Activity on the record it belongs to | The cut-off date for history is agreed up front. Logged email history is scoped per migration, because of its volume and attachments |
| Custom objects | Custom objects | These need a HubSpot Enterprise subscription, so we check it early |
| Reports, dashboards, flows and workflow rules | Rebuilt as reports, dashboards and workflows | Only the ones someone still uses. Fields nobody fills in stay behind |
How does a Salesforce to HubSpot migration run?
- Read what you have. An inventory of objects, fields, owners, stages, reports and automations, and a look at which of them anyone actually uses.
- Agree the map. Every object and field gets a HubSpot home, or a decision to retire it. You sign off the map and the history cut-off before anything moves.
- Build HubSpot first. Pipelines, properties and views are set up around how your team sells now, so records land somewhere that makes sense.
- Test migration. A sample moves first and we check records side by side with Salesforce before the full run.
- Full migration, then the delta. The full export goes across, your team keeps working, and the records that changed in the meantime go across in a final pass just before switch-over.
- Train, then switch. Your team is trained on the new portal while it is built, so switch-over is never their first look at it. We suggest keeping Salesforce read only for a while so people can check nothing is missing.
- Clean up what came across. Legacy Salesforce fields are removed from HubSpot so nobody reports off the wrong one. We did exactly that for Chief Executive Women, along with rebuilding the Salesforce reports their team relied on.
Most Salesforce moves are planned as a full implementation, which runs 8 to 12 weeks including the migration, depending on data volume and custom objects. You will know your length once we have seen a sample export. The phases and the week by week plan are on HubSpot implementation and onboarding, and the general approach to a CRM move is on CRM implementation and migration.
How does the HubSpot Salesforce integration work?
HubSpot’s own Salesforce integration syncs contacts, companies, deals, activities and other supported records in both directions. It works well once someone has decided which system owns each field and which records should sync at all. Left on its defaults, it copies every disagreement from one side to the other, and whichever system writes last wins.
| Requirement | What HubSpot says |
|---|---|
| HubSpot subscription | Professional or Enterprise on Marketing, Sales, Service, Data or Content Hub, or Smart CRM |
| Salesforce edition | An edition with API access, or Salesforce Professional. Group Edition is not supported |
| Who installs it | A Salesforce system administrator with API Enabled and the other listed permissions |
| Instances | One Salesforce instance per HubSpot account |
| API calls | The integration uses part of your daily Salesforce API limit, and one contact sync can take up to four calls |
Where integrations go wrong
Two examples from portals we have been asked to look at, both anonymised. At a not-for-profit, couples shared one email address in Salesforce. HubSpot matches contacts on email, so the sync kept colliding, and in their words, “we know that it’s a problem with the data in Salesforce, but HubSpot gets blamed for it.” At another business, a sync was overwriting where leads came from: a lead that arrived from Google search read as an offline source two days later, which wiped out the first-touch attribution marketing reported on.
Both are ownership problems, and both are fixed the same way: decide which system wins for each field, write it down, and test it on your own records before the sync is switched on.
Is HubSpot cheaper than Salesforce, and what does a move cost?
It depends on how many seats you need, which hubs or clouds you are on, and how much of each your team actually uses. Licence prices are only one line. A fair comparison counts all of these:
| Cost line | What to count |
|---|---|
| Licences | Seats people actually log into, and whether some only need to read. One business told us losing Salesforce’s read-only seats was a big part of why HubSpot appealed. |
| Admin time | Who changes a field, a stage or a report, and how long it takes. A prospect put it to us plainly: “You need a degree in Salesforce to be able to set it up.” |
| Add-ons and connectors | Paid apps, marketing tools bolted onto the CRM, and the tier you need for features like custom objects |
| The move itself | Mapping, migration, rebuilding reports and training, paid once |
| The contract | When the Salesforce term ends, and what a renewal locks you into |
Salesforce moves start from around $12,000, plus the HubSpot licence. The final price is set once we have seen a sample export, because the number of objects, the amount of history and how clean it is decide the cost. What a HubSpot build costs a 100 person Australian business explains what moves a build price.
What do teams that left Salesforce say about it?
LDK Healthcare, a Brisbane retirement living and aged care brand, used Salesforce before we built its HubSpot CRM. Anthony Browne at LDK: “As a prior user of Salesforce I would never go back as HubSpot mixed with Neighbourhood support has delivered beyond our expectations.”
At Chief Executive Women, we removed legacy Salesforce fields from HubSpot, merged thousands of duplicate contacts into one profile per member, and built 30+ custom properties for membership. The team got 29 hours a week back.
A clinic group came to us less than a year after moving to Salesforce, before more of the business was built around it. The team found it cumbersome, hard to customise and expensive for what they used, so we moved them to HubSpot.
Read next.
Guides from the team on choosing between the two, testing a migration, and picking a partner for it.
- HubSpot vs Salesforce for 60 to 200 people
- HubSpot or Salesforce at 100 people
- Testing a migration in a HubSpot sandbox
- Which HubSpot partner tier a Salesforce move needs
- HubSpot CRM support options in Australia
- CRM implementation, without the old mess
- HubSpot implementation and onboarding
- HubSpot partner in Australia, based in Brisbane
What people ask about Salesforce and HubSpot.
Can HubSpot and Salesforce work together?
Yes. HubSpot’s Salesforce integration syncs contacts, companies, deals and activity in both directions. It needs a HubSpot Professional or Enterprise subscription and a Salesforce edition with API access. It works well once someone has decided which system owns each field. We set those rules with you, write them down, and test them on your own records first.
Should we move from Salesforce to HubSpot?
Sometimes. A move makes sense when your team uses a small part of Salesforce, struggles to change anything without an admin, or already runs marketing in HubSpot. When Salesforce is built deeply around how you operate and the people running it know it well, keeping it and connecting HubSpot is often the better answer.
What moves in a Salesforce to HubSpot migration?
Accounts, contacts, leads, opportunities, owners, notes, tasks and calls, plus the custom objects you actually use. Custom objects in HubSpot need Enterprise. Reports, dashboards, flows and workflow rules do not copy across, so we rebuild the ones your team still opens.
Do we lose our history when we leave Salesforce?
No. Calls, meetings, tasks and notes come across attached to the record they belong to, up to a cut-off date you agree. Logged email history is scoped per migration, because of its volume and attachments. We check a sample of records side by side after the move, and suggest keeping Salesforce read only for a while so your team can confirm nothing is missing.
How long does a Salesforce to HubSpot migration take?
We plan most as a full implementation, which runs 8 to 12 weeks including the migration. Where yours lands depends on data volume, custom objects and how clean the data is, and we confirm it once we have seen a sample export.
How much does a Salesforce to HubSpot migration cost?
Salesforce moves start from around $12,000, plus the HubSpot licence. The final price is set once we have seen a sample export, because the number of objects, the amount of history and how clean it is decide the cost.
Is HubSpot cheaper than Salesforce?
It depends on your seats, your hubs or clouds and how much of each you use. Count admin time, add-ons and the contract term as well as licences. We are a HubSpot partner, so ask us to show our working with your real setup.
How do you decide which system owns a record?
By asking who creates it and who changes it. If sales updates opportunities in Salesforce, Salesforce owns them. If marketing captures contacts through HubSpot forms, HubSpot owns those fields. We agree what happens when both sides change the same value and hand you the map in writing.
Tell us how your Salesforce is set up.
A few lines is enough. You will get a human reply within one business day. After a first call with Matt, one PM plans it and builds it.
Got it, there.
We will be back to you within one business day. Rather not wait? Pick a time with Matt below and skip the email round, or call 1300 71 61 41.