How to Set Up HubSpot Field Mappings

Learn how to set up HubSpot field mappings in Cognism to control exports, map data correctly, and manage update rules.

This guide explains how to configure field mappings, export rules, and update behaviour in Cognism. 

By mapping data correctly, you can ensure records are created and updated accurately in HubSpot while maintaining consistent data across your CRM.

Prerequisites

Before you start, you must:

  • Be a Cognism admin
  • Have HubSpot connected to Cognism

Here is how to set up HubSpot field mappings with the Cognism platform: 

1 - Open the HubSpot field mapping settings

  1. In Cognism, click Integrations in the left-hand menu. 
  2. Select HubSpot
  3. Click Setup
  4. Follow the setup steps until you reach Map data fields

Field mappings are configured during the HubSpot integration setup flow.

2 - Configure export rules

Export rules control what happens when Cognism finds matching records in HubSpot during an export.

You can configure these rules separately for contacts and companies.

  1. Open the General step. 
  2. Choose how Cognism should behave when a matching record exists.

You can select one or more of the following options:

  • Create new contact
  • Update existing contact
  • Create new company
  • Update existing company

These settings apply to all exports.

3 - Map contact fields

Use the Contact step to define how Cognism contact data maps to HubSpot fields.

  1. Open the Contact step. 
  2. For each Cognism field, select the HubSpot field you want to map it to.
  3. Save your changes.

All standard HubSpot contact fields are supported.

You can also map data to custom HubSpot fields.

If you want to track where records originate, we recommend adding Cognism as a drop down to your existing source field. 

Available contact mappings in Cognism

Cognism fieldDescription
First namePerson’s first name
Last namePerson’s last name
EmailPerson’s primary email address
Company namePerson’s company name
Job titlePerson’s job title
Office phonePerson’s office phone number
Mobile phonePerson’s mobile phone number
CityPerson’s city
StatePerson’s state
CountryPerson’s country
StreetCompany street address
Zip codeCompany postcode
WebsiteCompany website
IndustryIndustry the person works in

4 - Map company fields

Use the Company step to control how company data is sent to HubSpot.

  1. Open the Company step. 
  2. Select the HubSpot field for each Cognism company field.
  3. Save your changes.

All standard HubSpot company fields are supported.

Available company mappings in Cognism

Cognism fieldDescription
Company nameCompany name
Company aliasAlternative company name
Company websiteCompany website
Number of employeesNumber of employees
IndustryCompany industry
Company typeOrganisation type
Company countryCompany country
Company stateCompany state
Company cityCompany city
Company addressHead office address
Company postcodeHead office postcode
Company phoneHead office phone number
Company year foundedYear the company was founded

5 - Configure static value mappings

Additional mappings allow you to populate HubSpot fields with static values.

These values are applied to all exported contacts or companies.

For example, you can map a fixed value, such as Cognism, to a HubSpot source field.

6 - Set update rules

Update rules control how Cognism data is applied to existing HubSpot records.

For each mapped field, choose one of the following:

  • Only update if blank – Cognism updates the field only if it is empty in HubSpot 
  • Always overwrite – Cognism updates the field every time you export 

These settings can affect reporting and data accuracy.

Expected results

When field mappings are configured:

  • Cognism exports data into the correct HubSpot fields
  • Records are created or updated based on your rules
  • Export behaviour is consistent across the web app and Chrome Extension

Next steps

  • Review your HubSpot custom fields
  • Test an export with a sample contact
Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.