Does the Azure Data Factory HubSpot connector v2.0 (Preview) support incremental load?

Question

Does the Azure Data Factory HubSpot connector v2.0 (Preview) support incremental load?

Tariq Riahi 0

The HubSpot connector 1.0 supported incremental loads by means of passing a query. The new 2.0 connector does not support queries. Does that mean the new connector does not support incremental loads, or is there some other option? Fetching all of the data to staging would be highly inefficient and unusable.

0 comments

2 answers

Your answer

Answer 1

Tariq Riahi 0

Hi @Pilladi Padma Sai Manisha

Thanks for the explanation. I understand that the query property used in HubSpot connector v1.0 is no longer available in v2.0.

However, I am still unclear whether incremental extraction is actually supported by the v2.0 connector.

For example, when loading objects such as Contacts, Leads, Calls, and similar HubSpot entities using Copy Activity, can the v2.0 connector retrieve only records changed since a given timestamp (for example hs_lastmodifieddate > @watermark), or does it always read the full object and require filtering after the data has already been extracted?

In other words, is there a documented source-side incremental/delta extraction capability in the v2.0 connector that replaces the v1.0 query functionality, or is full extraction/REST API currently the only supported approach?

I worry that retrieving the full dataset every night might keep the pipeline occupied for too long.

Pilladi Padma Sai Manisha 10,770 Reputation points Microsoft External Staff Moderator

2026-06-17T03:56:55.41+00:00
Thanks for the clarification @Tariq Riahi

Based on the current documentation, HubSpot connector v2.0 (Preview) does not have a documented source-side incremental/delta extraction capability that replaces the query functionality available in v1.0.

For Copy Activity, there is currently no documented way to apply filters such as hs_lastmodifieddate > @watermark at the source level. The connector primarily uses tableName and doesn't expose built-in support for server-side filtering or native incremental loading.

If incremental ingestion is required, the recommended options are:

Implement a custom watermark strategy outside the connector, if supported by the HubSpot object.

Use the HubSpot REST APIs via the REST connector for true source-side delta extraction.

Otherwise, a full extraction would be required.

So, there is currently no documented built-in replacement for the v1.0 query-based incremental load capability in v2.0 (Preview).
Pilladi Padma Sai Manisha 10,770 Reputation points Microsoft External Staff Moderator

2026-06-18T05:57:20.4233333+00:00

Hi @Tariq Riahi
Could you please review the above response and please let us know if you have any queries.
Pilladi Padma Sai Manisha 10,770 Reputation points Microsoft External Staff Moderator

2026-06-19T09:20:54.77+00:00

Hi
Just checking in to see if you have got a chance to see my response to your question in resolving the issue.

If you feel that your quires have been resolved, please accept the answer by clicking the "Upvote" and "Accept Answer" on the post.

Thank you!

Answer 2

Pilladi Padma Sai Manisha 10,770 Microsoft External Staff Moderator

Hi @Tariq Riahi

You're correct that the HubSpot connector v2.0 (Preview) no longer supports the query property, which was commonly used in v1.0 to implement incremental loads.

As a result, the v1.0 query-based incremental pattern doesn't carry over to v2.0.

The current v2.0 documentation focuses on accessing supported HubSpot objects via tableName, and it does not describe an equivalent built-in incremental load capability that replaces query.

If incremental ingestion is required, you'll likely need to implement it at the ADF pipeline level, for example:

Maintain a watermark value (such as a last modified timestamp or ID).
Store the latest processed value in an external control table or metadata store.
Use pipeline logic to process only new or changed records where possible.

If you're migrating from v1.0 and depend heavily on query-based delta extraction, you may want to validate whether your specific HubSpot objects expose fields that can support a custom watermark strategy before moving to v2.0.

Documentation:

If you can share which HubSpot objects/tables you're loading and whether you're using Copy activity or Mapping Data Flows, we can suggest a more specific incremental loading pattern.

Pilladi Padma Sai Manisha 10,770 Reputation points Microsoft External Staff Moderator

2026-06-16T07:20:52.5566667+00:00

Hi @Tariq Riahi
Following up to see if the below answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Tariq Riahi 0 Reputation points

2026-06-17T11:15:00.8033333+00:00

Hi @Pilladi Padma Sai Manisha , please see my above message.