Systems integration
HubSpot Salesforce integration problems: causes and fixes
Why HubSpot Salesforce integration problems happen, who fixes each common sync error, and a field ownership sheet and weekly routine to keep them down.
Marketing runs HubSpot, sales runs Salesforce, and the HubSpot Salesforce integration between them worked well for a year. Now a rep in Olathe says the lead she called this morning shows a different phone number in each system, the marketing report counts fewer opportunities than the sales forecast, and the error count on the HubSpot sync page keeps climbing. Nobody owns the problem, because it sits between two teams.
Most HubSpot Salesforce integration problems come from four places: a Salesforce rule or automation that rejects the update, values that do not match between the systems, duplicate records, and a connected user without the right access. The fix is to decide which system owns each field, then work the error list on a schedule.
What causes HubSpot Salesforce integration problems
The integration acts in Salesforce as one user, the connected user. HubSpot’s own setup guide says that user’s Salesforce permissions decide what HubSpot can do through the sync. Updates HubSpot sends can be rejected by the same checks a person would face, such as duplicate rules, validation rules or required fields.
That is why most errors start with an ordinary change made on one side without telling the other. Sales adds a new opportunity stage. An admin makes a field required for a forecast report. A rep leaves and is deactivated with hundreds of records still in their name. Each change is sensible in Salesforce, and each one can stop records coming over from HubSpot.
HubSpot groups the errors into associations, custom code, duplicates, permissions, picklists, property mappings and property values. Its list of common Salesforce sync errors gives the cause and fix for each. API calls are a separate limit. HubSpot notes that syncing a single contact can take up to four Salesforce API calls, and the integration uses only the share of your Salesforce allowance allocated to HubSpot, so a busy sync can run short.
Common sync errors and who fixes them
In a company of 50 or 200 people, the person who sees the error is often not the person who can fix it. This table matches HubSpot’s common errors to a likely owner.
| What the sync page shows | Usual cause | Who fixes it |
|---|---|---|
| Custom code error (validation rule or flow) | A rule or automation in Salesforce rejects the update | Salesforce admin |
| Missing or restricted picklist value | A value exists in one system but not the other | Both admins, agreeing one list |
| Inactive Salesforce owner | Records still belong to a deactivated rep | Sales ops reassigns them |
| Email already in use, or duplicate rule | Two records for one person | Marketing ops and sales ops together |
| Insufficient access or field permission | The connected user cannot see or edit a field | Salesforce admin |
| Missing or invalid opportunity stage | A Salesforce stage is missing from the HubSpot pipeline | Both admins |
| String too long, or invalid email | One bad value on one record | Whoever owns the record |
Fix the cause before you resync. HubSpot lets you resync up to 100 errors at a time. Resyncing first usually produces the same errors again.
Decide which system owns each field
Every mapped field has a sync rule. HubSpot’s field mapping guide defines four. Prefer Salesforce unless blank sends a HubSpot value only when Salesforce has none. Always use Salesforce never sends HubSpot data across. Two-way syncs in both directions, and the most recent value wins. Don’t sync leaves the field unsynced in both directions.
Many teams set two-way without much thought, and it causes most of the confusion. Most recent wins is fine for a phone number. It is risky for lead status, lifecycle stage or owner, where a marketing workflow and a sales rep can overwrite each other all day. HubSpot also notes that the owner mapping can only be two-way and that owner values must match exactly. Owners are also where departed reps show up, as the Inactive Salesforce owner error.
Write a one page field ownership sheet. For each mapped field, record the system that owns it, the sync rule, and who may change its list of values. A common starting point: marketing owns source, campaign and subscription fields; sales owns owner, stage, amount and the account relationship; basic contact details are two-way only if both teams truly edit them. Do not map one HubSpot property to several Salesforce fields. HubSpot warns this can cause overwrites or sync loops.
You can also limit what goes to Salesforce. An inclusion segment means only HubSpot records that meet your criteria sync, so students, job seekers and vendors stay out of the sales team’s lead list. Leads and contacts created in Salesforce can still create HubSpot contacts.
A weekly sync check that keeps errors down
Check it once a week. Half an hour is often enough.
Open Sync Health. In HubSpot, go to Settings, Integrations, Connected Apps, Salesforce, then the Sync Health tab. Read the errors by type, not record by record. A batch of errors of one type often shares one cause.
Check API use. The same tab shows calls used in the past 24 hours against the amount allocated to HubSpot. If you are close to the limit, raise the allocation or reduce what syncs before records start waiting.
Review the change log. Any new picklist value, stage, record type, required field or departed rep should reach both admins before it goes live. A distributor in West Des Moines that adds a stage for its busy season should add it in both pipelines on the same day.
Know who the connected user is. If the connection runs under a person’s own login, find out now. If that person leaves, someone has to reconnect the integration under another user, and HubSpot says that user needs permissions equal to or greater than the previous one. Our guide on what to do when your Salesforce admin quits covers the wider handover.
Fix the sync or consolidate onto one system
Keeping both systems is often the right call, whether you are a software company in Boulder or a manufacturer in Fargo. If marketing gets real value from HubSpot, the ownership sheet clears most errors, and the remaining trouble sits in a handful of fields, repair the sync.
Consolidation deserves a hard look when the same records still conflict every week after clear rules, when marketing and sales keep separate definitions of a qualified lead and their reports never agree, or when an acquisition has left you with two CRMs and two sets of customers. Consolidation is a project in its own right: data has to move, marketers have to learn new tools, and automations have to be rebuilt.
We work with midsize companies, roughly 10 to 500 people, across Nebraska, Iowa, Kansas, Colorado and the wider Midwest, from our office in Omaha. Midsize companies often run lean, with one marketer and a part time Salesforce admin, which is exactly when ownership slips. If you want an outside view before you decide, our two to three week, fixed price diagnostic maps how data moves between your systems and ends with a costed roadmap you own, with no obligation to have us build it.
Common questions
Why do HubSpot and Salesforce show different values for the same contact?
Usually the sync rule. Under two-way, the most recent edit wins in both systems. Under Prefer Salesforce unless blank, HubSpot’s value stays behind once Salesforce has one. Check the rule for that field before assuming the sync is broken.
Which Salesforce editions work with the HubSpot integration?
HubSpot says it needs a Salesforce edition with API access, or Salesforce Professional, and it does not support Group Edition. On the HubSpot side, it needs a Professional or Enterprise subscription.
Can we stop some HubSpot contacts from reaching Salesforce?
Yes. Set an inclusion segment so only records that meet your criteria sync from HubSpot to Salesforce.