DatriseAI-first ETL

CallRail to Azure Synapse Integration

AI-first ETL from CallRail into Azure Synapse. Governed entities, incremental sync, typed landing tables.

How Datrise loads CallRail into Azure Synapse

Datrise syncs CallRail's calls, trackers, form submissions, sources, call outcomes, and recordings 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

CallRail: Call tracking and marketing attribution.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How CallRail entities map to Azure Synapse

CallRail entityAzure Synapse objectNotes
callscallrail_callsid PK · custom fields → NVARCHAR(MAX) JSON columns
trackerscallrail_trackersid PK · linked to callrail_calls
form submissionscallrail_form_submissionsid PK · linked to callrail_calls
sourcescallrail_sourcesid PK · linked to callrail_calls

FAQ

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