Drift to Azure Synapse Integration

How Datrise loads Drift into Azure Synapse

Datrise syncs Drift's conversations, contacts, playbooks, meetings, messages, and accounts into Azure Synapse as a typed table per source entity. Flexible or custom fields land in NVARCHAR(MAX) JSON columns, and timestamps such as created, updated, and status changes are typed as datetime2.

Sync is incremental: Datrise uses COPY into staging, then a MERGE on stable id, so re-runs update only what changed. Hash distribution on the join id with date partitioning on facts. Synapse dedicated pools reward good hash-distribution choices, so Datrise distributes on entity ids to avoid data-movement-heavy joins.

Ideal for Azure analytics estates feeding Power BI.

Endpoints

Drift: Conversational marketing and sales chat.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Drift entities map to Azure Synapse

Drift entity	Azure Synapse object	Notes
conversations	`drift_conversations`	id PK · custom fields → NVARCHAR(MAX) JSON columns
contacts	`drift_contacts`	id PK · linked to drift_conversations
playbooks	`drift_playbooks`	id PK · linked to drift_conversations
meetings	`drift_meetings`	id PK · linked to drift_conversations

FAQ

How does Datrise handle Drift's custom fields in Azure Synapse?

Flexible values are stored as NVARCHAR(MAX) JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Azure Synapse types.

How does the Drift to Azure Synapse sync stay up to date?

It runs incrementally — Datrise uses COPY into staging, then a MERGE on stable id.

Related pipelines

Early access

Connect Drift to Azure Synapse the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.