HubSpot and Salesforce are the two systems companies most often end up running at the same time: marketing and sales built up in HubSpot, an enterprise sales motion or a parent company standardized on Salesforce. When both hold customer records, keeping them in agreement stops being a nice-to-have. A rep working an opportunity in Salesforce and a marketer scoring the same contact in HubSpot need to be looking at the same truth.
This guide covers the HubSpot Salesforce integration end to end: what the native connector does, how to set it up, exactly where it stops, and how to tell when your setup has outgrown it and a custom build is the better answer. It is a companion to the broader guide to HubSpot integrations, focused on the one connection people ask about most.
In this article
1.
2.
3.
4.
5.
6.
7.
8.
9.
Why Run HubSpot and Salesforce Together
Most teams do not choose to run both on purpose. They arrive there: marketing lives in HubSpot, an enterprise or field sales team lives in Salesforce, or an acquisition brings a second CRM into the building. Once that happens, the two systems hold overlapping records, and the cost of them disagreeing is real. Leads worked in HubSpot need to reach the Salesforce reps who close them, and the outcomes those reps record need to flow back so marketing knows what actually worked.
The point of connecting HubSpot and Salesforce is not to move data for its own sake. It is so a marketer and a rep looking at the same customer see the same story, and neither is acting on a record the other already changed.
What the Native HubSpot Salesforce Connector Does
HubSpot ships a native Salesforce integration, included on its Professional and Enterprise tiers, and for a standard setup it covers the essentials well.
Maps the core objects
HubSpot contacts sync to Salesforce leads and contacts, companies to accounts, and deals to opportunities. Activities like emails and calls can sync too, so the timeline of an account is not split across two tools.
Per-field sync direction
Each field mapping can be one-way from HubSpot to Salesforce, one-way the other direction, or two-way. You also set which system wins when both change the same field, so you are not guessing who overwrote what.
Inclusion lists
An inclusion list controls which HubSpot contacts are eligible to sync to Salesforce, so you push the records that matter rather than your entire database. This keeps Salesforce clean and stays within its limits.
A sync health view
The connector shows sync status and surfaces errors, so when something stops flowing you have a place to look. It reports problems, though it does not resolve them for you.
How to Set Up the HubSpot Salesforce Integration
The native setup is a guided flow. At a high level it looks like this.
- 1
Confirm both sides qualify
Check that you are on HubSpot Professional or Enterprise and that your Salesforce edition has API access. You also need a Salesforce user allowed to install a connected app.
- 2
Install the connector from the App Marketplace
Add the Salesforce integration from the HubSpot App Marketplace and authenticate the Salesforce account you want to sync with. HubSpot installs a managed package on the Salesforce side.
- 3
Define field mappings and direction
Map HubSpot properties to Salesforce fields, and for each one choose the sync direction and the tiebreaker system. Start with the standard mappings HubSpot suggests, then adjust for your fields.
- 4
Set the inclusion list
Decide which HubSpot contacts are eligible to sync to Salesforce using an inclusion list, so you control what crosses over instead of pushing everything.
- 5
Turn it on and watch the sync health page
Enable the sync and monitor the health page for the first cycles. Early errors are usually mapping or validation issues that are easy to fix before they compound.
For a straightforward two-system setup with standard objects, that is genuinely all it takes, and there is no reason to build anything custom.
Where the Native Connector Stops
The native connector is a general-purpose tool, and general-purpose tools have edges. These are the ones teams hit.
Signs you have reached the connector's limits
Custom objects. The connector is built around standard objects. If your process depends on custom objects on either side, its support is limited compared to a tailored build.
Multiple Salesforce orgs. It connects one HubSpot account to one Salesforce org. Multi-org Salesforce setups, common after acquisitions, are outside its model.
Conditional or transformed logic. If you need to transform values in flight, route records by condition, or apply mapping logic more complex than a field-to-field rule, you are past what the connector expresses.
More than two systems. The moment the sync needs to involve a third system, like a billing tool or a data warehouse, a two-system connector is the wrong shape.
Control over timing and errors. Teams that need tighter control over sync timing, ordering, or how errors are handled and retried tend to outgrow the connector's own schedule.
None of these mean the native connector is bad. They mean your requirements have moved past a general connector and into territory that a purpose-built integration is designed for.
Native Connector vs Custom Integration
The choice is not about which is better in the abstract. It is about which one fits the sync you actually need.
If you are syncing contacts, companies, and deals between one HubSpot account and one Salesforce org with field-level rules, use the native connector. It is included in your subscription, quick to set up, and there is nothing to maintain. Do not build what you can turn on.
When you need custom objects, more than one Salesforce org, conditional or transformed mappings, or a sync that reaches beyond these two systems, build it properly. A custom integration fits your exact logic, can be monitored, and has an owner, which matters when the sync is load-bearing for revenue.
What It Costs
The native connector has no separate price. It is included in HubSpot Professional and Enterprise, though you do need qualifying editions of both platforms, and the Salesforce side must have API access.
A custom HubSpot Salesforce integration is a one-time build cost plus ongoing maintenance, scoped to the work: how many objects, whether custom objects are involved, one org or several, two systems or more, and how the sync handles conflicts and errors. The number teams underestimate, as with any integration, is the maintenance. A Salesforce admin changes a picklist, HubSpot renames a property, an API version is deprecated, and a sync that no one owns quietly breaks.
A HubSpot Salesforce sync is not a project you finish. It is a piece of infrastructure that has to survive both platforms changing underneath it. The build is the easy part. Keeping it correct is the job.
That is why we productized it. StackTie builds a custom HubSpot Salesforce integration for a fixed fee and then maintains it on a flat monthly retainer, so it keeps working as both systems evolve instead of becoming the sync everyone is afraid to touch.
Common Sync Problems and How to Avoid Them
When a HubSpot Salesforce sync misbehaves, it is almost always one of a handful of causes. A good integration is designed against them from the start.
Salesforce API limits
Large syncs can exhaust Salesforce's daily API allocation, and records stop flowing. A proper integration batches work, backs off, and queues rather than dropping data.
Expired or reduced authorization
The connected app's access lapses or an admin narrows its permissions, and the sync halts. The fix is detection and an alert, not discovering it days later.
Broken field mappings
Someone edits a property or a picklist on either side and a mapping silently stops matching. Resilient syncs validate mappings and fail loudly when a field disappears.
Salesforce validation rules
Records that violate a Salesforce validation rule get rejected on arrival. The integration needs to catch these, report which records failed and why, and let you correct them.
The native connector will show you many of these on its sync health page. The difference with a well-built custom integration is that it is designed to handle them, retry what it can, and tell a human about what it cannot.
Need a HubSpot Salesforce sync that holds up?
When the native connector cannot express your logic, StackTie builds a custom HubSpot Salesforce integration for a fixed fee and maintains it for a flat monthly retainer. Live in 14 days or it's free. Book a free audit.
The Bottom Line
For most teams, connecting HubSpot and Salesforce starts and ends with the native connector: standard objects, one org, field-level rules, included in your plan, nothing to maintain. Turn it on and move on. The moment your requirements reach past that, custom objects, multiple orgs, real mapping logic, a sync that touches more than these two systems, or one that is important enough to need monitoring and an owner, a custom integration is the better call. Whichever you choose, treat the sync as infrastructure that has to survive both platforms changing, because that, not the initial setup, is where these connections live or die.
