Skip to main content
Documentation
Troubleshooting
Feature Requests Status

HubSpot Overview

Edit on GitHub
  • Updated
Fivetran System User Fivetranner

HubSpot is an inbound marketing and sales software that helps companies attract visitors, convert leads, and close customers.

Featureslink

Feature Name Supported Notes
Capture deletes check COMPANY, CONTACT, CONTACT_LIST, DEAL, DEAL_PIPELINE, DEAL_PIPELINE_STAGE, FORM, OWNER_TEAM, ROLE, TEAM, TEAM_USER, TICKET_PIPELINE, TICKET_PIPELINE_STAGE and USERS tables.
Custom data check COMPANY, CONTACT, DEAL, LINE ITEMS, and PRODUCT tables only. We support custom objects.
Data blocking check Column level
Column hashing check
Re-sync check Connector level
History check COMPANY_PROPERTY_HISTORY, CONTACT_PROPERTY_HISTORY, DEAL_PROPERTY_HISTORY, DEAL_STAGE, LINE_ITEM_PROPERTY_HISTORY, PRODUCT_PROPERTY_HISTORY, and TICKET_PROPERTY_HISTORY tables *.
API configurable check API configuration
Priority-first sync check EMAIL_EVENT_SENT, EMAIL_EVENT_DROPPED, EMAIL_EVENT_DELIVERED, EMAIL_EVENT_DEFERRED, EMAIL_EVENT_BOUNCE, EMAIL_EVENT_OPEN, EMAIL_EVENT_CLICK, EMAIL_EVENT_STATUS_CHANGE, EMAIL_EVENT_SPAM_REPORT, EMAIL_EVENT_FORWARD, EMAIL_EVENT_PRINT, and EMAIL_EVENT_SUPPRESSED tables.
Fivetran data models check Get the models: source / transform
Private networking

IMPORTANT: The HubSpot connector doesn’t support switching modes because we fetch history data directly from the APIs. We maintain two separate tables, one for live mode and one for history mode. For example, on the connector’s Schema tab, you will have two tables, COMPANY and COMPANY_PROPERTY_HISTORY. You can sync the history table only if you have included the live table in your syncs.

Supported productslink

Product Name
HubSpot CRM
Marketing Hub
Sales Hub
Service Hub

Setup guidelink

Follow our step-by-step HubSpot setup guide to connect HubSpot with your destination using Fivetran connectors.

Sync overviewlink

Sync strategylink

During a sync if we find more than 9,900 updated records for the following endpoints, we re-import the associated source tables in full to capture all the changes:

  • COMPANIES
  • DEALS
  • ENGAGEMENTS
  • CUSTOM_OBJECTS

If we find 990 updated records for the LINE_ITEMS table, we re-import the table in full to capture all the changes.

NOTE: The HubSpot API returns a maximum of 10,000 most recently updated records. We maintain a buffer of 100 to ensure data integrity and prevent API errors. When we detect that the number of updated records exceeds 9,900, we consider that the number is more than 10,000 and re-import the table in full. For the LINE_ITEMS table, the API returns a maximum of 1000 records. When we detect that the number of records exceeds 990, we re-import the table in full.

Sync strategy for ENGAGEMENT tables

We do incremental syncs of the ENGAGEMENT and ENGAGEMENT_* tables according to the sync frequency you set in your Fivetran dashboard. We also perform a full re-sync of these tables once every three days because we noticed incomplete data when we performed incremental syncs alone. If a full re-sync of these tables is still pending when we attempt the next incremental sync, we skip that incremental sync.

Sync strategy for EMAIL EVENT tables

In every sync, we re-fetch data that is twenty-five hours behind the data synced in the current incremental sync for the EMAIL_EVENT_* tables you have selected. We do this to capture events we may have missed because of HubSpot’s event processing delays.

The EMAIL_EVENT table syncs data for only the event types you define in the source EMAIL_EVENT_* child tables. To sync the EMAIL_EVENT table, make sure to select all the relevant EMAIL_EVENT_* child tables in the Schema tab of your connector’s dashboard. If you don’t select any of these child tables, we don’t sync data into the EMAIL_EVENT table.

TIP: Hubspot’s Email Events API sends bot events that may increase your total event count. To exclude these bot events, query the events with filtered_event = false.

Sync strategy for PROPERTY_HISTORY tables

Enabling history mode increases your monthly active rows (MAR) consumption because every change is recorded as a new row that counts towards MAR. We do incremental syncs of the history tables. We may also sometimes do a full re-sync of these tables according to the connector sync strategy.

NOTE: The CONTACT_PROPERTY_HISTORY table contains different versions of each record, and syncing the table may contribute to higher MAR usage because of its size.

Capture deleteslink

We use different strategies to capture deletes because the HubSpot API doesn’t offer a mechanism to capture deletes:

  • Infer deletes for the following tables:

    • CONTACT_LIST
    • DEAL_PIPELINE
    • DEAL_PIPELINE_STAGE
    • FORM
    • OWNER_TEAM
    • ROLE
    • TEAM
    • TEAM_USER
    • TICKET_PIPELINE
    • TICKET_PIPELINE_STAGE
    • USERS
    • TICKET_PIPELINE_STAGE

    We compare the tables against their previous version and capture deletes using the _fivetran_deleted system column.

  • Use webhooks to capture deletes for the COMPANY, CONTACT, and DEAL tables.

    NOTE: If you created the connector using our REST API, we don’t capture deletes for the COMPANY, CONTACT, and DEAL tables, because these connectors are not authorized using the Fivetran Hubspot application.

We do not capture deletes for tables that do not support the Capture deletes feature, though they still contain the is_deleted or _fivetran_deleted columns. Deleted records are marked as false in the is_deleted or _fivetran_deleted columns.

Capture mergeslink

In HubSpot, you can merge two records into one record. For example, when you merge two contacts, the primary contact record remains after the merge and the secondary contact is merged into the primary record. For more information, see HubSpot’s documentation.

We capture merges for the COMPANY, CONTACT, and DEAL tables.

  • To capture merges of the CONTACT table, we use a separate table, CONTACT_MERGE_AUDIT.

    NOTE: You can also use our dbt Core-compatible data model to delete your merged contacts. Delete merged contacts using hubspot_contact_merge_audit_enabled: TRUE. The data model enables you to audit your merge contacts and removes any merged record from the CONTACT table.

  • To capture merges of the DEAL table, we have a merged_deal table in your destination. This table reflects that deal with id merged_deal_id has been merged into deal with id deal_id.

    NOTE: In your destination table, you may observe the missing _fivetran_deleted column.

  • To capture merges of the COMPANY table, we mark the company records as is_deleted = TRUE.

Deal stage calculationslink

The HubSpot API returns only the date_entered value of the dealstage properties data. We sync this data to the DEAL_STAGE table.

Fivetran populates the date_entered value in the _fivetran_start column and sets the date_exited value in the _fivetran_end column. The date_exited value for a deal stage is the date_entered value of the next deal stage in chronological order.

You can calculate the time_in value as the difference between the _fivetran_start and _fivetran_end column values in the DEAL_STAGE table.

For example, in the DEAL_STAGE table:

deal_id deal stage date_entered _fivetran_start _fivetran_end
10 123 11:00 11:00 12:00
10 145 12:00 12:00 13:00
10 157 13:00 13:00 14:00
10 173 14:00 14:00 MAX_TIMESTAMP_VALUE

  • For deal_id 10 in deal stage 145:

    • date_entered_145 = _fivetran_start = 12:00
    • date_exited_145 = date_entered_157 = _fivetran_end = 13:00
    • time_in_145 = 1 hour (_fivetran_end - _fivetran_start)

  • For deal_id 10 in deal stage 173:

    • date_entered_173 = _fivetran_start = 14:00
    • date_exited_173 = _fivetran_end = MAX_TIMESTAMP_VALUE
    • time_in_173 = MAX_TIMESTAMP_VALUE - 14:00 (_fivetran_end - _fivetran_start)

HubSpot Tickets API limitationslink

HubSpot’s Tickets API endpoint returns a list of changes to the ticket objects. HubSpot limits the returned changes to the last 24 hours. To ensure data integrity, Fivetran triggers a re-sync of the TICKET table if the cursor is older than 24 hours.

Schema informationlink

Marketing Hub schemalink

This schema is applicable for the HubSpot Marketing Hub product.

To zoom, open the ERD in a new window.

CRM and Sales Hub schemalink

This schema is applicable for the HubSpot CRM and Sales Hub products.

To zoom, open ERD in new window

Service Hub schemalink

This schema is applicable for the HubSpot Service Hub product.

To zoom, open ERD in new window

HubSpot Developer Preview APIlink

We maintain the following tables using the HubSpot developer preview API, so there are sometimes structural changes in these tables. Fivetran automatically handles structural changes, which might lead to some schema breaking changes. If that happens, we need to re-sync the affected tables. You can read more in the HubSpot Developer Preview API documentation.

  • LINE_ITEM
  • LINE_ITEM_PROPERTY_HISTORY
  • PRODUCT
  • PRODUCT_PROPERTY_HISTORY

Custom objectslink

You can sync custom objects from your HubSpot account to your destination. We create a destination table for each custom object. We follow our standard table naming conventions.

We sync the properties you define for the custom objects into the PROPERTY table.

We create an association table in your destination to capture the associations between different custom objects and associations between a custom object and the following tables:

  • COMPANY
  • CONTACT
  • DEAL
  • EMAIL
  • ENGAGEMENT
  • LINE_ITEM
  • PRODUCT
  • TICKET

Negative timestamps from HubSpotlink

We automatically convert negative timestamps received from HubSpot to EPOCH, for example, 1st January 1970 00:00:00 UTC.

Was this article helpful?
0 out of 0 found this helpful
Return to top

Related articles

Didn’t find what you need?

Contact support