Aircall to Microsoft SQL Server Integration

How Datrise loads Aircall into Microsoft SQL Server

Datrise syncs Aircall's calls, users, teams, phone numbers, tags, and call recordings into Microsoft SQL Server 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 a watermark on updated-at, applied with a MERGE statement, so re-runs update only what changed. Optional partitioned tables on a date partition function. SQL Server defaults to a case-insensitive collation, so Datrise preserves original casing in a metadata column to avoid silent key collisions.

Ideal for Microsoft-stack analytics and Power BI Import models.

Endpoints

Aircall: Cloud phone system for sales and support teams.

Microsoft SQL Server: Microsoft relational DB with enterprise features.

How Aircall entities map to Microsoft SQL Server

Aircall entity	Microsoft SQL Server object	Notes
calls	`aircall_calls`	id PK · custom fields → NVARCHAR(MAX) JSON columns
users	`aircall_users`	id PK · linked to aircall_calls
teams	`aircall_teams`	id PK · linked to aircall_calls
phone numbers	`aircall_phone_numbers`	id PK · linked to aircall_calls

FAQ

How does Datrise handle Aircall's custom fields in Microsoft SQL Server?

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 Microsoft SQL Server types.

How does the Aircall to Microsoft SQL Server sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with a MERGE statement.

Related pipelines

Early access

Connect Aircall to Microsoft SQL Server 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.