crm sync conflict: hubspot overwrote salesforce data error
Resolves HubSpot-Salesforce sync conflicts where HubSpot overwrote Salesforce data URIs set field-level sync direction and conflict rules. Use when Salesforce values get clobbered by the sync. Not for one-time import overwrites.
TL;DR
The sync's field mapping lets HubSpot win on fields where Salesforce should be the source of truth. Open the sync's field mappings, set the direction per field (Salesforce to HubSpot, HubSpot to Salesforce, or most-recent), and re-sync. Blanket bidirectional sync guarantees data loss.
Error
(No error; the symptom is Salesforce field values replaced by older or blank HubSpot values after a sync.)Steps
- Identify the clobbered fields and their values before and after the sync. Expected: you know exactly which fields lost data.
- Open the integration's field mappings for those fields. Expected: you see the sync direction, often bidirectional by default.
- Set the correct direction per field: Salesforce wins for owner, stage, and close date; HubSpot wins for marketing fields. Expected: each field has an explicit source of truth.
- For genuinely shared fields, use most-recent-wins if the integration supports it. Expected: the latest edit survives regardless of side.
- Fix the clobbered values (restore from history or the source) and re-run the sync. Expected: values stay correct on both sides.
When to use
- Salesforce data gets overwritten by HubSpot values.
- Fields flip-flop between two values on every sync.
- After enabling a new bidirectional field mapping.
When not to use
- One-time import overwrites (fix the import mapping, not the sync).
- Salesforce-to-Salesforce overwrites (different problem).
Tool compatibility
- HubSpot-Salesforce native sync; field mapping settings.
- Sync history and error logs.
Variant phrasings
sync overwrote the wrong side
Direction misconfigured; set per-field direction.
field values flip-flopping
Bidirectional sync with no conflict rule; pick a winner.
Why it happens
Default mappings are often bidirectional, which means the last writer wins with no notion of authority. Two systems editing the same field on different schedules produce a ping-pong of overwrites.
Edge cases
- Blank values overwriting real values is the worst case; some mappings treat blank as "no change" and some as "clear the field".
- Sync filters can exclude records from one direction; check the inclusion rules too.
- Historical values are recoverable from field history; enable it before you need it.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_MAlOsUu0Zlr-vygBsrv13A