Map HubSpot properties to Oneflow data fields

Angelica Angelis
Angelica Angelis
  • Updated

INFORMATION

This article covers the basics of property mapping. For a more detailed guide on the enhanced functionality, please see our updated article on Two-way sync for HubSpot.

Any property of a HubSpot object (e.g., a Deal, Contact, Company, Ticket, Quote, Listing, Appointment, Service, or Custom Object) can be mapped to a data field in a Oneflow contract. By default, the HubSpot integration transfers a fixed set of properties to Oneflow data fields when a contract is created.

However, you can map and sync additional HubSpot properties to Oneflow’s data fields via the Two-way sync functionality. To do this, you’ll need to select which HubSpot property will be mapped to which data field in Oneflow.

NOTE

You’ll need HubSpot administrative privileges to configure data fields using Two-way sync. Once configured, the additional properties will be available to all Oneflow users of the account.

Map properties to data fields

To map HubSpot properties to data fields in Oneflow, follow these steps:

  1. Log in to HubSpot as an administrator.
  2. Navigate to any HubSpot object (e.g., a Deal, Contact, Company, Ticket, Quote, Listing, Appointment, Service, or Custom Object).
Screenshot 2026-04-28 at 14.51.47.png
  1. In the Oneflow widget, click on Settings.
  2. Select the Two-way Sync & mapping tab.
Two-way Sync & mapping tab in Oneflow settings
  1. Click the + Add new property button.

A new field mapping row will appear, where you’ll need to set three values: Object, Property, and Oneflow label.

NOTE

Please note that all three values are mandatory for mapping a property.

  1. Select the HubSpot object whose property you want to map from the first dropdown. This can be:
    • Deal
    • Company
    • Contact
    • Ticket
    • Quote
    • Listing
    • Appointment
    • Service
    • Course
    • Custom object

  2. Select a property from the second dropdown (the list varies by object).

    INFORMATION

    Using the Search feature: Click the search icon and start typing the name of any object, property, or Oneflow label in the text field (requires a minimum of three characters to start searching). The table will be filtered to match your search.
    Searching for properties to map

  3. Enter a Oneflow Label, which is the name of the Oneflow data field the HubSpot property maps to. This label appears in the Oneflow contract/template. By default, the text box is populated as Objectname_propertyname, but admins can choose any name.

    NOTE

    Each Oneflow label mapped to a HubSpot property must be unique; two property mappings cannot share the same Oneflow label.
    Unique Oneflow Label error

  4. Select your preferred sync direction options for each property (HubSpot → Oneflow, Oneflow → HubSpot, or both).

    NOTE

    To learn more about sync directions, see the Two-way sync article.

  5. Click Save Changes.
Saving property mapping changes

INFORMATION

  • If you have linked Ticket or Quote properties to data fields in Oneflow, your HubSpot object should have only one ticket or quote associated. If multiple exist, no data will be transferred.
  • Oneflow supports mapping data fields for up to three participants in a contract to their HubSpot Contact properties.
    • Only data fields associated with the first three participants in a contract are updated from HubSpot Contact properties.
    • Postfixes “_1”, “_2”, and “_3” are added to participant data field labels in Oneflow based on their position (e.g., Contact_Name_1, Phone_1 map to Participant 1).

Understanding Contact and Product Mapping

Certain HubSpot objects, like Contact and Product, have a unique mapping behavior when creating Oneflow data fields. When you map their fields, Oneflow creates numbered sets of data fields to handle multiple contacts (participants) or products from a single deal. The key to this mapping is the order in which the contacts or products appear.

How Contact Mapping Works

When you map HubSpot fields for a Contact (like Name or Email), Oneflow creates corresponding data fields like `Contact_Name_1`, `Contact_Name_2`, and `Contact_Name_3`. The mapping for participant 1, 2, etc., is determined by the top-to-bottom order of contacts in the Participants list when you create the contract.

Example:

Imagine your participants are listed in this order in the 'Create Contract' window:

  1. Amanda Payne
  2. Jane Smith
  3. Sam Jones

The system will automatically map their data as follows:

  1. Amanda Payne → All `Contact_*_1` data fields (`Contact_Name_1`, `Contact_Email_1`, etc.)
  2. Jane Smith → All `Contact_*_2` data fields (`Contact_Name_2`, `Contact_Email_2`, etc.)
  3. Sam Jones → All `Contact_*_3` data fields (`Contact_Name_3`, `Contact_Email_3`, etc.)

This means the first person in the list will always populate the `_1` fields, the second will populate the `_2` fields, and so on. A similar logic applies to Products, where the order of line items in your HubSpot deal determines which data populates the `Product_1`, `Product_2`, and `Product_3` fields in the contract.

Using Mapped Properties in a Oneflow Template

After mapping HubSpot properties to Oneflow data fields, let’s see how to transfer these values to a contract. This example uses a custom HubSpot Company property called ‘Org no’ mapped to a Oneflow data field called 'Company Org no'. (To learn how to create a custom property in HubSpot, see Create and edit properties).

Follow the steps below to use a mapped HubSpot property in your Oneflow contract:

  1. Ensure you’ve successfully mapped the HubSpot properties with the data fields in Oneflow as specified above.
  2. Log in to your Oneflow account.

  3. Navigate to a template and ensure its template group is set to Hubspot.

    IMPORTANT

    If the template group isn’t set to Hubspot, select Hubspot from the template group dropdown in the Settings pane.

HubSpot template group setting
  1. Make a note of the template name; you’ll need it later.
  2. In the template, place the cursor where you want the data field and click the Data field icon.
Inserting a data field in the template
  1. Select the data field from the dropdown list.
Selecting the mapped data field
Data field inserted in the template

INFORMATION

Before creating a contract, ensure the HubSpot property you’re pulling (e.g., Org no) contains a value; otherwise, the Oneflow data field will be empty.

  1. Go to the HubSpot deal from which you want to create a contract and click the company name.
Navigating to company from HubSpot deal
  1. Ensure the custom property (e.g., Org no) contains a value.
Verifying property value in HubSpot
  1. Open the Oneflow widget in the deal and click Create contract.
Create contract button in Oneflow widget
  1. Enter a name in Contract Name.
  2. From the Template dropdown, select the HubSpot template you configured in Oneflow.
  3. Select the checkboxes for the contacts (participants) to add to the contract. To learn more, see Getting Started with HubSpot.
  4. Click Create Contract to confirm.
Create Contract dialog in HubSpot
  1. Click Navigate to contract.
Navigate to contract button
  1. Verify that the HubSpot property value is populated in the Oneflow contract (e.g., Organization number).
Verifying mapped data in the Oneflow contract

Delete property mappings

If you wish to remove a HubSpot property mapped to a Oneflow data field, you can do this from the Oneflow integration Settings panel in HubSpot.

NOTE

You’ll need administrator rights to delete property mappings.

To delete property mappings, follow these steps:

  1. Log in to HubSpot as an administrator.
  2. Navigate to any HubSpot object (e.g., Deal, Contact, Company, Ticket, Quote, Listing, Appointment, Service, or Custom Object).
  3. Click Settings in the Oneflow pane.
  4. Select the Two-way Sync & mapping tab.
  5. Click the bin icon next to the mapping you wish to delete.
  6. Click Delete in the confirmation prompt.
Deleting a property mapping
  1. Click Save Changes to apply.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request