Question 1

What can Polytomic pull from HubSpot into Redshift?

Accepted Answer

The CRM objects, covering companies, contacts, deals, line items, products, tickets, meetings, calls, emails, notes, tasks, invoices, owners and your custom objects. Alongside those sit property histories, associations, engagements, forms and submissions, lists and memberships, pipelines, marketing events, email events and campaigns, workflows and subscription changes. Custom properties are discovered dynamically, and association labels you defined yourself are exposed as fields.

Question 2

What happens in Redshift when someone adds a property in HubSpot?

Accepted Answer

New source columns are selected automatically by default and added to the destination with an ALTER TABLE, so a property added in HubSpot shows up in Redshift without you rebuilding anything. Two things to know. Columns dropped at the source are kept in the data warehouse rather than removed, so old fields linger until you clean them up. And if a property changes to an incompatible type, the old column is renamed with its previous type appended and a fresh column takes the original name.

Question 3

How do incremental reads work?

Accepted Answer

For the primary CRM objects, the HubSpot Search API finds records changed since the last run by last modified date, then a batch read fetches the full set of properties and associations for those records. The first load uses the list API instead, because there is nothing to compare against yet. Some event style datasets carry their own timestamp cursors rather than going through search. All of it happens inside a single ETL run rather than as separate pipelines.

Question 4

Are deleted or archived records reflected?

Accepted Answer

Not through incremental reads, and this is worth designing around rather than discovering later. The HubSpot incremental API does not report deletions, so a record removed in HubSpot will not be marked as removed in Redshift by an incremental run. The options are full refresh mode, or periodic full resyncs so reconciliation removes rows no longer present. Some entity types expose an archived or deleted timestamp field, but that is not general delete tracking across the CRM.

Question 5

Why replicate HubSpot into a data warehouse?

Accepted Answer

Mostly for history and for joins. HubSpot reflects current state well, but nothing in it stamps a deal amount historically in a way you can query, so questions about how a quarter actually developed are hard to answer from the CRM alone. ETL into a data warehouse gives you that history at your own grain, and puts CRM records next to product usage, billing and support data so the joins people keep asking for become ordinary SQL.

Sync HubSpot to Redshift

Sync HubSpot to Redshift with Polytomic

Property history included

Custom properties discovered

Objects and associations

Or sync Redshift to HubSpot

Trusted by businesses worldwide

Step-by-step integration guide

Connect HubSpot in Polytomic

Connect Redshift in Polytomic

Create a sync between HubSpot and Redshift

Map fields and enable the sync

Frequently asked questions

The sync and ETL platform that does it all

Powerful data sync

Advanced analytics

Enterprise security

Easy setup

Ready to connect HubSpot with Redshift?