Release Notes

June 2026

We have updated our sync strategy and now incrementally sync the MARKETING_CAMPAIGN_CONTACT table and its child tables. Previously, we re-imported this table. As part of this change, we no longer capture deletes for this table.

April 2026

We have added a new table, LEAD_DEAL, to store data for the associations between leads and deals.

We have added the following new tables for each custom object we sync:

• <CUSTOM_OBJECT_NAME>_PIPELINE to store pipeline definitions for the custom object type
• <CUSTOM_OBJECT_NAME>_PIPELINE_STAGE to store stage definitions for the custom object pipelines

We have added the following new tables to store Listings object data:

• LISTING
• LISTING_COMPANY
• LISTING_CONTACT
• LISTING_DEAL
• LISTING_ENGAGEMENT
• LISTING_PIPELINE
• LISTING_PIPELINE_STAGE
• LISTING_PROPERTY_HISTORY
• LISTING_TICKET

We have added the following new tables to store Orders object data:

• ORDER
• ORDER_COMPANY
• ORDER_CONTACT
• ORDER_DEAL
• ORDER_ENGAGEMENT
• ORDER_FEEDBACK_SUBMISSION
• ORDER_INVOICE
• ORDER_LINE_ITEM
• ORDER_PAYMENT
• ORDER_PIPELINE
• ORDER_PIPELINE_STAGE
• ORDER_PROPERTY_HISTORY
• ORDER_QUOTE
• ORDER_TICKET

We have added the following new tables to store Projects object data:

• PROJECT
• PROJECT_COMPANY
• PROJECT_CONTACT
• PROJECT_DEAL
• PROJECT_ENGAGEMENT
• PROJECT_LISTING
• PROJECT_PIPELINE
• PROJECT_PIPELINE_STAGE
• PROJECT_PROPERTY_HISTORY
• PROJECT_SERVICE
• PROJECT_TICKET

We are gradually rolling out these changes to all existing connections.

March 2026

We have simplified how the HubSpot connector handles merged records to prevent duplicate data. When you merge records in HubSpot, Fivetran now marks the merged records as deleted (_fivetran_deleted = true). This change enables you to filter out inactive records without using complex joins.

We now support HubSpot's Services API to sync service records from your HubSpot account. To support this enhancement, we have added the following new tables:

• SERVICE
• SERVICE_COMPANY
• SERVICE_CONTACT
• SERVICE_DEAL
• SERVICE_ENGAGEMENT
• SERVICE_PIPELINE
• SERVICE_PIPELINE_STAGE
• SERVICE_PROPERTY_HISTORY
• SERVICE_TICKET

We are gradually rolling out this enhancement to all existing connections.

We have added a new table, DEAL_SPLIT, using HubSpot's Deal Splits API to sync deal split information from your HubSpot account.

January 2026

HubSpot deprecated the folderId field in the MARKETING_EMAIL table and has introduced a replacement field, folderIdV2. For more information, see HubSpot's documentation.

To ensure a smooth transition, Fivetran will continue to populate both the folderId and folderIdV2 fields until January 28, 2026. After this date, we will no longer populate the folderId field.

We recommend updating your downstream processes to use folderIdV2 and safely dropping the folderId column from the destination after the deprecation date.

We've added three new tables to the HubSpot connector to support account activity tracking:

• AUDIT_LOG - Contains a centralized audit log of all user actions within your HubSpot account, including CRM object creation, property value updates, security activity, and more. This table includes information about who performed the action (acting_user_user_id, acting_user_user_email), what action was performed (category, sub_category, action), and when it occurred (occurred_at).

• ACTIVITY_LOGIN - Tracks all user login attempts (both successful and unsuccessful) to your HubSpot account from the past 90 days. This table includes details such as login timestamp (login_at), whether the login succeeded (login_succeeded), IP address (ip_address), geographic location (location, country_code, region_code), and browser information (user_agent).

• ACTIVITY_SECURITY - Records security-related activities including CRM exports, user management changes, and integration installations. This table contains information about the type of security event (type), the user who performed the action (acting_user, user_id), when it occurred (created_at), and location details (ip_address, location, country_code, region_code).

These tables sync incrementally and require the account-info.security.read OAuth scope. You would need to re-auth to enable this scope. Please note that the AUDIT_LOG table is only available for Enterprise HubSpot accounts.

