Field mapping defines which information travels between the two systems. Nothing is synced by default; you create each field pair manually.
Available on: Platform > Integrations > HubSpot > Fields
Who can do it: Admin
Module: Platform
Create a mapping
-
In Platform > Integrations > HubSpot, find the account and click Configure
-
Open the Fields tab
-
Click Add mapping
-
In HubSpot field, choose the destination property — use Search field… to filter by name
-
In Smart field, choose the matching Nuvia field
-
Click Save mappings
How fields are organized on screen
The list is split into two sides, each with its own organization.
| Side | How it is organized |
|---|---|
| HubSpot field | Grouped by object: Contact, Deal, and Lead. The most commonly used properties appear first; the rest follow in alphabetical order |
| Smart field (Nuvia) | Grouped by context: Contact, Conversation, Qualification, and Company |
To find a specific property in accounts with many fields, use the Search field… search inside the selector. It filters by name as you type.
Labels that appear on the rows
-
Bidirectional sync (Contact, Deal, and Lead) → the mapping applies in both directions. There is no per-field direction setting (direction can only be chosen in the Funnels tab, per stage)
-
Read-only → the property is calculated by HubSpot and cannot be written through the API
Dropdowns and multiple choice
When the Nuvia field is a selection or multiple choice field, Nuvia sends HubSpot the option text, exactly as it is set up in the Nuvia field. HubSpot only accepts this value if it is identical to one of the property's options, including uppercase, lowercase, accents, and spaces.
| Option in Nuvia | Option in HubSpot | Result |
|---|---|---|
Hot |
Hot |
Syncs |
hot |
Hot |
Rejected, the capitalization difference invalidates the value |
Qualified |
Qualified with a trailing space |
Rejected |
Not interested |
Not Interested |
Rejected |
The failure is recorded in the History tab, with status Failed or Partial and the message: “The value sent is not one of the options accepted by property X in HubSpot. Review this field's mapping in the integration.” Since the history is kept for 7 days, it is worth checking it regularly after changing selection fields.
How to avoid it
-
Copy and paste the option text straight from HubSpot when you set up the field options in Nuvia; do not retype it
-
Standardize before mapping: if HubSpot has
Hot,Warm,Cold, the Nuvia field needs to have exactly those three texts -
After creating the mapping, change a test contact and check the result in the History
Multiple choice
Multiple choice values travel separated by semicolons (;), which is the separator HubSpot uses. So if any selected option has ; in its text, the entire field is not sent; the semicolon would break the value on the other side. The rest of the fields in that record go through normally.
Avoid using ; in the option text of Nuvia selection fields.
In the opposite direction
When a dropdown value comes from HubSpot, it is saved in Nuvia with the option's internal code, not the label you see in HubSpot. In the History panel the label is displayed normally; the difference shows up in the value stored on the contact.
Refresh the property list
When someone creates, renames, or deletes a property in HubSpot:
-
Open the Advanced tab
-
In Refresh fields, click Sync fields
Nuvia fetches the latest properties from HubSpot, makes the new ones available for mapping, and removes mappings for properties that no longer exist.