Skip to main content

​
Overview

Field mappings pair HubSpot properties with Unify attributes and control how values sync in each direction. For example, you can use HubSpot as the source for company ownership while filling an empty phone number in HubSpot with a value from Unify. Mappings are shared by connections to the same HubSpot account within your Unify workspace. You need permission to manage the HubSpot integration to edit them. Sync rules control when Unify writes records using these mappings.

​
Configure field mappings

1

Open an object mapping

Open Settings → HubSpot and select the connection. Under Field mappings, click Edit mapping for the object you want to configure.Unify prepares mappings for standard fields when you connect. Review them before enabling bidirectional syncs, especially if your team uses custom properties in place of standard ones.
2

Choose the fields

Select the Unify attribute and corresponding HubSpot property in each row. Click Add field to add another pair.Choose compatible field types. The editor identifies required fields and limits the available choices for fields that cannot be read or written. Create a custom property in HubSpot before mapping to it.
3

Choose the sync behavior

Use Sync to Unify to choose the read behavior and Sync to HubSpot to choose the write behavior. These choices are independent: a field can be read into Unify while writes to HubSpot are disabled.
4

Save the mapping

Resolve any required-field or compatibility warnings, then click Save. Changes to incoming mappings trigger background reprocessing of existing records for that object. Values update as that work progresses alongside regular syncs.Outgoing changes use the saved mapping on subsequent syncs. Review a write in Sync log to check the values sent to HubSpot.

​
Read behavior

Read behavior controls how a HubSpot value updates its mapped Unify attribute:

​
Write behavior

Write behavior controls how a Unify value updates its mapped HubSpot property: Overwrite on manual edit is available only for supported attributes. Use default values when a property needs a fallback value during sync. Direct updates requested in chat use the values supplied for that action.

​
Ownership mappings

An engagement policy can depend on a company ownership mapping. Its ownership attribute must read from the CRM with Overwrite and write with Overwrite on manual edit. Changing or removing that mapping can disable policy enforcement; the editor identifies affected policies before you save. Coordinate ownership changes with the administrator responsible for your team’s engagement policies.

​
Available fields

The editor lists the Unify attributes and HubSpot properties available for the selected object. This includes supported custom attributes and properties. Available choices depend on field type and the connected account’s access. Unify also provides activity and attribution values, such as the first or most recent play and sequence associated with a person. To store one in a custom HubSpot property, create a property with a compatible type and map the corresponding Unify value.

​
Troubleshooting

Review the warnings beside the affected fields. Required Unify attributes need a read mapping. Required HubSpot properties need a suitable write mapping or default value. Check that the selected field types are compatible.
Confirm that the property exists on the selected HubSpot object and that the connected account can access it. Read-only fields cannot receive writes. Ask your HubSpot administrator to review the field’s type and permissions if it remains unavailable.
Open the object mapping and choose Reset to default. Review the confirmation before proceeding: the reset replaces your customized mapping and saves immediately. Check any ownership-policy warning before confirming.