Salesforce HubSpot Integration Services
The native connector links HubSpot and Salesforce in an afternoon. Keeping leads, contacts, companies and deals in step for years — without duplicates, overwritten fields or a burned API limit — is the part we are hired for.
01
The setup
How to connect HubSpot and Salesforce
HubSpot and Salesforce connect through HubSpot’s native Salesforce connector: install it from the HubSpot App Marketplace, approve the HubSpot package in Salesforce, choose a sync user, then map fields and decide which records sync. The install takes an afternoon. The decisions behind it are what take the time.
Before you start
- Editions. HubSpot Professional or Enterprise, and a Salesforce edition with API access — Enterprise, Unlimited or Performance, or Professional with the API add-on.
- Admin access on both sides. A HubSpot super admin, and a Salesforce administrator to install the package.
- A dedicated integration user in Salesforce. Changes made by the sync are attributed to it, which keeps audit history readable, and its permissions decide what HubSpot can see.
- A backup. Export both systems first. The first sync can update thousands of records in minutes, and there is no undo button.
The steps
- In HubSpot, open the App Marketplace, find Salesforce and click Install. Log in with the Salesforce integration user when prompted.
- Install the HubSpot integration package in Salesforce, for admins only or for all users, and add the HubSpot Visualforce module to lead and contact layouts if reps should see HubSpot activity there.
- Choose what syncs: contacts and leads, companies to accounts, deals to opportunities, tasks and activities. Set an inclusion list so only the records you choose reach Salesforce.
- Map fields and set a sync rule on each one: Prefer Salesforce unless blank, Always use Salesforce, Two-way or Don’t sync.
- Set the API call limit HubSpot may use, so the connector cannot consume the allowance your other integrations need.
- Test on a handful of records — create, edit and convert in each system — before letting the full sync run.
02
The connector
What the native HubSpot–Salesforce connector does — and where it breaks
The connector is good. For a single marketing team handing leads to a single sales team, it is usually all you need. It syncs contacts and leads, companies and accounts, deals and opportunities, tasks, and on HubSpot Enterprise, custom objects. It maps owners by email address and logs HubSpot activity against the Salesforce record. Where it breaks is predictable.
Duplicate records
HubSpot keys contacts on email address. Salesforce allows the same email on several leads and contacts, and keeps leads and contacts as separate objects. Sync without matching rules and an agreed lead-conversion policy, and one person becomes three records. The fix is upstream: inclusion lists, Salesforce duplicate rules, and a decision about whether HubSpot creates leads or contacts — then merging what is already there.
Fields overwritten in both directions
A two-way rule on a field both teams edit means whichever system saved last wins, and nobody notices until a report is wrong. Every field needs an owner. Most should be one-way; very few should be two-way.
The Salesforce API limit
Every sync consumes Salesforce API calls. A large inclusion list, frequent property updates from marketing automation and a low daily allowance together can use it up, and then every other integration in the org starts failing. Budget the calls before go-live, not after the first outage.
Pipelines, associations and custom logic
Deal stages map to opportunity stages per pipeline, and a record type or pipeline added later is missed until someone maps it. Company associations built by HubSpot’s domain matching can fight a Salesforce account hierarchy. And anything conditional — route this lead differently by region, hold that one until it is qualified — is beyond what sync rules express.
When the connection itself fails
Most connection errors come from the integration user: an expired password, a lost permission, or an IP restriction on its profile. HubSpot’s sync health page lists failed records with the Salesforce error attached. Read it weekly, or have someone alerted when failures appear.
03
Your options
Your three HubSpot–Salesforce integration options
There are three ways to integrate HubSpot and Salesforce. Most teams should start with the first and stay there; the other two exist for the problems the connector cannot solve.
| Option | Best for | Where it stops | Relative cost |
|---|---|---|---|
| Native HubSpot connector | One marketing team handing leads to one sales team; standard objects | Conditional routing, multi-system flows, strict API budgets | Included in HubSpot Pro and Enterprise; setup effort only |
| Middleware (Workato, MuleSoft) | HubSpot and Salesforce plus an ERP, billing or data warehouse in the same flow | Adds a licence and a platform someone has to own | Middleware licence plus build |
| Custom API build | Unusual objects, strict data residency, or logic no tool expresses | You own the code, its monitoring and its upgrades | Highest build cost; no licence |
When to bring in a partner
If you are setting up the connector for the first time with a clean database, HubSpot’s documentation will get you there. Bring us in when the sync has already run for a while and the data shows it — duplicates, overwritten fields, pipelines out of step — or when HubSpot is one of several systems that need to agree about a customer. We write down which system owns each object and field, fix the data that exists, configure the connector or build the middleware to that contract, and leave you a sync health dashboard your ops team can read.
HubSpot is one of the Salesforce integrations we build; if the job is mostly development, you can also hire a Salesforce developer by the hour or the month.
04
The problem
Why people call us about this.
A
The same person exists three times across HubSpot and Salesforce, and sales and marketing count them differently.
B
A field someone fixed in Salesforce is overwritten by HubSpot the next time the record syncs.
C
The connector has quietly used your daily Salesforce API allowance and other integrations start to fail.
05
What’s covered
The Salesforce we actually configure.
Most HubSpot–Salesforce problems are decisions nobody made at setup: which system owns each field, what happens to a lead that converts, and which records should sync at all. We make those decisions in writing first, then configure to them.
06
How it runs
Five phases, and what you see at the end of each.
01 · Week 1
Inventory
What exists, who owns it, and which system is really the source of truth. Almost always surfaces something nobody knew was live.
A written map
02 · Weeks 2–3
Contract
The design in writing, with each decision and its reversal cost named. This is where we argue with the brief — before money is spent.
A signed scope
03 · Middle
Build
Built against the contract and reviewed against it. You see working software every two weeks, in your own sandbox.
Fortnightly demos
04 · Late
Prove
Volume testing at twice expected load, deliberate failure injection, and a replay run with your team watching.
A test evidence pack
05 · Final week
Hand over
Runbook, monitoring, escalation path and a named owner on your side — then a month watching it together before we step back.
Runbook and owner
07
First call
Thirty minutes. Three answers.
You speak to a certified architect, not a sales engineer. No deck, no discovery fee, and no obligation to go further — you leave the call with three things whether you hire us or not.
Whether this is even the right line
About a third of the time it is not, and we say so. Usually the ask is custom development when the real problem sits in the data model underneath.
A shape and a range
Roughly how long, roughly how many people, and the band it falls in. The firm number follows discovery about two weeks later, and it holds.
The two risks we would flag
The things most likely to blow the timeline on a project like yours — named on the call, before anyone has signed anything.
Book it for this week.
Pick a slot directly in the calendar — most questions get answered inside the thirty minutes.
08
FAQ
Asked on nearly every call.
Can HubSpot and Salesforce be integrated without middleware?
Yes. HubSpot’s own Salesforce connector covers leads, contacts, companies, deals, tasks and, on Enterprise, custom objects. Middleware or a custom build is worth it only when you need logic the connector cannot express, or several other systems in the same flow.
Which HubSpot and Salesforce editions does the connector need?
A HubSpot Professional or Enterprise subscription, and a Salesforce edition with API access — Enterprise, Unlimited or Performance, or Professional with the API add-on. Check both before planning anything else.
Why does the integration create duplicate records?
HubSpot deduplicates contacts on email address and Salesforce does not, and Salesforce keeps leads and contacts as separate objects. Without inclusion lists, matching rules and a decision about lead conversion, the same person arrives more than once.
How long does a HubSpot–Salesforce integration project take?
A clean connector setup with agreed field ownership usually takes two to four weeks. Fixing a sync that has already run for a year — merging duplicates and repairing overwritten data — takes longer, and we size it after looking at both systems.
Other lines