December 2025

We have added support for the following HubSpot APIs:

• Carts
• Commerce Payments
• Commerce Subscriptions
• Discounts
• Fees
• Taxes

We are gradually rolling out this improvement to all existing connections.

November 2025

Row filtering is now supported for the following connectors:

• Amazon S3
• Google Ads
• Google Drive
• HubSpot
• Jira
• Salesforce
• Generic Oracle
• Oracle RAC
• Amazon RDS for Oracle

To learn how to use row filtering and see the list of supported connectors, see our row filtering documentation.

October 2025

We unified each connector’s pre-built dbt Core–compatible data models into a single model. It standardizes and documents the Fivetran schemas created in your destination and outputs analytics-ready tables. Previously, most connectors used distinct source and transform models.

September 2025

We have fixed a bug where we synced incorrect values into the properties_occurred_at column of the MARKETING_EVENT_PARTICIPANT table. We now sync the correct values into this column.

We have re-synced the table to backfill the accurate data. This re-sync will not count towards paid MAR.

July 2025

We have added two new tables COMPANY_LIST and COMPANY_LIST_MEMBER to our HubSpot connector. COMPANY_LIST_MEMBER is a child table of COMPANY_LIST and contains the members of the list.

We are gradually rolling out this change to all existing connections.

We’re deprecating the archived column in the CUSTOM_OBJECT table. We now use the _fivetran_deleted column to indicate whether a record is archived in the CUSTOM_OBJECT table. To support a smooth transition, we will populate both the archived and _fivetran_deleted for a limited time. After the transition period, you can drop the archived column from your destination.

We have added support for HubSpot's Conversations API to sync conversations data from your HubSpot account. We are gradually rolling out this improvement to all existing connections.

We have improved our sync strategy for the 'EVENT' table to allow syncing all types of events from HubSpot, except e_list_size_changed and e_user_performed_action_no_object_type.

We now re-import property history for records with recent merges in the COMPANY and CONTACT tables during every incremental sync. This prevents frequent full resyncs of these tables to fetch the latest properties of merged records. To enable this, you can create a custom workflow for the COMPANY or CONTACT tables with the merge_timestamp property.

June 2025

We have added support for HubSpot's Marketing Campaigns API to sync your HubSpot account's marketing campaigns data.

We are gradually rolling out this improvement to all existing connections.

In the DEAL_PIPELINE_STAGE table, we have corrected the name of the closed_won column to is_closed. The data in this column represents whether a deal is closed or not, regardless of its label. You can still use the label column to determine whether a deal is "closed won" or "closed lost". This change ensures the HubSpot connector more accurately reflects your source data.

We are gradually rolling out these changes to all existing connectors. We will populate both closed_won and is_closed for a transition period. After this period, you can drop the closed_won column at your convenience.

April 2025

We have changed the primary key for the PROPERTY table. We now use the combination of _fivetran_id and hubspot_object columns as its composite primary key. Previously, only _fivetran_id was its primary key.

February 2025

December 2024

We have added a new field, Historical sync time frame, to the connection setup form. This allows you to select how many months' worth of historical data you want to sync. For an existing connection, you can edit the connection details and set the time frame value. For more information, see our Historical sync time frame documentation.

We apply the historical sync limit to the following tables only:

• CUSTOM_EVENT
• EMAIL_EVENT
• EVENT

We are gradually rolling out this feature to all connections.

HubSpot will sunset the Contact List V1 APIs on May 2025. For all connections created on or after December 13, 2024, we will use the V3 APIs to sync data to the CONTACT_LIST and CONTACT_LIST_MEMBER tables. For more information, see Hubspot documentation.

We are gradually rolling out these changes to all existing connections.

November 2024

We have added support for the HubSpot Feedback Submissions API to sync the feedback submissions data in your HubSpot account. We are gradually rolling out this improvement to all existing connections.

October 2024

Fivetran has created a dbt Core-compatible app reporting model that generates an end model containing unstructured document data to be used for Retrieval Augmented Generation (RAG) applications leveraging Large Language Models (LLMs).

The Unified RAG model supports the HubSpot, Jira, and Zendesk Support connectors.

Learn more in our Unified RAG model documentation.

We have added the following new same object association tables:

