Mapping Direction
FirstTouch field mappings write FirstTouch-held or enriched values into HubSpot properties. Mapping a field does not import arbitrary HubSpot values into FirstTouch variables.Contact And Company Mappings
The HubSpot settings page can include:- Contact field mapping
- Company field mapping
- locked identity rows used for matching and required updates
- editable rows for optional enrichment fields
Locked Rows
The following identity mappings are locked to their standard HubSpot properties because FirstTouch relies on them for matching and required updates:- Contact: email, first name, last name, phone, and LinkedIn URL
- Company: name, domain, and LinkedIn company page
Overwrite Behavior
Changing a mapping chooses the destination property; it does not add a per-mapping overwrite setting. Normal mapped updates follow a fixed server-side overwrite policy. A Flow Plan CRM action can separately copy FirstTouch properties to CRM properties and expose an overwrite choice for that action. That choice applies only to the property-copy action. It does not change the server policy for normal mapped updates, and the action does not create or enrich a CRM record.Primary Company Association
Some Contact-based HubSpot operations use the Contact’s Primary Company Association when they need one Company context. This is not a universal rule for every integration path; operations that already carry a specific HubSpot Company ID use that supplied context.Troubleshooting
If a property did not update, check:- HubSpot connection status
- Contact or Company matching
- field mapping
- locked or disabled mapping state
- the fixed server overwrite policy, or the CRM property-copy action’s overwrite choice when that action performed the write
- HubSpot property permissions
- whether the value exists in FirstTouch