Why does Salesforce sync keep overwriting HubSpot contacts?
The short answer
Check whether multiple Salesforce leads or contacts share the same email address before changing field rules in HubSpot. HubSpot documents that these duplicates can cause a contact to sync with the Salesforce record most recently updated, repeatedly replacing its information.
Key points
- Inspect the linked Salesforce record, not just the visible HubSpot contact.
- A person with different email addresses may not be recognized as a duplicate.
- Review deletion settings before merging anything.
- Test a small approved set before resuming a broader sync.
Official references
Separate a duplicate problem from a field rule problem
For a B2B sales team, a lead created by a campaign and a contact created by a salesperson can represent the same person. HubSpot's Salesforce documentation says that matching uses email addresses. When multiple Salesforce records share an email, the initial match uses the first record returned, not a guaranteed preferred record. Later updates can change which duplicate supplies the data. Compare record IDs and modification times before deciding that an integration needs replacing.
What to ask an implementation partner to demonstrate
- 01Identify every Salesforce lead and contact in the affected sample, including alternate email addresses.
- 02Record the Salesforce ID currently linked to the HubSpot contact and export the fields needed for recovery.
- 03Inspect whether deleting a Salesforce record can also delete its HubSpot contact.
- 04Choose the surviving record with the data owner. HubSpot recommends keeping the record currently syncing as the primary record when merging in Salesforce.
- 05Run a controlled update in each direction and confirm the intended record, owner, consent data and associations remain intact.
When cleanup is not enough
If records continue to appear twice, review every process that creates leads and contacts, including imports, forms and sales tools. Ask whether selective sync can exclude unsuitable records while the team resolves identity rules. Do not treat a temporary pause or exclusion as a permanent repair. The acceptance criterion is that a repeat submission and a later sales edit still resolve to the intended person without losing history.
From our team
How Proven ROI helps
Proven ROI provides CRM implementation and system integration services. A scoped investigation can separate record matching problems from field ownership rules before a team commits to migration or replacement.
Talk to a real personCommon follow up questions
- Should we delete the duplicates directly in HubSpot?
- Not as the first step. Inspect Salesforce duplicates and the connector's deletion settings first. HubSpot warns that merging a secondary Salesforce record can delete the corresponding HubSpot contact when deletion sync is enabled.
- Does this describe every HubSpot connector?
- No. This behavior is documented for the HubSpot Salesforce integration. Other connectors need their own matching and deletion rules checked.