HubSpot Salesforce Integration: Why Your Numbers Don’t Match, and How to Fix It

Lead count from HubSpot: 412.
Same report from Salesforce, five minutes later: 367.
Pipeline review: tomorrow at nine.

The HubSpot Salesforce integration is supposed to keep marketing and sales on the same numbers. In most companies it doesn't, and nobody notices until a meeting like that one.

Your two systems are almost certainly out of sync. What matters is how far, and whether it's changing decisions.

Why they drift apart

HubSpot and Salesforce weren't built to mirror each other. Marketing wants engagement and lifecycle stages. Sales wants pipeline and activity. The integration sits in the middle, and it doesn't run itself.

The sync goes one direction for some fields, both for others, and not at all for the rest. The mapping was set up once, usually by someone who has since left. Fields get added on one side and never mapped on the other. A contact gets merged in one system and duplicated in the other.

Neither team sees it, because each lives in its own tool, until a rep calls a lead marketing disqualified six months ago.

Ask who set up the field mapping. If the answer is a name nobody recognizes, start here.

Four common HubSpot Salesforce integration failures

Lead source gets lost. HubSpot captures UTMs and lead source on the contact. Salesforce has its own Lead Source picklist. If they weren't mapped on purpose, the value either never arrives or lands in a "Web" bucket that tells you nothing.

Lifecycle stage and lead status disagree. HubSpot has lifecycle stages. Salesforce has Lead Status and Opportunity Stage. They look easy to keep in sync and almost never are. Marketing thinks someone is an MQL, sales marked them Not Qualified, and the nurture that should have started never does.

Activity lives in one place. Email clicks in HubSpot. Calls and meeting notes in Salesforce. Both teams make decisions with half the history.

Duplicates split the story. Two Leads for one person, or a Lead and a Contact, or two HubSpot contacts with different emails. Now the email engagement is on one record and the form fills are on the other, and your score is working from half the data. (A Salesforce Lead syncing to a HubSpot Contact is normal. That's how the integration maps people.)

How to audit the integration

  1. Check the field mapping. List every HubSpot property that's supposed to sync. Confirm it's mapped, the direction is right, and the field types match. A text field syncing into a restricted picklist fails every time the text isn't an allowed value, and you'll only see that in the error log.
  2. Compare 50 to 100 records. Pick contacts that exist in both systems. Check lead source, lifecycle stage, company and last activity date. The mismatch rate tells you how bad it is.
  3. Open the sync error log. I rarely meet a team that checks it. It's full of records that tried to sync and failed, usually a required Salesforce field that was blank or a picklist value one side doesn't have. They pile up for months.
  4. Check workflows that depend on the other system. Anything that triggers on Salesforce data (or the reverse) can break without telling anyone when a mapping changes.

What clean looks like

  • Lead source is captured on every contact, mapped to a standard field in both systems, and never overwritten after the first value.
  • Lifecycle stage and lead status move together, with written definitions for each stage and who moves a record forward.
  • Duplicates get merged on a schedule, not when they finally cause a scene.
  • One person owns it. Not "marketing ops and sales ops together." One person who knows the integration, watches the error log, and gets an alert when failures spike.

Put the owner's name in the description on the sync settings, where the next admin will find it.

What a broken sync costs

When the two systems disagree, attribution and scoring break. Nurtures fire at the wrong time or not at all. Reps get leads they already worked. Every pipeline review becomes a debate about whose number is right.

The cost is hard to see. The campaign that got cut because attribution was wrong. The lead that went cold because a follow-up never fired. The deal the rep lost without the full history.

Most of it traces back to the field mapping and the error log, which is why the audit above starts there.

Want a second set of eyes?

Book a Health Check

Two weeks, fixed price. You get a ranked list of what's distorting your pipeline data, from the CRM sync to lifecycle stages, and how to fix each one.

Book a fit call

Not ready to talk? Run the free audit first.

The newsletter

Notes from the Field.

Every other week, one broken thing and how I’d fix it.

One email every other week · unsubscribe anytime · Privacy policy