• COMPANY_COMPANY
• CONTACT_CONTACT
• DEAL_DEAL
• TICKET_TICKET

We have added a new column, category. This column is a part of the composite primary key for all the standard and custom association tables.

We have migrated the custom object association tables from V3 to V4 of the HubSpot Associations API. As part of this migration, we have made the following changes:

• Added a new column, type_id, to the custom object association tables and removed the type column from them. The new column is a part of the composite primary key. It is also a foreign key to the ASSOCIATION_TYPE table.
• Added the category column of the ASSOCIATION_TYPE table to its composite primary key.
• Replaced the [CUSTOM_OBJECT]_TO_EMAIL table with a new table, [CUSTOM_OBJECT]_TO_ENGAGEMENT, to store all 7 types of engagement associations. In the new table, you can identify the type of engagement association by the engagement_type column.
• Created a backup of the existing custom object association tables in your destination to avoid data loss. The backup table names are in the following format: [TABLE_NAME]\_BACKUP\_[DATE].
• Synced the new custom object association tables, including their history, into your destination.

September 2024

We have added support for HubSpot's Custom Events API to sync the custom events and its definitions data in your HubSpot account. We are gradually rolling out this improvement to all existing connections.

August 2024

We have added support for HubSpot's Leads API to sync the leads and leads pipelines data in your HubSpot account. We are gradually rolling out this improvement to all existing connections.

We have added support for property history tables for custom objects. The new tables are named as <custom_object>_property_history and are located within the corresponding custom object tables.

April 2024

We now support table-level re-syncs for HubSpot connections.

We now support HubSpot's Goals API to sync the goals data in your HubSpot account. To support this enhancement, we have added the following new tables:

• <CUSTOM_OBJECT>_GOAL
• ENGAGEMENT_GOAL
• GOAL
• GOAL_COMPANY
• GOAL_CONTACT
• GOAL_DEAL
• GOAL_PROPERTY_HISTORY
• GOAL_TICKET

We are gradually rolling out these changes to all existing connections.

We now support HubSpot's Event Analytics API to sync the event analytics data in your HubSpot account. To support this enhancement, we have added a new table, EVENT. We are gradually rolling out this change to all existing connections.

October 2023

We have added the following new tables to support the HubSpot Quotes API:

• QUOTE
• QUOTE_COMPANY
• QUOTE_CONTACT
• QUOTE_DEAL
• QUOTE_LINE_ITEM
• QUOTE_PROPERTY_HISTORY

These tables are available by default for all HubSpot connections created after October 12, 2023. We are gradually rolling out these changes to all existing HubSpot connections.

We have introduced the following schema changes for connections created on or after October 17, 2023:

• We have upgraded to API v3 to sync the TICKET_PIPELINE, TICKET_PIPELINE_STAGE, DEAL_PIPELINE and DEAL_PIPELINE_STAGE tables.
• We have deprecated the active column for all the four tables mentioned above.
• We have added a new column, write_permissions, to the TICKET_PIPELINE_STAGE and DEAL_PIPELINE_STAGE tables.

We are gradually rolling out these changes to all existing HubSpot connections.

September 2023

We now perform a weekly table re-sync to capture soft deletes for the CONTACT_LIST_MEMBER table. We are gradually rolling out this feature to all existing connections.

We have added the following new tables to support the HubSpot Web Analytics API:

• GEOLOCATION_ANALYTICS_DAILY_REPORT
• GEOLOCATION_ANALYTICS_MONTHLY_REPORT
• GEOLOCATION_ANALYTICS_OVERALL_REPORT
• GEOLOCATION_ANALYTICS_WEEKLY_REPORT
• SESSIONS_ANALYTICS_DAILY_REPORT
• SESSIONS_ANALYTICS_MONTHLY_REPORT
• SESSIONS_ANALYTICS_OVERALL_REPORT
• SESSIONS_ANALYTICS_WEEKLY_REPORT
• SOURCES_ANALYTICS_DAILY_REPORT
• SOURCES_ANALYTICS_MONTHLY_REPORT
• SOURCES_ANALYTICS_OVERALL_REPORT
• SOURCES_ANALYTICS_WEEKLY_REPORT
• TOTALS_ANALYTICS_DAILY_REPORT
• TOTALS_ANALYTICS_MONTHLY_REPORT
• TOTALS_ANALYTICS_WEEKLY_REPORT
• UTM_ANALYTICS_DAILY_REPORT
• UTM_ANALYTICS_MONTHLY_REPORT
• UTM_ANALYTICS_OVERALL_REPORT
• UTM_ANALYTICS_WEEKLY_REPORT

