How to Sync Components to HubSpot

This article walks you through how to map a plan component to your HubSpot data.

Before You Start

Make sure you are connected to HubSpot and that the objects you want to use are connected. The integration and objects are managed on the Integrations page in QuotaPath. Once your data is imported and synced, head to Plans and click on the plan you want to update.

In the video above, we are updating a draft plan.

Start a Mapping

Click on the Plan, then click on the earnings component you want to map (or click the small down caret on the right of the component to show the details).
When the Component details drop down, scroll down and click Map Data Source.

You will have the option to use an existing mapping if one exists:

If you choose that path, find your mapping, select it, and click Next. From there, you can “Edit it as a new mapping” or apply that mapping directly to this component.
Let’s assume we choose “Create New Mapping.”

Name the Mapping and Choose an Object

Each mapping has a mapping name. By default, a new mapping name is the plan name, a colon, then the component name. You can adjust the mapping name to make it clear what this mapping represents and to distinguish it from other mappings.

Next, select the object you want to connect to. The objects shown here are the ones connected on the Integrations page. In this example, we will select Deals.

Map Your Fields

Line up the QuotaPath fields with the HubSpot data you want to pull. In this example, we are using Deal Name.
For ARR, choose Amount. You can search for any field, or hit the space bar to view options like Annual Recurring Revenue or anything else that makes sense from your HubSpot.
Do the same for Deal Date by choosing Close Date.
Map the Deal Owner — whoever is the commissionable team member in QuotaPath. In this example, that is Deal Owner; in other plans it may be a property like SDR Owner or Manager.

For any property you use for ownership within QuotaPath, make sure it is a HubSpot user property. This allows the assignee filter to line up the user ID in HubSpot with the user in QuotaPath based on email addresses.

You can also add deals to all plan assignees. This is useful if, for example, you have a couple of solutions engineers supporting the entire sales team — in that case, you can add deals to both plan assignees so everyone gets credit.

You can add additional fields here as well. In this example, we are adding the Term Length field and mapping it to the Term Length property in HubSpot. Click Next.

Define Closed Won, Pipeline, and Closed Lost

The next step is deciding what is considered Closed Won and what is considered Pipeline within QuotaPath. In this example, for Closed Won, we are using Deal Stage and selecting Closed Won. For Pipeline, you can select where you want to start bringing data in — most teams choose a later stage of pipeline so reps can forecast those deals within QuotaPath. You can also map when something is considered Closed Lost.

This example is a straightforward AE plan, so we are using deal stages. For an SDR plan that brings in sales qualified leads, you might use something like an SQL Date — the fact that an SQL Date is stamped on the deal could itself be the Closed Won condition. You could say SQL Date is not null, and that becomes the Closed Won condition.

Add Filters and Sync

Click Next. From here, you can add any additional filters needed to bring in specific deals. For example, if you want to filter by Term Length where Term Length is multi-year, you can do that. You can filter on anything within HubSpot at the deal level — search in the field, or hit the space bar to access any deal-level property that is synced.

Once your filters are added, click Sync to save the mapping and sync your data.

That is how you map a component to HubSpot.