Skip to main content
Custom Field Mapping

Learn how to map custom HubSpot fields to Karbon for seamless client data syncing.

Erin Jamison avatar
Written by Erin Jamison
Updated this week

When syncing data from HubSpot to Karbon, you may want to ensure that specific data fields are transferred accurately. The Custom Field Mapping feature allows you to map HubSpot custom fields to Karbon fields, providing flexibility and helping you maintain data consistency across both platforms.

Custom Field Mapping Setup

When setting up custom field mappings between HubSpot and Karbon, it's important to follow the detailed steps to ensure a seamless synchronization. For a step-by-step guide on configuring your custom field mappings, please refer to our HubSpot to Karbon Custom Field Mapping Setup article.

In this guide, you’ll learn how to:

  • Select fields to sync between HubSpot and Karbon

  • Map custom fields for both HubSpot Companies and Contacts

  • Handle field-specific configurations, such as ensuring the correct data format and valid values

  • Add or remove mappings as your integration evolves

Available Custom Fields for Mapping

The exact list of available fields will depend on your HubSpot instance setup. Here are the key fields that you can map between HubSpot and Karbon:

1. BirthDate

  • Valid for: HubSpot Contacts

  • Format: ISO8601 date (e.g., 1997-01-05)

2. DeathDate

  • Valid for: HubSpot Contacts

  • Format: ISO8601 date (e.g., 2023-12-31)

3. OrganizationKey / ContactKey

  • Description: This is the Karbon permakey for the organization or contact. You can map this if you already store the Karbon key in HubSpot and don't want the integration to search for a match.

4. Client Owner / Client Manager

  • Valid for: HubSpot Contacts and Companies

  • Types of Inputs: HubSpot User ID, Name, or Email

  • Important Note: If the data doesn't match an active Karbon User, it will be ignored.

5. Karbon Contact Type

  • Valid for: HubSpot Contacts

  • Description: This must match an active Karbon Contact Type, such as "Client".

6. Custom Identifier

  • Description: A unique identifier for the organization or contact. If a duplicate is found in Karbon, the record will fail to update.

7. Financial Year End Day & Month

  • Valid for: HubSpot Organizations and Contacts

  • Day Format: 1, 28, 30, or 31

  • Month Format: 1 to 12

8. Incorporation Date

  • Valid for: HubSpot Organizations and Contacts

  • Format: ISO8601 date (e.g., 2005-09-12)

9. Legal Name

  • Valid for: HubSpot Organizations and Contacts

  • Description: The legal name of the Organization or Contact.

10. Tax Country Code

  • Valid for: HubSpot Organizations and Contacts

  • Format: Two-letter ISO country code (e.g., US, AU, CA)

11. Trading Name

  • Valid for: HubSpot Organizations and Contacts

  • Description: The trading name used by the Organization or Contact.

12. Annual Revenue

  • Valid for: HubSpot Organizations and Contacts

  • Format: Numeric value representing the organization's or contact’s annual revenue.

13. Industry

  • Valid for: HubSpot Organizations and Contacts

  • Description: The industry that the Organization or Contact operates in.

Mapping Fields Between HubSpot and Karbon

The mapping process allows you to select the HubSpot fields to match the corresponding Karbon fields. You’ll typically map the following:

  • HubSpot Field: Client Owner

    • Karbon Field: Client Owner (mapped via HubSpot User ID, Name, or Email)

  • HubSpot Field: Organization Key

    • Karbon Field: Organization Permakey

  • HubSpot Field: BirthDate

    • Karbon Field: Birth Date (ISO8601 format)

To add a field, simply click the “Add a HubSpot <> Karbon Mapper” button, then choose the field from the dropdown list.

Notes on Mapping

  • Client Owner / Client Manager: Ensure the name or email you’re mapping matches an active Karbon User. If it does not, the mapping will be ignored.

  • Custom Identifier: A unique identifier can be used to prevent duplicates from being created. If a duplicate is found in Karbon, the record will not be updated.

Did this answer your question?