We are gradually rolling out these changes to all HubSpot connections.

July 2023

We have changed our sync strategy for table properties. Now, depending on your table property selection in the Schema tab, we sync the property’s historical data to the associated property history table.

Now, in the connector’s Schema tab, if you deselect a property in the DEAL table, we won’t sync the history data of the property to the DEAL_PROPERTY_HISTORY table. Previously, we synced the property history data. The change in sync strategy impacts the following tables and the associated property history tables:

• COMPANY and COMPANY_PROPERTY_HISTORY
• CONTACT and CONTACT_PROPERTY_HISTORY
• DEAL and DEAL_PROPERTY_HISTORY
• ENGAGEMENT_CALL and ENGAGEMENT_PROPERTY_HISTORY
• ENGAGEMENT_COMMUNICATION and ENGAGEMENT_PROPERTY_HISTORY
• ENGAGEMENT_EMAIL and ENGAGEMENT_PROPERTY_HISTORY
• ENGAGEMENT_MEETING and ENGAGEMENT_PROPERTY_HISTORY
• ENGAGEMENT_NOTE and ENGAGEMENT_PROPERTY_HISTORY
• ENGAGEMENT_POSTAL_MAIL and ENGAGEMENT_PROPERTY_HISTORY
• ENGAGEMENT_TASK and ENGAGEMENT_PROPERTY_HISTORY
• LINE_ITEM and LINE_ITEM_PROPERTY_HISTORY
• PRODUCT and PRODUCT_PROPERTY_HISTORY
• TICKET and TICKET_PROPERTY_HISTORY

We have deprecated the following tables as HubSpot is sunsetting its Calendar API:

• CALENDAR_EVENT
• CALENDAR_TOPIC
• CALENDAR_USER

May 2023

We have added two new tables, ASSOCIATION_TYPE and CONTACT_COMPANY.

We have added two new columns, created_at and updated_at, to the following tables:

• DEAL_PIPELINE
• DEAL_PIPELINE_STAGE
• PROPERTY
• TICKET_PIPELINE
• TICKET_PIPELINE_STAGE

We have added the show_currency_symbol column to the PROPERTY table.

We have added a new column, type_id, to the following tables:

• DEAL_COMPANY
• DEAL_CONTACT

We have also included the type_id column as a part of the composite primary key for these tables. You can use the type_id column to identify primary associations.

These changes are available in all HubSpot connections created after May 8, 2023. We are gradually rolling out these changes to the existing HubSpot connections.

We have made the following schema changes to support HubSpot API v3:

• We have added the following new tables:

  • ENGAGEMENT_COMMUNICATION
  • ENGAGEMENT_POSTAL_MAIL
  • ENGAGEMENT_PROPERTY_HISTORY
  • LINE_ITEM_DEAL

• We no longer support the following tables:

  • ENGAGEMENT_PUBLISHING_TASK
  • ENGAGEMENT_EMAIL_BCC
  • ENGAGEMENT_EMAIL_CC
  • ENGAGEMENT_EMAIL_TO

• We have deprecated the following tables:

  • ENGAGEMENT_EMAIL_BCC
  • ENGAGEMENT_EMAIL_CC
  • ENGAGEMENT_EMAIL_TO

  The data from these deprecated tables will be available as columns in the ENGAGEMENT_EMAIL table. For more information, see HubSpot's Properties documentation.

• We have changed the primary key for a few ENGAGEMENT_* tables. The new composite primary key is a combination of the id and type columns. Previously, the id column was the primary key.

• To support the primary key change for older connectors, we have deleted the ENGAGEMENT_* tables and re-synced them.

• We have deprecated most of the existing columns of the ENGAGEMENT_* tables to standardize column naming conventions. We now sync the data only into the child tables' property_* columns. Check your HubSpot connector dashboard for the properties for each engagement type. However, we won't be able to create the new columns if you have set the Block all option in the SCHEMA CHANGE SETTINGS.

