Salesforce to HubSpot: migrate, integrate or stay

For teams with a Salesforce renewal coming up: what a move to HubSpot costs, and why most take 8 to 12 weeks.

Neighbourhood team member in a black NBH tee, smiling, on a coral shape

Migrate, integrate or stay put, and a straight answer on which.

Salesforce and HubSpot are both CRMs: the system where your team keeps every customer, every deal and every conversation. Plenty of businesses end up with one, wondering about the other, or running both at once.

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 document that says which system is in charge of each piece of information. 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 project manager who plans your move or connection is the person who builds it and trains your team.

New to this? Six words this page uses

Objects and records

An object is a type of thing the CRM keeps, like companies or deals. A record is one of them: one company, one deal.

Fields

The pieces of information on each record, like a phone number or a deal’s value. HubSpot calls them properties.

Migration

Moving your records out of Salesforce and into HubSpot, once, so you can switch Salesforce off.

Integration

Keeping both systems and connecting them, so a change in one copies across to the other. That copying is called a sync.

Field map

A written list of every field, where it goes in HubSpot, and which system wins when the two disagree.

Admin

The person allowed to change how the CRM is set up: its fields, stages and reports. In Salesforce this is often a paid specialist.

Businesses we build for

Flight Centre TikTok MINI Tyro Plungie Raine & Horne CooperSurgical National Storage Selleys Taylor Tasmanian Walking Company Esri Australia Play Matters Higgins Coatings Gro Iress

Should you migrate to HubSpot, integrate the two, or stay on Salesforce?

If you are comparing HubSpot vs Salesforce, the answer is usually one of these three. A Salesforce renewal is a good moment to work it out properly, before the contract decides for you.

Migrate to HubSpot

Usually fits when. Your team uses a small part of Salesforce, changes need an admin, or marketing already runs in HubSpot

What we do. Map every object, field, owner and stage on paper, migrate with history, rebuild the reports people still open

What you end up with. One system your own people can run

HubSpot tier to check. Enterprise if you rely on Salesforce custom objects

Integrate both

Usually fits when. Sales lives in Salesforce, marketing lives in HubSpot, and both are worth keeping

What we do. Agree which system owns each record and field, set the sync to respect it, test on your own records

What you end up with. Two systems that agree on every customer

HubSpot tier to check. Professional or Enterprise on at least one hub

Stay on Salesforce

Usually fits when. Salesforce is heavily customised, tied into other platforms and run by people who know it well

What we do. Tell you so, and connect HubSpot where marketing needs it

What you end up with. No migration you did not need

HubSpot tier to check. The same as integrate, if you connect

How we place a business on the first call. The answer is confirmed once we have seen how your team actually uses Salesforce.

We are a HubSpot partner, so ask us to show our working. Our longer comparison is HubSpot vs Salesforce for 60 to 200 people, which includes where Salesforce genuinely wins.

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.

  • Accounts

    In HubSpotCompanies

    What to watchDuplicate accounts merged before they arrive

  • Contacts and leads

    In HubSpotContacts

    What to watchHubSpot matches contacts on email, so two people sharing one address need a decision first

  • Opportunities

    In HubSpotDeals, in a pipeline

    What to watchStages mapped to how your team sells today

  • Users and owners

    In HubSpotUsers and record owners

    What to watchOwners matched person by person, so nobody loses their book

  • Notes, tasks and calls

    In HubSpotActivity on the record it belongs to

    What to watchThe cut-off date for history is agreed up front. Logged email history is scoped per migration, because of its volume and attachments

  • Custom objects

    In HubSpotCustom objects

    What to watchThese need a HubSpot Enterprise subscription, so we check it early

  • Reports, dashboards, flows and workflow rules

    In HubSpotRebuilt as reports, dashboards and workflows

    What to watchOnly the ones someone still uses. Fields nobody fills in stay behind

The usual mapping. Your field map is written for your portal, and you approve it before the test migration.

What we built, and what it moved.

A National Storage facility

National Storage

99.99%

Data sync rate, up from 0.3%

230+

Centres across Australia and New Zealand

53.5%

Email open rate

The Agency office reception

The Agency

$5M

Annual commission trajectory

3.4×

Growth in compliant reach

44

Qualified deals in two months

The Flint Group team

Flint Group

$2B

Loans closed since the work began

75%

Faster onboarding for new team members

100%

Staff adoption as one source of truth

