HubSpot
HubSpot is an inbound marketing and sales software that helps companies attract visitors, convert leads, and close customers.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Capture Deletes | check | CONTACT_LIST, CONTACT_LIST_MEMBER, DEAL_PIPELINE, DEAL_PIPELINE_STAGE, and FORM tables. |
| Custom Data | check | COMPANY, CONTACT, DEAL, LINE ITEMS and PRODUCT tables only |
| Data Blocking | check | Table level |
| Column Hashing | ||
| Re-sync | check | Connector level |
| History | ||
| API Configurable | check | |
| Priority-first sync |
Setup guide
Follow our step-by-step HubSpot setup guide to connect HubSpot with your destination using Fivetran connectors.
Schema information
This schemas applies to all HubSpot connections.
HubSpot Marketing Schema
To zoom, open ERD in new window
HubSpot Sales/CRM Schema
To zoom, open ERD in new window
Deleted Rows
The HubSpot API doesn't make deleted records available so Fivetran can't mark deleted records in the destination warehouse. Deleted records will remain marked false where is_deleted or _fivetran_deleted columns exist except for the tables listed in the Update Frequency section below.
Update Frequency
Because the HubSpot API does not offer a mechanism to capture deletes, Fivetran infers deletes for the tables listed below. We perform a full import of these tables once a day, compare them to the previous version, and mark deletes using the _fivetran_deleted system column:
CONTACT_LISTCONTACT_LIST_MEMBERDEAL_PIPELINEDEAL_PIPELINE_STAGEFORM
HubSpot Developer Preview API
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_ITEMLINE_ITEM_PROPERTY_HISTORYPRODUCTPRODUCT_PROPERTY_HISTORY
Negative Timestamps from HubSpot
We automatically convert negative timestamps received from HubSpot to EPOCH, for example, 1st January 1970 00:00:00 UTC.