• We have deprecated the columns of the ENGAGEMENT table. We now sync the data into the child table's property_* columns.

• We no longer support the following columns in the tables below:

  Column	Table
  object_type	TICKET
  selected	LINE_ITEM_PROPERTY_HISTORY
  deal_id	LINE_ITEM

• To standardize the delete column, we have replaced the is_delete column with _fivetran_deleted column for the LINE_ITEM, TICKET, and PRODUCT tables. We will apply the changes to the older connectors as part of the migration.

• We have added a new table, LINE_ITEM_DEAL, to store data related to the association between line_item records and deal records.

• We have added a new column, type_id, to the following tables:

  • ENGAGEMENT_DEAL
  • ENGAGEMENT_COMPANY
  • ENGAGEMENT_CONTACT
  • TICKET_COMPANY
  • TICKET_CONTACT
  • TICKET_DEAL
  • TICKET_ENGAGEMENT

• We have added two new columns, source and, source_id, to the following tables:

  • LINE_ITEM_PROPERTY_HISTORY
  • PRODUCT_PROPERTY_HISTORY

These changes are available for all HubSpot connections created after May 12, 2023. We are gradually rolling out these changes to all existing HubSpot connections. See the HubSpot ERDs for more details.

We now use HubSpot API v3 to sync the following parent tables and their associated child tables:

• ENGAGEMENT

  • ENGAGEMENT_CALL
  • ENGAGEMENT_COMMUNICATION
  • ENGAGEMENT_COMPANY
  • ENGAGEMENT_CONTACT
  • ENGAGEMENT_DEAL
  • ENGAGEMENT_EMAIL
  • ENGAGEMENT_MEETING
  • ENGAGEMENT_NOTE
  • ENGAGEMENT_POSTAL_MAIL
  • ENGAGEMENT_PROPERTY_HISTORY
  • ENGAGEMENT_TASK

• LINE_ITEM

  • LINE_ITEM_DEAL
  • LINE_ITEM_PROPERTY_HISTORY

• PRODUCT

  • PRODUCT_PROPERTY_HISTORY

• TICKET

  • TICKET_COMPANY
  • TICKET_CONTACT
  • TICKET_DEAL
  • TICKET_ENGAGEMENT
  • TICKET_PROPERTY_HISTORY

New HubSpot connections created on or after May 12, 2023, will support this feature by default.

We are gradually rolling out the changes to all existing connections.

April 2023

We now use HubSpot API v1 to sync the following deprecated columns of the CONTACT_FORM_SUBMISSION table:

• conversion_id
• page_url
• title

Previously, we had deprecated these columns for connectors syncing the parent CONTACT table using API v3. This change only applies to HubSpot connections created on or after November 11, 2022, or connectors that use API v3 to sync the CONTACT table.

February 2023

For connections created after November 11, 2022, we have removed the sync dependency of the DEAL_STAGE table on the DEAL_PROPERTY_HISTORY table. To sync the DEAL_STAGE table, you no longer need to select the DEAL_PROPERTY_HISTORY table in the Schema tab. We are gradually rolling out this improvement for connections created before November 11, 2022.

November 2022

We now name custom object association tables using the format, [FROM_SCHEMA_NAME]_TO_[TO_SCHEMA_NAME].

The composite primary keys for the custom object association tables are the from_id, to_id, and type fields.

We will re-sync all the existing custom object association tables to reflect the changes.

We now use version HubSpot API v3 to sync the following parent tables and their associated child tables:

• DEAL
  • DEAL_STAGE
  • DEAL_CONTACT
  • DEAL_COMPANY
  • DEAL_PROPERTY_HISTORY
  • MERGED_DEAL
• CONTACT
  • CONTACT_PROPERTY_HISTORY
  • CONTACT_FORM_SUBMISSION
• COMPANY
  • COMPANY_PROPERTY_HISTORY

New HubSpot connections created on or after November 11, 2022, will support this feature by default. We are gradually rolling out this improvement to all existing connections.

For HubSpot connections created on or after November 11, 2022, we have made the following schema changes:

• We no longer support the following tables:

  • CONTACT_IDENTITY_PROFILE
  • CONTACT_MERGE_AUDIT
  • IDENTITY_PROFILE_IDENTITY
  The property_hs_calculated_merged_vids column of the CONTACT table stores the contact merge data.

