Front to Microsoft SQL Server Integration

How Datrise loads Front into Microsoft SQL Server

Datrise syncs Front's conversations, messages, contacts, inboxes, tags, and teammates 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

Front: Shared inbox for team email and messaging.

Microsoft SQL Server: Microsoft relational DB with enterprise features.

How Front entities map to Microsoft SQL Server

Front entity	Microsoft SQL Server object	Notes
conversations	`frontapp_conversations`	id PK · custom fields → NVARCHAR(MAX) JSON columns
messages	`frontapp_messages`	id PK · linked to frontapp_conversations
contacts	`frontapp_contacts`	id PK · linked to frontapp_conversations
inboxes	`frontapp_inboxes`	id PK · linked to frontapp_conversations

FAQ

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