You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These fields are being removed due to the fields no longer being available via the HubSpot v3 API and as a result are no longer available in the contact_list source table.
Migration Path / Alternatives
In order to successfully migrate, users will need to ensure they are not relying on the above mentioned fields. Additionally, the properties_* fields are now synced in the contact_list source table. These fields may be relied upon. If you feel there are any important properties_* fields, let us know here and we can be sure to add those in before the full sunsetting of the above mentioned fields.
Additional Context or Notes
The text was updated successfully, but these errors were encountered:
fivetran-joemarkiewicz
changed the title
[Deprecation] CONTACT_LIST Fields - Planned Removal Date 05-10-2025
[Deprecation] CONTACT_LIST Fields
Feb 24, 2025
Planned Removal Date
May 10th, 2025
Original Deprecation Issue Link
HubSpot Transform Issue #155
Original Deprecation PR Link
HubSpot Source PR #137
Deprecated Item Type
Deprecated Item
The following fields are slated to be removed from the stg_hubspot__contact_list model:
Rationale and Impact Analysis
These fields are being removed due to the fields no longer being available via the HubSpot v3 API and as a result are no longer available in the
contact_list
source table.Migration Path / Alternatives
In order to successfully migrate, users will need to ensure they are not relying on the above mentioned fields. Additionally, the
properties_*
fields are now synced in thecontact_list
source table. These fields may be relied upon. If you feel there are any importantproperties_*
fields, let us know here and we can be sure to add those in before the full sunsetting of the above mentioned fields.Additional Context or Notes
The text was updated successfully, but these errors were encountered: