HubSpot Salesforce Field Mapping: Sync Direction & Conflict Resolution
Field mapping is where most HubSpot-Salesforce integrations go wrong. Map the wrong direction and you'll overwrite good data. Skip conflict resolution and you'll create endless sync loops.
This guide covers the strategic decisions behind field mapping—not just how to click buttons in HubSpot.
The Three Sync Directions
| Direction | What It Means | When to Use |
|---|---|---|
| HubSpot → Salesforce | HubSpot is the source of truth. Changes in HubSpot overwrite Salesforce. | Marketing-owned fields: lead source, campaign, form submissions |
| Salesforce → HubSpot | Salesforce is the source of truth. Changes in Salesforce overwrite HubSpot. | Sales-owned fields: deal stage, owner, close date |
| Bidirectional | Most recent change wins. Either system can update the other. | Shared fields: email, phone, company name |
The system where data is created or primarily maintained should be the source of truth for that field. Marketing creates lead source → HubSpot wins. Sales updates deal stage → Salesforce wins.
Recommended Sync Directions by Field Type
Contact/Lead Identity Fields
| Field | Direction | Rationale |
|---|---|---|
| Bidirectional | Either team may update; use most recent | |
| First Name / Last Name | Bidirectional | Sales often corrects form typos |
| Phone | Bidirectional | Sales may add direct lines |
| Job Title | Bidirectional | Updated in either system |
Marketing-Owned Fields
| Field | Direction | Rationale |
|---|---|---|
| Lead Source | HubSpot → Salesforce | Marketing creates and owns attribution |
| Original Source | HubSpot → Salesforce | First touch attribution from HubSpot |
| Recent Conversion | HubSpot → Salesforce | Form/landing page data from HubSpot |
| Lead Score | HubSpot → Salesforce | Scoring model lives in HubSpot |
| Lifecycle Stage | Bidirectional | Both systems may advance stages |
Sales-Owned Fields
| Field | Direction | Rationale |
|---|---|---|
| Contact Owner | Salesforce → HubSpot | Sales assigns ownership in SFDC |
| Deal Stage | Salesforce → HubSpot | Pipeline managed in Salesforce |
| Close Date | Salesforce → HubSpot | Sales forecasting in Salesforce |
| Deal Amount | Salesforce → HubSpot | Revenue data from Salesforce |
| Lead Status | Salesforce → HubSpot | SDR/Sales qualification in Salesforce |
Conflict Resolution: What Happens When Both Change?
For bidirectional fields, you must define what happens when both systems have different values. HubSpot offers two options:
Option 1: Most Recent Value Wins
Whichever system was updated most recently overwrites the other. Good for fields that either team may legitimately update.
Best for: Email, phone, job title, company name
Option 2: Prefer Salesforce Unless Blank
Salesforce value always wins unless it's empty. Good for fields where sales corrections should stick.
Best for: Fields where sales "cleans up" marketing data
"Always prefer HubSpot" or "Always prefer Salesforce" on bidirectional fields causes data to get stuck. If sales fixes a phone number in SFDC and HubSpot always wins, the fix gets overwritten.
Fields You Should NOT Sync
Not every field needs to sync. These commonly cause problems:
- System fields: Created date, last modified date (let each system track its own)
- Internal notes: Sales notes in SFDC shouldn't overwrite marketing notes in HubSpot
- Calculated fields: Formulas should calculate locally, not sync
- Temporary flags: "In campaign X" flags that only matter in one system
Field Mapping Best Practices
- Map only what you need. Start with 20-30 essential fields. Add more later if needed.
- Document every mapping. Spreadsheet with field name, direction, and rationale.
- Use consistent naming.
hs_lead_sourcein HubSpot maps toLead_Source__cin Salesforce. - Test before going live. Sync 10 test records. Verify each field mapped correctly.
- Monitor sync errors. Review HubSpot's sync health dashboard weekly.
Get the Full Integration Checklist
Complete field mapping template, lifecycle alignment, and sync error troubleshooting.
Download Checklist →Key Takeaways
- Choose sync direction based on which team owns the field
- Use "most recent wins" for shared fields like email and phone
- Don't sync system fields, notes, or calculated fields
- Document every mapping decision for future reference
- Test with a small batch before enabling full sync