• In the CONTACT_FORM_SUBMISSION table, we:

  • no longer support the conversion_id, page_url, and title columns.
  • have added a new column, page_id.
  • have changed the primary key. The new composite primary key is a combination of the contact_id, timestamp and form_id columns. Previously, the primary key was a combination of the contact_id and conversion_id columns.

• In the CONTACT table, we no longer support the merged_vids and canonical_vid columns.

• In the PROPERTY_OPTION table, we no longer support double_data and read_only columns.

• In the FORM table, we've added a new column form_type.

July 2022

We have added a new table, MERGED_DEAL. You can use this table to find the merged deals. To learn more, see Merge deals.

We have deprecated the is_merged column from the DEAL table. We will not delete the existing column from your destination table. For new records, we will populate this column as NULL in your destination table.

We now sync the OWNER table using version 3 of the HubSpot API. For more information, see HubSpot's API documentation. We no longer sync the following columns from the OWNER table because the new API version does not return them:

• portal_id
• type
• user_id_including_inactive

We will not delete the existing columns from your destination table. For new records, we will populate these columns as NULL in your destination table.

We have added the following new tables:

• OWNER_TEAM
• ROLE
• TEAM
• TEAM_USER
• USERS

To sync the TEAM, ROLE, and USERS tables, you must re-authenticate the connector because the endpoints need the settings.users.read and settings.users.teams.read scopes.

May 2022

The HubSpot connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. HubSpot's priority-first syncs fetch the most recent 24 hours' worth of data from the EMAIL_EVENT table and its child tables. To learn more, see our priority-first sync documentation.

Now, the EMAIL_EVENT table syncs data for only the event types you define in the source EMAIL_EVENT_* child tables. For more information, see our documentation.

February 2022

We have added support for custom objects. You can now sync custom objects from your HubSpot account to your destination. We create a destination table for each custom object. We are gradually rolling out this improvement to all our existing connections.

August 2021

The HubSpot connector now supports history mode for the following tables:

• COMPANY_PROPERTY_HISTORY
• CONTACT_PROPERTY_HISTORY
• DEAL_PROPERTY_HISTORY
• LINE_ITEM_PROPERTY_HISTORY
• PRODUCT_PROPERTY_HISTORY
• TICKET_PROPERTY_HISTORY

We are gradually rolling out this improvement to all existing connections. For more information about history mode, see our documentation.

July 2021

We have added a new primary key column, _fivetran_id, to the EMAIL_SUBSCRIPTION_CHANGE table. Be sure to update your queries.

June 2021

We have added the following new tables, to support HubSpot's Marketing Email API:

• MARKETING_EMAIL
• MARKETING_EMAIL_CAMPAIGN
• MARKETING_EMAIL_CONTACT
• MARKETING_EMAIL_CONTACT_LIST

May 2021

We now support incremental updates for the CONTACT_LIST_MEMBER table.

April 2021

We have added two new metadata tables, PROPERTY and PROPERTY_OPTION, to sync the properties associated with the following objects:

• company
• contact
• deal
• line_item
• product
• ticket

March 2021

We now re-sync the TICKET table if we find that the table hasn't been synced in the last 24 hours because of the Tickets API limitations. We re-sync the table to ensure data integrity.

We have added two new tables, TICKET_PIPELINE and TICKET_PIPELINE_STAGE to support HubSpot's pipelines object.

February 2021

We have added a new column, meeting_outcome, to the ENGAGEMENT_MEETING table.

We have added a new column, is_merged, to the DEAL table to track merged deals. If you'd like to sync historical data for this column, re-sync the DEAL table.

January 2021

We have added a new table, DEAL_STAGE which stores the dealstage properties data. Previously, we synced the dealstage data to the DEAL_PROPERTY_HISTORY table. The HubSpot API returns only the date_entered value. Use the date_entered and date_exited values to calculate the time_in value.

December 2020

We have added a new child table, CALENDAR_TOPIC, to the CALENDAR_EVENT table.

We have added the following new columns to the OWNER table:

• is_active
• active_user_id
• user_id_including_inactive

November 2020

We have expanded the public API endpoints Create a connection and Update a connection. Now you can authorize the following connectors by adding the auth section to payloads:

• Google Campaign Manager 360
• Google Ads
• Google Sheets
• HubSpot

We have added the following new tables to support HubSpot's Tickets API:

• TICKET
• TICKET_COMPANY
• TICKET_CONTACT
• TICKET_DEAL
• TICKET_ENGAGEMENT
• TICKET_PROPERTY_HISTORY

See our Service Hub schema for more information.

October 2020

We now support future timestamp values in the ENGAGEMENT_MEETING table. If you previously synced future timestamp values, re-sync the table to ensure data integrity.

September 2020

We have added a new child table, CALENDAR_USER, to the CALENDAR_EVENT table.

August 2020

We have released pre-built, dbt Core-compatible data models for HubSpot. Find the models in Fivetran's dbt hub or data models documentation. Learn more about our dbt Core integration in our Transformations for dbt Core documentation.

We now use webhooks to capture deletes for the COMPANY, CONTACT, and DEAL tables. We are gradually rolling out this new feature to all existing connections. If you'd like to enable this feature on your connector, contact our support team.

July 2020

We have added a warning to your Fivetran dashboard that asks you to increase your sync frequency if your COMPANY and COMPANY_PROPERTY_HISTORY tables have huge recurring updates. Previously, if these tables had more than 9900 updates, we initiated a complete re-sync to prevent data integrity issues. The re-sync caused high MAR (monthly active rows) consumption. You can prevent these re-syncs and avoid impact on your MAR by increasing your sync frequency.

May 2020

You can now configure your HubSpot connector using the Fivetran REST API. This feature is in BETA and is available only for Standard and Enterprise accounts.

April 2020

We now support future timestamp values in the following tables:

• CALENDAR_EVENT
• COMPANY_PROPERTY_HISTORY
• CONTACT_FORM_SUBMISSION
• CONTACT_PROPERTY_HISTORY
• DEAL_PROPERTY_HISTORY
• EMAIL_SUBSCRIPTION_CHANGE
• ENGAGEMENT
• LINE_ITEM_PROPERTY_HISTORY
• IDENTITY_PROFILE_IDENTITY

If you have previously synced future timestamp values, re-sync the tables to ensure data integrity.

March 2020

We have added three new fields to the CONTACT table:

• canonical_vid
• merged_vids
• profile_url

We have added three new tables:

• CONTACT_MERGE_AUDIT
• CONTACT_IDENTITY_PROFILE
• IDENTITY_PROFILE_IDENTITY

August 2019

We have added a new column, activityType, to the ENGAGEMENT table.

July 2019

We have added the table blocking feature to all HubSpot tables. You can now choose which tables you'd like to sync or omit from syncing. To select or deselect tables, go to the Schema page of your Fivetran dashboard.

If you want to sync a child table, you must also sync its parent table.

May 2019

Changes made through contact batch updates are processed asynchronously, so it can take several minutes for changes to be applied to contact records. To capture all the changes, once a day we take the cursor back by 1 day to capture all the updates.

February 2019

We now automatically sync new fields in the ENGAGEMENT_* tables.

January 2019

We have added a new column, web_conference_meeting_id, to the ENGAGEMENT_MEETING table.

We have added a new column, unknown_visitor_conversation, to the ENGAGEMENT_CALL table.

September 2018

We have added a new column, transcription_id, to the ENGAGEMENT_CALL table.

The HubSpot connector can now sync ecommerce data for your Sales Hub, including products and line items. We have added the following tables to support this feature:

• PRODUCT
• PRODUCT_PROPERTY_HISTORY
• LINE_ITEM
• LINE_ITEM_PROPERTY_HISTORY

August 2018

We have added two new columns, attachedVideoOpened and attachedVideoWatched, to the ENGAGEMENT_EMAIL table.

July 2018

We have added the media_processing_status column to the ENGAGEMENT_EMAIL table.

May 2018

We have added two new fields, callee_object_type and callee_object_id, to the ENGAGEMENT_CALL table.

April 2018

We have added the following new columns to the tables below:

We will now re-sync the entire ENGAGEMENTS table when there are more than 10,000 changed records, because HubSpot can no longer complete incremental queries to the engagements endpoint when there are so many changed records.

Some HubSpot records have very old timestamps (for example,Jan 1 1970). These values no longer cause our syncs to fail.