DatriseAI-first ETL

Kommo Azure Synapse

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

How Datrise loads Kommo into Azure Synapse

Datrise syncs Kommo's conversational CRM events, chats, leads, and sales automation triggers 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

Kommo: Conversational CRM for WhatsApp, chat funnels, and sales automation.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Kommo entities map to Azure Synapse

Kommo entityAzure Synapse objectNotes
conversational CRM eventskommo_conversational_crm_eventsdatetime2 events
chatskommo_chatsid PK · linked to kommo_conversational_crm_events
leadskommo_leadsid PK · linked to kommo_conversational_crm_events
sales automation triggerskommo_sales_automation_triggersid PK · linked to kommo_conversational_crm_events

FAQ

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