HubSpot Common Action and Field Mapping

When you install the HubSpot integration, you decide which Measure fields map to which HubSpot fields. The HubSpot fields available depend on what exists in your HubSpot account, so most mappings do not pre-populate. This article walks through the common fields, teams map, and default mappings that need to be configured for a successful sync.

Action mapping dictates field mapping. It determines which events in HubSpot and Measure trigger a sync, and that decides which fields actually need to be mapped. Configure action mapping first, then review the field mappings underneath it. Action mapping is both for updating Contacts <> Customers in HubSpot and Deals <> Contracts bidirectionally. There is one exception where customer fields map automatically without action mapping configured.

HubSpot to Measure

• Contact <> Customer

  • When a contact is added: Create a customer in Measure.

  • When a contact is updated: Update the customer in Measure

• Deal <> Customer

  • When a deal is created: Create a customer in Measure

  • When a deal is updated: Update the customer in Measure

Measure to HubSpot

• Customer <> Contact

  • When a customer is created: Create a contact in HubSpot.

  • When a customer is updated: Update the contact in HubSpot.

• Contract <> Deal

  • When a contract is updated: Update the deal in HubSpot

These actions keep contacts and customers aligned in both directions. Set any action to Do Nothing if you want a one-way sync.

Customer mapping is less common. Many teams prefer to keep HubSpot as the source of truth for contact data and do not want updates in Measure flowing back to HubSpot. If that applies to your team, set the Customer <> Contact action mapping to Do Nothing under the Measure to HubSpot section above.

The Customer to HubSpot Contact mapping covers the same fields you would fill in when creating a customer manually in Measure. The HubSpot contact properties available in the dropdown depend on what exists in your HubSpot account, including any custom properties your team has added. Nothing pre-populates. You decide which Measure customer field flows into each HubSpot field.

When a contract is created from an associated deal in HubSpot and no matching customer exists in Measure yet, Measure automatically creates the customer. In this case, core contact fields are pulled from the HubSpot contact regardless of your action mapping settings. The following fields are mapped automatically: Contact Name, Email, Billing Emails, Title, Organization, Phone Number, and Address.

For example, if your team sets Customer <> Contact action mapping to Do Nothing but creates a contract from a HubSpot deal, Measure still creates the customer record using those core fields. You do not need to configure customer field mapping for this to work.

Common fields teams map:

Map only the fields your team relies on inside Measure. Leave the rest unmapped if they are not necessary.

The Contract to HubSpot Deal mapping keeps deal records in sync with Measure contracts. As with customer mapping, the HubSpot deal properties available depend on your HubSpot account.

The mapping that ships with meaningful defaults is Deal Stage → Status, which controls how Measure contract statuses translate to HubSpot pipeline stages. The pipeline itself is auto-computed. Measure sets it for you.

Common fields teams map:

Map additional deal fields like Close Date, Create Date and others only if you need that data to round-trip.

Deal Stage is the one mapping that almost always needs review. Measure contract statuses map to HubSpot sales pipeline stages, and HubSpot pipelines vary by team. The defaults point to HubSpot's standard Sales Pipeline stages:

If your team uses a custom pipeline, remap the statuses that matter for your workflow. You do not need to remap every status. Only the ones your pipeline actually uses. Statuses that never get triggered will not cause sync issues if they are left on the default.

Most fields do not need your attention. Focus your setup time on:

• Action mappings to determine what you want synced over, and if the sync will be bi-directional.

• Deal Name, Deal Stage Field Mapping for the statuses your pipeline actually uses. ⚠️ These are required fields for the sync to work.

• Any deal fields your team relies on inside Measure, including custom HubSpot properties that you want synced over for a deal/contract.

Review your Integration Logs on the HubSpot Integration page after the first few syncs to confirm everything is flowing as expected.