DatriseAI-first ETL

Freshsales Azure Synapse

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

How Datrise loads Freshsales into Azure Synapse

Datrise syncs Freshsales's leads, contacts, deals, calls, and email activity telemetry 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

Freshsales: CRM by Freshworks with built-in phone and email.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Freshsales entities map to Azure Synapse

Freshsales entityAzure Synapse objectNotes
leadsfreshsales_leadsid PK · custom fields → NVARCHAR(MAX) JSON columns
contactsfreshsales_contactsid PK · linked to freshsales_leads
dealsfreshsales_dealsid PK · linked to freshsales_leads
callsfreshsales_callsid PK · linked to freshsales_leads

FAQ

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