What is Field Mapping?

Field mapping is the set of rules that tells two connected systems which field in one matches which field in the other, so a value written in your CRM, forms or enrichment tool lands in the right place and format.

At a glance

• Every integration that moves records between tools, such as HubSpot and Salesforce, runs on a field map.
• A mapping pairs two fields of compatible types and adds a sync rule that says which system wins.
• HubSpot’s Salesforce connector offers four sync rules: prefer Salesforce unless blank, always use Salesforce, two-way, and don’t sync.
• Most mapping failures are quiet. Values get dropped, overwritten or left blank without an error anyone sees.

How field mapping works

A field map has three parts: the source field, the destination field and the rule for which way data flows. The two fields have to hold the same kind of data. In HubSpot’s Salesforce integration, a dropdown property maps to a Salesforce picklist, multiple checkboxes map to a multi-select picklist, a single checkbox to a boolean, and a date picker to a date or datetime field.

The sync rule decides what happens when both systems hold a value. Under “prefer Salesforce unless blank”, HubSpot only writes to Salesforce when the Salesforce field is empty. Under “two-way”, the most recent value overwrites the other one, and a deletion on either side deletes it on both.

A field mapping example

Example (illustrative): your enrichment tool writes employee count to a HubSpot number property, which maps to a number field on the Salesforce Account. Set to “always use Salesforce”, nothing new ever reaches the Account, so your segmentation by company size runs on whatever was typed in by hand.

Common field mapping mistakes

• Mapping one property to several fields. HubSpot warns that duplicate mappings can overwrite values or create sync loops. Use one mapping per field.
• Expecting a new mapping to backfill. Existing values don’t sync retroactively when you create a mapping. Run a resync or an import, or old records stay blank.
• Picking “two-way” by default. If a rep and an automation both edit the field, the last write wins and the history is gone. Decide which system owns each field.
• Mapping lookup fields as text. Salesforce reference fields arrive in HubSpot as 18-digit record IDs, not readable labels, unless you map them to a dropdown and label each option.
• Owners that don’t match. Owner sync only works when the HubSpot user matches an active Salesforce user by name and email. Otherwise the owner resets.
• No written map. When the person who set it up moves on, nobody can say why a field holds what it holds. Export the mappings and keep the list with your CRM documentation.

Limits to know before you build

Connectors have hard limits. HubSpot caps the Salesforce integration at 500 field mappings per object, and some mappings can’t be changed at all: the owner mapping is two-way only, even when the screen shows another rule. Check these before you design a field list around them.

Custom HubSpot properties of the “HubSpot user” type can’t be mapped to Salesforce at all, so a team that tracks a second owner that way needs a different field type.

How field mapping shows up in a revenue system

Routing, scoring and every pipeline report depend on fields that arrive the same way each time. At Datatruck, we set up HubSpot from scratch alongside the outbound motion, together with the ICP, the messaging and the dashboards. You can read how Datatruck’s sales motion was built, or see what our RevOps work covers.

Terms that sit next to field mapping

Field mapping decides where values from data enrichment land, and data hygiene and deduplication keep those values clean once they’re there. Lead routing and lead scoring both read mapped fields, so a broken map shows up first as leads with the wrong owner. Most maps connect a marketing tool to a CRM such as Salesforce.