HubSpot to Salesforce Integration · CRM & Platform Systems

HubSpot to Salesforce integration done so it survives the next field rename.

Two best-of-breed systems, one of the most common operational fault lines in B2B.

The HubSpot to Salesforce integration is famously easy to install and famously fragile in practice. The connector behavior, sync filters, and field mapping decisions made at install determine whether the next three years of marketing-to-sales handoff is smooth or painful.

Discuss the engagement

What goes wrong with this integration specifically

The native HubSpot to Salesforce connector is good. It is also configurable in ways that quietly become wrong over time. Sync filters narrow the universe of records that move between systems; once they drift out of alignment with the actual segmentation, MQLs stop appearing in Salesforce or appear without the context the AE needs.

Field mapping decisions made at implementation get layered with new fields over time, often without coordinating direction. The marketing team adds a HubSpot property; the sales team adds a Salesforce field with a similar but not identical purpose; both think the other side is going to populate the data; neither does.

We work through these by starting with the sync filters, working through field-by-field mapping with an explicit owner per field, and putting governance around schema changes so the same drift doesn't restart immediately.

The HubSpot to Salesforce reconciliation pass

Every audit we run covers all of these. Most environments need work in at least three.

1
Inclusion lists / sync filters
Which Salesforce records flow into HubSpot, and which HubSpot contacts are eligible to sync. The filters here govern the entire data universe.
2
Field-level mapping
Every synced field, with an explicit source-of-truth owner and direction. Where conflicts get resolved.
3
Lead/contact lifecycle
Lead vs. contact behavior in Salesforce, lifecycle stage in HubSpot, and the rules that move records between the two.
4
Campaign membership
HubSpot enrollment translated to Salesforce campaign influence, with attribution behavior consistent across both.
5
Activity timeline
Email opens, form submissions, and engagement events appearing on the Salesforce record where AEs actually look.

Matching service

See the same work from the platform and delivery angle.

The service page covers scope, approach, and what an engagement actually delivers.

Salesforce CRM →

Frequently asked questions

QDo we need HubSpot Marketing Hub Enterprise to do this well?+

Not necessarily. Several of the more aggressive sync features sit in Enterprise tiers, but a well-architected Pro-tier integration is dramatically more reliable than a poorly-architected Enterprise one.

QShould we use HubSpot's native connector or a third party?+

Native is the default. Third-party (Workato, custom) only when there's a specific behavior the native connector doesn't support and the operational cost of working around it is high.

QHow long does a HubSpot to Salesforce repair take?+

Three to eight weeks depending on how much accumulated drift there is, and whether the engagement includes ongoing governance after the repair.

QCan you set this up greenfield?+

Yes. Greenfield is faster and cleaner: six to eight weeks for a full implementation including governance documentation.

QWhat about Pardot/Account Engagement and Salesforce?+

Different problem shape. Pardot is owned by Salesforce, so the integration is fundamentally tighter: but the governance discipline is the same.

QDo you handle Salesforce CPQ or other Salesforce-side complexity?+

Yes when it touches the marketing-to-sales seam. Pure Salesforce-side configuration we'd typically partner with a Salesforce specialist on.

QWhat's the most common mistake in this integration?+

Treating the inclusion list as a set-and-forget. The list of records eligible to sync needs to evolve with the segmentation strategy; teams that don't revisit it end up with a sync that no longer reflects how the program actually works.

QCan you fix our duplicate record problem?+

Yes. Deduplication strategy: both prevention and remediation: is part of the standard scope.