Skip to content
CRM ⇄ Database

Kommo to MySQL integration — real-time, two-way sync

Keep Kommo and MySQL in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Kommo and MySQL

Treat Kommo like part of your database: its records live in MySQL as real tables, and writes in either place sync to the other in seconds.

Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in MySQL, where it can be queried and joined like everything else.

Stacksync mirrors Chats, Leads, Contacts, Companies from Kommo into Tables, Views, Columns, Primary and Unique Keys in MySQL with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Kommo with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.

Common use cases

  • 01 Keep customer records consistent between Kommo and invoicing or ERP systems
  • 02 Mirror pipeline stage changes into BI tools for forecasting
  • 03 Keep e-commerce orders in MySQL flowing into finance and fulfillment systems without export scripts
  • 04 Feed a warehouse from MySQL continuously using binlog-based capture instead of nightly dumps

Common sync patterns

Query the CRM like a database

Accounts, contacts, and custom objects from Kommo become tables in MySQL you can join with application data directly.

Product events onto CRM records

Signup, usage, or lifecycle changes written to MySQL sync onto the matching records in Kommo, giving go-to-market teams live product context.

Internal tools without API code

Back-office apps read and write the synced tables; Stacksync handles the Kommo API, limits, and retries.

What you can sync between Kommo and MySQL

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Kommo objects MySQL objects How this pairing syncs
Pipelines & Statuses Stage definitions structure lead progress and drive stage-change syncs to reporting tools. Triggers An alternative change-capture mechanism when binlog access is unavailable. Pipelines & Statuses is specific to Kommo and Triggers to MySQL — each maps to any object or custom field on the other side.
Tasks Follow-up records keep rep activity consistent across systems. Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. Tasks is specific to Kommo and Databases (Schemas) to MySQL — each maps to any object or custom field on the other side.
Notes Free-text and system notes attach context to synced leads and contacts. Tables The primary sync target; rows map to records in connected systems. Notes is specific to Kommo and Tables to MySQL — each maps to any object or custom field on the other side.
Custom Fields Per-entity custom fields hold data written from external databases and enrichment. Views Read-side projections used as outbound sync sources. Custom Fields is specific to Kommo and Views to MySQL — each maps to any object or custom field on the other side.
Users Account users map lead ownership to people in other systems. Columns Field-level mapping targets with engine-typed values. Users is specific to Kommo and Columns to MySQL — each maps to any object or custom field on the other side.
Chats Messenger conversations from WhatsApp, Instagram, and other channels attach to leads and contacts. Primary and Unique Keys Match keys for idempotent upserts and conflict handling. Chats is specific to Kommo and Primary and Unique Keys to MySQL — each maps to any object or custom field on the other side.

How changes propagate between Kommo and MySQL

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Kommo MySQL Sub-second propagation

DetectionKommo notifies Stacksync of record changes through webhook events. Webhooks on record add and update events, plus polling for backfill.

DeliveryEach detected change is applied to MySQL as a row-level write, with types converted between the two schemas.

MySQL Kommo Sub-second propagation

DetectionChanges in MySQL are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when.

DeliveryEach detected change is written to Kommo through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Kommo: Subject to per-account request rate limits.
  • MySQL: No API rate limits; throughput is bounded by connection limits and server resources.
What ships with Kommo ⇄ MySQL

Connect Kommo and MySQL for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Kommo–MySQL connection.

Real-time

Two-way sync

Changes in Kommo or MySQL instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Kommo or MySQL data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Kommo or MySQL record.

Observability

Monitoring

Track your Kommo ⇄ MySQL sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Kommo and MySQL.

How the Kommo and MySQL connectors work

Kommo

Integration surface
REST API
Authentication
OAuth 2.0 with refresh tokens
Change detection
Webhooks on record add and update events, plus polling for backfill
Capabilities
read · write · webhooks
Rate limits
Subject to per-account request rate limits

MySQL

Integration surface
SQL wire protocol (MySQL client/server protocol)
Authentication
Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host)
Change detection
Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when binary logging is enabled)
Capabilities
read · write · CDC
Rate limits
No API rate limits; throughput is bounded by connection limits and server resources
MySQL setup guide
How it works

How to connect Kommo to MySQL — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Kommo and MySQL with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Kommo connected
    MySQL connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Kommo and MySQL objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Kommo ⇄ MySQL
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Kommo MySQL
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Kommo and MySQL integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 558 integrations available for Kommo and MySQL.

Popular · 8 of 558
All Kommo integrations All MySQL integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own