How does a Salesforce to HubSpot migration run?

  1. Read what you have

    A list of everything in your Salesforce: objects, fields, owners, sales stages, reports and automations, and a look at which of them anyone actually uses.

  2. Agree the map

    Every object and field gets a home in HubSpot, or a decision to retire it. You sign off the map, and how far back the history goes, before anything moves.

  3. Build HubSpot first

    Sales stages, fields and saved views are set up around how your team sells now, so records land somewhere that makes sense.

  4. Test migration

    A sample moves first and we check records side by side with Salesforce before the full run.

  5. Full migration, then a final catch-up

    Everything goes across while your team keeps working in Salesforce. Records that changed in the meantime go across in one last pass just before you switch.

  6. Train, then switch

    Your team is trained on HubSpot 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.

  7. Clean up what came across

    Old 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 how much data you have and how many custom objects. You will know your length once we have seen a sample of your data. 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.

Bring us the pipeline nobody trusts and the reports that never agree.

Book a call

HubSpot partnership

We are a HubSpot Diamond Partner and we have been building on the platform for more than a decade, across every Hub.

What that means when HubSpot sits next to Salesforce:

  • A team that has already solved it. However your portal is behaving, we have almost certainly seen it before.
  • A direct line into HubSpot. For faults that are genuinely on the HubSpot side, where no configuration will fix them.
  • Enough time on the platform to know its edges. We know which parts of HubSpot to trust and which to build over.

17 HubSpot Impact Awards sit behind those three, including Technical Expertise, Platform Excellence, Platform Migration Excellence and Product Excellence. Each one is a real client’s system, with the figures attached. We are also Certified HubSpot Trainers, and we run Brisbane’s official HubSpot User Group.

See the HubSpot work

Meet the engineers

We change big portals in place.

When the HubSpot portal is large, starting again is usually riskier than fixing it, since three things tend to be true at once:

  • Integrations nobody documented. We map them by reading what the portal actually does, because nobody remembers.
  • A sales team mid quarter. Selling carries on right through it.
  • A board reading the same dashboard every Monday. Reporting keeps running while the model underneath it changes.

So we make the changes in place and in the right order, and reporting stays standing while we do. A restart would mean asking the company to stop selling for a quarter.

Clients include ASX listed companies, household names and businesses running national operations on portals we architected. Most had a live pipeline and a team mid quarter while we worked, so we plan around that.

  • 17HubSpot Impact Awards, 2020 to 2026
  • 300+Businesses helped
  • 11+Years as HubSpot partners
The Agency office reception
“Cassy was absolutely amazing. She didn’t just help ‘set up’ HubSpot, but took the time to understand our business, our people, and the unique challenges of recruitment in real estate.”
Trent P Trent P Head of Brand, The Agency · Read the case study

Your CRM stays yours, and it can stay in Australia.

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.

data moves one way owner of the field
How a HubSpot Salesforce integration settles who owns what HubSpot owns the fields marketing captures, such as form answers and email engagement. Salesforce owns the opportunities and sales activity. Both feed a written field map in the middle, which says which system wins for each field. A new lead passes from HubSpot to Salesforce, and the outcome of the deal passes back from Salesforce to HubSpot. HubSpotOwns form answers andmarketing engagement Written field mapWhich system wins,field by field SalesforceOwns opportunities andsales activity A new lead goes to sales The deal outcome comes back to marketing
The field map is the part most integrations skip. You see it, in writing, before anything syncs, and the next admin can read it.
  • 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

    Each time the two systems swap data, it counts against a daily allowance Salesforce sets, called the API limit. One contact sync can use up to four of those calls

From HubSpot’s Salesforce integration requirements, last updated by HubSpot on 18 June 2026. Check them against your own subscriptions before you plan.

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 marketing’s record of which channel first brought each lead in.

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. A fair comparison counts all of these:

  • 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

What to put side by side before a renewal. Current licence prices are on HubSpot’s pricing page and Salesforce’s Australian pricing page.

Salesforce moves start from around $12,000, plus the HubSpot licence. The final price is set once we have seen a sample of your data, 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.

Our two minute take on HubSpot against Salesforce, Pipedrive and Zoho. Watch it on YouTube.

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 old Salesforce fields from HubSpot, merged thousands of duplicate contacts into one profile per member, and built 30+ custom fields 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.

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.

All fields are required except the newsletter tick box.

Please enter your first name.
Please enter your last name.
Please enter a valid email.
Please add a quick note so we can help.

We reply within one business day. By submitting you agree to our Privacy Policy.

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.