Batches sized by width
Two thousand parameters divided by the column count.
Replicate HubSpot into Azure SQL with Polytomic so CRM records are queryable in T-SQL. Azure SQL caps a statement at two thousand parameters, so ETL sizes each batch as two thousand divided by your column count, and a wide CRM object means smaller batches.
Two thousand parameters divided by the column count.
Contact, company and deal changes as their own tables.
Discovered automatically, refreshed every twelve hours.
Polytomic is bi-directional by default, so you can move data the other way just as easily.
Azure SQL to HubSpot
Jonathan Krangel
VP Global Head of Revenue Operations
“Polytomic handles so many ETL and sync jobs at Cursor. They are a true partner to us.”
Follow these simple steps to connect HubSpot with Azure SQL in minutes
Connect HubSpot
Connect Azure SQL
Create sync
Enable sync
Connect HubSpot to Polytomic with OAuth, granting the scopes for the objects you need.
Connect Azure SQL to Polytomic with server, database, and SQL authentication credentials.
Sync data in either direction between HubSpot and Azure SQL. Choose the source data and destination objects for the direction you need.
Map the fields, choose the sync schedule and behavior, then save and enable the sync.
Get answers to common questions about the integration process
Sync data in either direction between HubSpot and Azure SQL.
Use both integrations' source and destination capabilities in one managed sync workflow.
Enterprise encryption and security protocols ensure your data remains protected.
Get up and running in minutes with our step-by-step integration guide.