How to Map Hubspot Properties to Salesforce Fields
Connecting Hubspot with Salesforce is a powerful way to keep your marketing and sales data aligned. To make the most of the integration, you must correctly map Hubspot properties to Salesforce fields so records stay accurate, complete, and synchronized.
This guide walks through the key concepts, required permissions, and step-by-step instructions you need to configure property mappings safely.
Before You Map Hubspot Properties
Before editing any mapping, verify that the Hubspot and Salesforce integration is fully installed and authorized on your portal.
Required access and permissions
- Access to the Hubspot Salesforce integration settings
- Permissions to edit properties in Hubspot
- Permissions in Salesforce to view and manage object fields
Changes to mappings can affect live data, so coordinate with your CRM administrator before modifying core fields.
Supported Salesforce objects
You can map Hubspot properties to standard Salesforce objects, including:
- Leads
- Contacts
- Accounts
- Opportunities
- Campaigns (for certain integration features)
Custom objects may have additional limitations depending on your integration configuration.
Accessing Hubspot Salesforce Field Mappings
To configure the mapping between Hubspot properties and Salesforce fields, open the integration settings area.
- In your Hubspot account, navigate to the Salesforce integration settings.
- Locate the section for Object and field mappings.
- Select the CRM object you want to configure, such as Contacts or Companies.
Each row in this area represents a mapped pair of one Hubspot property and one Salesforce field.
Understanding Hubspot to Salesforce Mapping Types
The integration offers several mapping types, depending on the data you are syncing and how you want conflicts handled.
One-to-one property mappings
Most mappings are one-to-one. A single Hubspot property corresponds directly to a single Salesforce field of a compatible type, such as:
- Text → Text
- Number → Number
- Date → Date
- Dropdown → Picklist
Only compatible types should be used to avoid sync errors.
Read-only and write-only behavior
Depending on your configuration, some fields may be read-only from Hubspot or from Salesforce:
- Read-only from Hubspot: Data can be viewed but not written back.
- Read-only from Salesforce: Data is controlled by Hubspot and not overwritten by updates from Salesforce.
Check each mapping’s rules before editing to avoid unexpected overwrites.
Custom property mapping in Hubspot
You can map custom Hubspot properties to custom Salesforce fields as long as they use compatible types and live on supported objects. Always document your custom mappings so your team knows where data is stored and how it flows between the systems.
How to Create a New Hubspot Mapping
To add a new connection between a Hubspot property and a Salesforce field, follow these steps.
- Open the integration settings and choose the relevant object (for example, Contacts).
- Click the option to add or create a new field mapping.
- Select the Hubspot property you want to sync.
- Choose the Salesforce field that should receive data from that property.
- Confirm the field types are compatible.
- Set the sync rule that controls which system wins in case of conflicting updates.
- Save your changes.
After saving, new sync cycles will begin using the updated mapping rules.
Editing Existing Hubspot to Salesforce Mappings
Updating an existing mapping lets you adjust how data moves between the systems without recreating everything from scratch.
- In the mapping table, find the row that corresponds to the property you want to change.
- Click to edit the mapping details.
- Review the current Hubspot property and Salesforce field pairing.
- Adjust the sync behavior or change to a different compatible field if necessary.
- Save the mapping and monitor upcoming sync results for issues.
Be cautious when changing a frequently used field, such as email address or lifecycle stage, because it can impact automation, reporting, and deduplication logic in both systems.
Choosing Sync Rules for Hubspot and Salesforce
Each mapping includes a sync rule that governs how the integration handles changes coming from both platforms.
Common sync rule patterns
- Prefer Salesforce: Salesforce is the source of truth. Updates there will overwrite Hubspot values.
- Prefer Hubspot: Hubspot is the source of truth and can push updates into Salesforce.
- Two-way sync: The integration decides which value is most recent and keeps both systems aligned.
Select the rule that matches your data governance strategy and clearly communicate this to your team.
Handling blank values and overrides
Consider what should happen when one side is blank:
- Should a blank in Hubspot clear out data in Salesforce?
- Should Salesforce ignore blanks from Hubspot and keep its existing value?
Configure these behaviors carefully to avoid accidentally erasing important information.
Best Practices for Reliable Hubspot Sync
Clean, predictable mappings reduce sync errors and keep your marketing and sales reports accurate.
Align picklists and dropdowns
When mapping dropdown or picklist fields:
- Ensure options in Hubspot match values in Salesforce.
- Avoid using different labels that represent the same meaning.
- Periodically review and clean up unused options.
Mismatched options are a common cause of sync failures or unexpected default values.
Test new mappings safely
When you introduce a new mapping or change sync rules:
- Test on a small set of records before a full rollout.
- Monitor sync logs for errors or warnings.
- Confirm that Salesforce records display exactly what you expect after the sync.
Consider exporting key data before large changes so you can restore values if needed.
Document your Hubspot integration setup
Create an internal document that lists:
- Each mapped Hubspot property and the corresponding Salesforce field
- Sync direction and conflict rules
- Any special handling for blanks or default values
This documentation will help new team members understand your stack and prevent accidental misconfigurations.
Troubleshooting Hubspot to Salesforce Mapping Issues
If data is not syncing correctly, focus first on the mapping configuration and field compatibility.
- Verify that the Hubspot property and Salesforce field types match.
- Check that the field is visible and editable for the integration user in Salesforce.
- Review sync logs for specific error messages tied to problem records.
- Confirm there are no validation rules in Salesforce blocking updates.
Adjust mappings as required, then re-sync affected records.
Where to Learn More About Hubspot Salesforce Mapping
For deeper technical details on how to map Hubspot properties to Salesforce fields, review the official documentation on the Hubspot Knowledge Base: Map Hubspot properties to Salesforce fields.
If you need expert help designing an integration strategy, you can also consult a specialized solutions partner like Consultevo for guidance on CRM architecture and synchronization rules.
By carefully planning your mappings, managing sync rules, and testing changes, you can ensure that data flows reliably between Hubspot and Salesforce and that both systems support your sales, marketing, and reporting needs.
Need Help With Hubspot?
If you want expert help building, automating, or scaling your Hubspot , work with ConsultEvo, a team who has a decade of Hubspot experience.
“`
