Kommo → MySQL
AI-first ETL from Kommo into MySQL. Governed entities, incremental sync, typed landing tables.
How Datrise loads Kommo into MySQL
Datrise syncs Kommo's conversational CRM events, chats, leads, and sales automation triggers into MySQL as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME/TIMESTAMP.
Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.
Ideal for operational reporting and app databases already standardized on MySQL.
Endpoints
Kommo: Conversational CRM for WhatsApp, chat funnels, and sales automation.
MySQL: Widely used OSS relational engine (InnoDB).
How Kommo entities map to MySQL
| Kommo entity | MySQL object | Notes |
|---|---|---|
| conversational CRM events | kommo_conversational_crm_events | DATETIME/TIMESTAMP events |
| chats | kommo_chats | id PK · linked to kommo_conversational_crm_events |
| leads | kommo_leads | id PK · linked to kommo_conversational_crm_events |
| sales automation triggers | kommo_sales_automation_triggers | id PK · linked to kommo_conversational_crm_events |
FAQ
How does Datrise handle Kommo's custom fields in MySQL?
Flexible values are stored as JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native MySQL types.
How does the Kommo to MySQL sync stay up to date?
It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.
Related pipelines
More destinations for Kommo
Early access
Connect Kommo to MySQL 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.