CRM integration

When the HubSpot and Salesforce sync stops agreeing

Two systems, one record, and a value that changes depending on which one updated last.

The short answerMost sync problems trace back to a few settings nobody revisited after setup: fields set to two-way where one system should own the value, an inclusion list that lets the wrong contacts cross, no rule for which system may create companies, and source fields overwritten when a lead converts. All of them are visible in the integration settings, and none of them needs a new tool.

How the connector decides which value wins

Every mapped field has a sync rule, and HubSpot documents four of them (HubSpot knowledge base):

The four sync rules
RuleWhat it doesUse it when
Prefer Salesforce unless blankHubSpot writes only when the Salesforce field is empty, and Salesforce values overwrite HubSpotSalesforce owns the value, but HubSpot can fill a gap once
Always use SalesforceHubSpot never writes to Salesforce, and Salesforce values overwrite HubSpotSalesforce is the only source, such as owner or stage
Two-wayWhichever system updated most recently wins, and deletions sync both waysGenuinely shared fields, which are rarer than they look
Don't syncNothing passes between the systemsFields that should live in one place only

Two-way is the setting people choose because it feels safe. It is the one that produces the coin flip: two systems take turns overwriting the same value, and the record shows whichever job ran last.

The five problems we find most often

Source gets overwritten at conversion

Marketing captures original source on the HubSpot contact. A rep then sets Lead Source in Salesforce from a picklist, and with a two-way mapping the rep's value replaces marketing's. The fix is to write original source once into its own Salesforce field, mapped as Prefer Salesforce unless blank and locked against edits, so HubSpot fills it once and nothing replaces it.

Duplicates created across the two systems

HubSpot deduplicates contacts by email. Salesforce allows duplicate leads unless duplicate rules are switched on, and the same person can exist as both a Lead and a Contact. When the connector cannot find a clean match it creates a record, and the duplicate count climbs on the Salesforce side.

An inclusion list that is too wide, or too narrow

The inclusion list decides which HubSpot contacts sync to Salesforce. Too wide, and every newsletter subscriber becomes a Salesforce lead nobody will work. Too narrow, and engaged contacts never reach a rep. Build it on your written lead definition rather than on whoever set it up two years ago.

Companies nobody owns

HubSpot can create companies automatically from email domains. Letting those flow into Salesforce as new accounts produces accounts with no owner and no territory. Decide which system is allowed to create companies, and match on normalized domain before anything is created.

Sync errors nobody reads

Records that fail validation rules, required fields or a picklist value that does not exist in Salesforce never sync, and the integration settings list them quietly. A weekly owner for that list catches most of the drift before it reaches a report.

The order to fix it in

  • Name one owning system for every mapped field, in writing.
  • Set each sync rule to match that owner, and move two-way fields to a one way rule wherever you can.
  • Rebuild the inclusion list on the written lead definition.
  • Decide which system may create companies and accounts, and match on domain first.
  • Give the sync error list a named owner and a weekly review.
  • Backfill source and associations on the records the old settings damaged.

Heavy two-way mappings also consume Salesforce API calls on every update. Cutting mappings nobody reads is the cheapest performance fix in the integration.

Questions

Why does HubSpot keep overwriting our Salesforce data?

Usually because the field is mapped as two-way, so whichever system updated most recently wins. Change the rule to match the system that should own the value.

Which sync rule should we use for lead source?

Write original source once into a dedicated Salesforce field mapped as Prefer Salesforce unless blank, and lock it against edits, so HubSpot fills it once and nothing overwrites it.

What is the HubSpot Salesforce inclusion list?

The rule that decides which HubSpot contacts sync to Salesforce. It should match your written lead definition, so reps see engaged people and not every subscriber.

How do we stop the sync creating duplicate leads?

Switch on Salesforce duplicate rules, decide when a person is a Lead or a Contact, match on email and domain, and clear the existing duplicates before tightening the sync.

Where do I see HubSpot Salesforce sync errors?

In the Salesforce integration settings inside HubSpot, which list records that failed and why. Give that list an owner and review it weekly.

Want to talk it through?

Leave an email and I will reply myself, usually the same day. No sequence, and no calendar link unless you ask for one.

One reply from a person. Nothing else.

Got it. You will hear from hello@sapwood.io.

Would rather just book time? Here is the calendar.