As HubSpot plans to sunset the v1 contact lists API on September 30, 2025, any API requests using this version for contacts or lists endpoints will begin to fail after that date. To ensure continuity, Qlik has released a new version, v4, of the connector.
The changes in questions are:
Schema change, primary key, replication key change for contacts stream
Schema change for contact_lists stream
What action do I need to take?
Upgrade to the new version. There are two ways to upgrade.
Upgrade and change the schema name
If you do not mind changing the schema name, you can do so by simply creating a new HubSpot integration and deleting the old one.
This is the recommended method. Creating a new integration with a different schema name means you will also benefit from a free historical re-sync of your data.
Upgrade using the same destination schema
If you prefer to reuse the same destination schema name:
Pause the existing integration from their Stitch account.
Wait for any records that arebeing preparedfor loading to be loaded.
Take note of the tables and fields tracked for replication, as well as the replication methods defined for these tables.
Delete the existing integration from your Stitch account.
Drop the schema from your destination data warehouse(or rename it if you'd like to continue working from this data as Stitch completes a new historical replication).
Contact Qlik Stitch Support to coordinate a manual row-usage exemption for this connection.
Configure a new integration with the same name, and Stitch will create this schema in your destination during the loading process.
If you have any questions, we're happy to assist. Contact us using chat or ask similar queries in theQlik Stitch forum.
