Deprecation Notices

HubSpot Contact Lists API Deprecation

Based on the following HubSpot changelog article: Upcoming Sunset: V1 Lists API, HubSpot has planned some specific breaking changes to the HubSpot schema of the HubSpot Driver, including the removal of specific tables.

The following table summarizes the tables affected by the deprecation of the Contact Lists API and the corresponding changes we have made in both Hubspot and HubSpotV3 schemas of the driver.

Please note that these changes are not final and may be adjusted based on further announcements or updates from the HubSpot API team. Refer to the HubSpot changelog article for the latest updates.


Table	V1 Status	V3 Status
Contacts	Partially affected. Columns related to lists and memberships (for example, ListMembershipsAggregate) will be removed.	Table remains with similar capabilities, but list membership aggregation is no longer included. Use the new ListMemberships table to retrieve this data.
ContactListMemberships	The API endpoint will stop returning list membership data. This table has been removed.	A new ListMemberships table has been introduced, covering multiple object types (not just contacts). However, due to API changes, the Email column will no longer be available.
ContactLists	HubSpot plans to sunset this endpoint. This table has been removed.	A new Lists table has been introduced, supporting multiple object types. It includes an ObjectTypeId column, and most other columns will remain the same with minor adjustments.
ContactsInList	HubSpot plans to sunset this endpoint. This table has been removed.	There will be no direct replacement, but similar functionality may be achieved using subqueries on the Contacts and ListMemberships tables. Example: `SELECT [*] FROM [Contacts] WHERE [Id] IN (SELECT [ObjectId] FROM [ListMemberships] WHERE [ObjectTypeId] = '0-1')`
Enrollments	The Enrollment can no longer retrieve all records in a single query. To query Enrollments, you must specify an Id in the filter, for example: `SELECT * FROM Enrollment WHERE Id = [id]`.	There is no equivalent for this endpoint in the V3 schema.

Other Tables Potentially Affected

The following tables might also be partially or fully impacted. However, according to the current HubSpot documentation, their related endpoints are expected to remain functional even after the Contact Lists API is sunset:

HubSpot has indicated that these endpoints will continue to work, but they will no longer return list membership information. Therefore, it is likely that these tables will remain functional in the driver.

Recommendation

We strongly advise customers to transition to the HubSpotV3 schema for all new development and to migrate existing implementations when possible. The V3 schema is more stable, actively maintained by HubSpot, and offers significantly improved functionality with regular updates and enhancements. The legacy HubSpot schema will become increasingly outdated over time, receiving fewer updates and missing out on new features and optimizations being implemented in the V3 API.

HubSpot Marketing Email V1 API Deprecation

Based on the following HubSpot changelog article: Upcoming Sunset: V1 Marketing Email API, HubSpot has announced breaking changes to the HubSpot schema of the HubSpot Driver, including the migration of email-related endpoints to V3.

The following table summarizes the tables affected by the deprecation of the Marketing Email V1 API and the corresponding changes we have made in both Hubspot and HubspotV3 schemas of the driver.