DatriseAI-first ETL

EspoCRM Azure Synapse

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

How Datrise loads EspoCRM into Azure Synapse

Datrise syncs EspoCRM's pipeline entities, custom objects, and process automation events 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

EspoCRM: Open-source CRM for pipeline management and custom entity modeling.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How EspoCRM entities map to Azure Synapse

EspoCRM entityAzure Synapse objectNotes
pipeline entitiesespocrm_pipeline_entitiesid PK · custom fields → NVARCHAR(MAX) JSON columns
custom objectsespocrm_custom_objectsid PK · linked to espocrm_pipeline_entities
process automation eventsespocrm_process_automation_eventsdatetime2 events

FAQ

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