Smaily to Azure Synapse Integration

How Datrise loads Smaily into Azure Synapse

Datrise syncs Smaily's subscribers, campaigns, lists, autoresponders, email events, and segments 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

Smaily: Email and SMS campaigns with subscriber segments.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Smaily entities map to Azure Synapse

Smaily entity	Azure Synapse object	Notes
subscribers	`smaily_subscribers`	id PK · custom fields → NVARCHAR(MAX) JSON columns
campaigns	`smaily_campaigns`	id PK · linked to smaily_subscribers
lists	`smaily_lists`	id PK · linked to smaily_subscribers
autoresponders	`smaily_autoresponders`	id PK · linked to smaily_subscribers

FAQ

How does Datrise handle Smaily'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 Smaily 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 Smaily 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.