# Does HubSpot Have a Native Salesforce Integration? What It Syncs and Where It Stops

Yes. HubSpot ships a native, two-way Salesforce integration built and maintained by HubSpot, with no third-party middleware required. It syncs contacts, companies, and deals to Salesforce contacts or leads, accounts, and opportunities, along with activities and custom field mappings. It needs HubSpot Professional or Enterprise and a compatible Salesforce edition. Field-level and object-level control is where most setups need extra thought.

If you run HubSpot as your marketing engine and Salesforce as your CRM, this question tends to come up right before a renewal: does the sync actually hold, or will someone be exporting CSVs by quarter three. The short answer is that the integration is real and genuinely native. The longer answer is that native covers a lot, then stops at a specific line worth knowing before you commit.

It does. HubSpot maintains its own Salesforce connector, installed as a managed package on the Salesforce side and configured from HubSpot. You are not buying a Zapier recipe or standing up MuleSoft to make the two talk. The sync is bi-directional by default, so a lead that fills out a HubSpot form can create or update a Salesforce record, and a stage change in Salesforce can flow back to HubSpot.

That "native" label matters for two reasons. First, HubSpot owns the maintenance, so Salesforce releases and API version changes are handled for you. Second, the connector understands both object models out of the box, which is the slow part of any custom build. For the wider context on how this fits HubSpot's connector ecosystem, our HubSpot integrations explained guide maps the full picture.

The connector maps HubSpot's core objects onto Salesforce's standard objects. Here is the practical map.

Source: HubSpot Knowledge Base, Salesforce integration overview, 2026.

The part teams underestimate is that last row. Every custom field mapping carries its own direction (HubSpot to Salesforce, Salesforce to HubSpot, or two-way) and its own conflict rule. Get twenty of those wrong and reporting quietly drifts apart between the two systems.

The connector is included with HubSpot, but not on every plan. You need HubSpot Professional or Enterprise on the relevant Hub. On the Salesforce side you need an edition with API access, which in practice means Enterprise or Unlimited, or Professional with the API add-on enabled.

Two people run the install: a Salesforce administrator with permission to add a managed package, and a HubSpot super admin. If your Salesforce edition lacks API access, the native connector cannot authenticate at all, and that is the single most common reason a "quick" setup stalls on day one. Confirm the edition before you schedule the work.

By default you can sync every eligible record, but most teams should not. HubSpot offers an inclusion list: an active list that decides which contacts are allowed to sync to Salesforce. It is the difference between pushing your entire marketing database into the CRM and pushing only sales-ready records.

Three settings decide how clean this stays:

1. Sync rules per object. Each object gets a direction. Marketing usually wants two-way on contacts, one-way on some fields.

2. Conflict resolution per field. When both systems change the same field, you pick the winner: prefer HubSpot, prefer Salesforce, or use the most recently updated value. Pick deliberately, because "most recent" can let a stale import overwrite good CRM data.

3. Deduplication on email. The connector matches on email. When both systems believe they own the email address and the matching is loose, you get duplicate contacts, and cleaning those up after the fact is genuinely painful.

I have watched a lead-status field mapped two-way quietly break funnel reporting, because HubSpot lifecycle stage and Salesforce lead status were fighting over the same record on every sync. The fix was making that mapping one-way and letting one system own the truth. Our write-up on native Salesforce integration benefits covers why single-system ownership beats clever two-way rules.

Native handles the standard object model well. It runs out of room in a few predictable places:

Custom objects sync is limited and gated to higher tiers, so a bespoke object in Salesforce may not map cleanly. Many-to-many relationships, non-standard routing, and approval logic that has to run mid-sync are outside what a field-mapping UI can express. And if your Salesforce org has been heavily customized over years, the standard connector will cover 80% and leave the last 20% to you.

That last 20% is where a custom or native-object bridge earns its place. The honest framing: use the native connector for everything it does well, and only build custom for the specific objects and rules it cannot reach. That decision, native connector versus custom versus middleware, is the same one we walk through in native integration vs. iPaaS. This is also where the native connector differs from the deeper setup mechanics in our HubSpot Salesforce integration guide, which walks the configuration screen by screen.

A short sequence that avoids the usual day-one stalls:

1. Confirm your HubSpot plan is Professional or Enterprise and your Salesforce edition has API access.

2. Install the HubSpot managed package in Salesforce with an admin account.

3. Build your inclusion list before turning on contact sync, so you never push the whole database.

4. Map objects first, then fields, setting a direction and conflict rule on each.

5. Turn on sync for a small test segment, verify records match, then widen.

6. Watch the first full sync for duplicates and fix matching before scaling.

For how this connector sits alongside HubSpot's other CRM connections, see HubSpot CRM integrations guide.

Is the HubSpot and Salesforce integration free? The connector itself carries no separate fee, but it is only available on HubSpot Professional and Enterprise plans, and it requires a Salesforce edition with API access. So it is included rather than free: you need the right tier on both sides.

Which HubSpot plan do I need for the Salesforce sync? HubSpot Professional or Enterprise on the relevant Hub. Starter and free plans do not include the native Salesforce connector. On the Salesforce side you need Enterprise or Unlimited, or Professional with the API add-on.

Is the sync real-time or batched? It is near-real-time rather than instant. Changes typically propagate within roughly ten to fifteen minutes, and high-volume periods can add delay. If a workflow depends on a change appearing in the other system within seconds, design around that lag.

Can I sync custom objects between HubSpot and Salesforce? Standard objects sync fully. Custom object sync is limited and gated to higher HubSpot tiers, and heavily customized Salesforce orgs often need a custom bridge for their bespoke objects. Plan for standard objects natively and the rest custom.

Does it create duplicate records? It can, when email matching is misconfigured or both systems believe they own the same contact. The connector matches on email, so tightening your matching and inclusion rules before the first full sync is the way to avoid a duplicate cleanup later.

About the author. Sunny Chauhan is the founder of appnigma.ai, where we build native Salesforce apps and integrations without glue code: direct, observable connections instead of a stack of hand-maintained callouts. He is a Salesforce-certified Platform Developer II who spent the better part of a decade building integrations and managed packages, including work at Zennify and Salesforce, before founding appnigma. That background is why the field-mapping and ownership questions here come before the setup screens.

Which field would you let one system own outright: lifecycle stage, lead status, or deal amount? That answer usually tells you how clean your sync will stay.

<!-- Related reading: /blogs/hubspot-salesforce-integration-guide /blogs/hubspot-integrations-explained /blogs/native-salesforce-integration-benefits /blogs/native-integration-vs-ipaas-mulesoft-boomi-zapier /blogs/hubspot-crm-integrations-guide -->