DatriseAI-first ETL

Salesforce Azure Synapse

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

How Datrise loads Salesforce into Azure Synapse

Datrise syncs Salesforce's accounts, opportunities, contacts, tasks, and pipeline stage history 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

Salesforce: Enterprise CRM and Customer 360 platform.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Salesforce entities map to Azure Synapse

Salesforce entityAzure Synapse objectNotes
accountssalesforce_accountsid PK · custom fields → NVARCHAR(MAX) JSON columns
opportunitiessalesforce_opportunitiesid PK · linked to salesforce_accounts
contactssalesforce_contactsid PK · linked to salesforce_accounts
taskssalesforce_tasksid PK · linked to salesforce_accounts

FAQ

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