folk to Azure Synapse Integration
AI-first ETL from folk into Azure Synapse. Governed entities, incremental sync, typed landing tables.
How Datrise loads folk into Azure Synapse
Datrise syncs folk's contacts, groups, deals, custom fields, interactions, and reminders 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
folk: Lightweight relationship CRM built on shared contact groups.
Azure Synapse: Microsoft analytics workspace with SQL pools.
How folk entities map to Azure Synapse
| folk entity | Azure Synapse object | Notes |
|---|---|---|
| contacts | folk_contacts | id PK · custom fields → NVARCHAR(MAX) JSON columns |
| groups | folk_groups | id PK · linked to folk_contacts |
| deals | folk_deals | id PK · linked to folk_contacts |
| custom fields | folk_custom_fields | id PK · linked to folk_contacts |
FAQ
How does Datrise handle folk'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 folk to Azure Synapse sync stay up to date?
It runs incrementally — Datrise uses COPY into staging, then a MERGE on stable id.
Related pipelines
More destinations for folk
More sources for Azure Synapse
Early access
Connect folk 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.