How to fix a broken HubSpot to Salesforce sync
Most HubSpot to Salesforce sync problems are configuration drift rather than connector failure. The sync is running. Records are moving. The wrong records, the wrong fields, or in the wrong direction.
This sequence works for native HubSpot to Salesforce sync. The same logic applies to third-party connectors with minor adjustments.
Steps
- 1
Confirm the sync is actually running
Check sync health in HubSpot (Data Management > Integrations > Salesforce > Sync activity). Connector errors here mean the sync is broken at the transport layer, not the configuration layer. Resolve those first.
- 2
Read the inclusion list
Open the Salesforce inclusion list and confirm it still matches your operational definition of which contacts should sync. Inclusion lists go stale fast as segmentation evolves; this is the most common root cause.
- 3
Audit field mappings field by field
For every mapped field, verify the source-of-truth direction is correct, the conflict-resolution rule matches the business rule, and the field types are compatible on both sides. Pay particular attention to picklists and multi-select fields.
- 4
Reconcile a sample of records
Pull twenty records that should have synced in the last 48 hours. Compare them in HubSpot and Salesforce side by side. Discrepancies tell you where the failure mode lives.
- 5
Check Salesforce-side validation rules
Records that fail Salesforce validation rules silently fail to sync. The HubSpot side reports green; the Salesforce record never appears. Validation rule changes upstream of the audit are a frequent cause.
- 6
Document and prevent recurrence
Write down the mapping decisions and conflict rules in a place the team will look. Add the inclusion list and field schema to your change-control process so the next schema change does not silently break the sync.
Common pitfalls
- !Trusting the connector status without sampling records.
- !Treating each field mapping as an isolated decision rather than a system.
- !Assuming Salesforce validation rules apply only to manual record creation.
Frequently asked questions
QWhat does a missing record in Salesforce usually mean?+
QWhy do field updates overwrite good data?+
QShould we use the native connector or a third-party tool?+
Need senior help applying this in your environment?
Reading the guide is one thing. Translating it into the live system you actually have to operate on Monday is another. That's where the conversation usually starts.