Skip to content
CRM ⇄ E-commerce

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

Keep Kommo and Magento 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 Magento

Keep the customers and orders that Kommo and Magento share aligned in real time, so sales works from live purchase history and the store works from current account details.

Kommo holds the customer relationship: the contacts, accounts, and deals a go-to-market team works. Magento runs the buying side: who placed which order, what they bought, and where it ships. The two describe the same people and companies, and when they are connected only by exports, sales answers questions without recent orders in front of them while the store works from account details that changed weeks ago.

Stacksync links Pipelines & Statuses, Tasks, Notes, Custom Fields in Kommo to Invoices, Shipments, Carts / quotes, Products in Magento with bi-directional, real-time sync. New customers, order activity, and corrected contact details move in whichever direction you configure, field by field, with conflicts resolved by rules you set. A record created or changed on either side shows up on the other within seconds, with no CSV exports and no nightly job.

The shared entity is the customer, matched on email or an external ID, so both systems agree on who the buyer is and the order history sits next to the relationship instead of in a separate tab.

Common use cases

  • 01 Mirror pipeline stage changes into BI tools for forecasting
  • 02 Route leads that originate in WhatsApp or Instagram conversations into other systems of record
  • 03 Sync Orders, invoices, and shipments from Magento into Postgres or a warehouse for revenue, margin, and fulfillment-SLA reporting.
  • 04 Master Products, prices, and Category assignments in an ERP or PIM and write them into Magento's catalog by SKU.

Common sync patterns

One customer identity across sales and store

A person who exists as a contact in Kommo and a buyer in Magento is kept as a single, deduplicated record, so both teams work from the same customer instead of two partial copies.

Where Magento records orders: purchase history on the account

Orders and their status from Magento appear on the matching contact or account in Kommo, so reps see what a customer has bought and what is in flight before the next conversation.

New buyers become CRM records

A customer created in Magento creates or updates the matching contact or account in Kommo, so first-time and repeat buyers land in the relationship system without a manual import.

What you can sync between Kommo and Magento

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 Magento objects How this pairing syncs
Custom Fields Per-entity custom fields hold data written from external databases and enrichment. Orders Sales orders with line items, totals, and status; typically read out of Magento into a warehouse or ERP for fulfillment and revenue reporting. Custom Fields is specific to Kommo and Orders to Magento — each maps to any object or custom field on the other side.
Users Account users map lead ownership to people in other systems. Customers Customer accounts and address book; synced two-way with a CRM so order history and contact records stay consistent. Users is specific to Kommo and Customers to Magento — 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. Inventory source items (MSI) Per-source stock quantities under Multi-Source Inventory; written from a WMS/ERP so storefront stock matches the warehouse. Chats is specific to Kommo and Inventory source items (MSI) to Magento — each maps to any object or custom field on the other side.
Leads The central pipeline record; external signups and form fills sync in as leads. Invoices Invoice documents tied to orders; read out for finance and revenue recognition, or created via the sales API when billing downstream. Leads is specific to Kommo and Invoices to Magento — each maps to any object or custom field on the other side.
Contacts Person records sync with other CRMs and databases for a shared contact file. Shipments Shipment and tracking records against orders; created or read to drive fulfillment status between Magento and a 3PL/WMS. Contacts is specific to Kommo and Shipments to Magento — each maps to any object or custom field on the other side.
Companies Organization records map to accounts in ERPs and invoicing tools. Carts / quotes Active and guest carts (quotes) with items and totals; read for abandoned-cart analysis (not available on the Cloud Service subset). Companies is specific to Kommo and Carts / quotes to Magento — each maps to any object or custom field on the other side.

How changes propagate between Kommo and Magento

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 Magento 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 written to Magento through its API, with automatic retries and rate-limit backoff.

Magento Kommo Sub-second propagation

DetectionMagento notifies Stacksync of record changes through webhook events. Polling with searchCriteria filters on updated_at (catalog, sales, and customer entities carry created_at/updated_at).

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.
  • Magento: No fixed request-per-minute cap on PaaS/on-prem; responses page via searchCriteria pageSize/currentPage under a default maximum page size of 300 (Web API Input Limits), with /async/bulk endpoints for large writes.
What ships with Kommo ⇄ Magento

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Kommo or Magento 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 Magento record.

Observability

Monitoring

Track your Kommo ⇄ Magento 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 Magento.

How the Kommo and Magento 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

Magento

Integration surface
REST and GraphQL Web APIs (SOAP also available)
Authentication
Token-based OAuth: an integration's access token (consumer key/secret + access token/secret) or a Bearer admin token (default 4-hour expiry); Adobe Commerce as a Cloud Service authenticates via Adobe IMS (OAuth 2)
Change detection
Polling with searchCriteria filters on updated_at (catalog, sales, and customer entities carry created_at/updated_at); optional near-real-time via the Adobe Commerce Webhooks / Adobe I/O Events modules (order/created, product/updated, customer/created)
Capabilities
read · write · webhooks
Rate limits
No fixed request-per-minute cap on PaaS/on-prem; responses page via searchCriteria pageSize/currentPage under a default maximum page size of 300 (Web API Input Limits), with /async/bulk endpoints for large writes.
How it works

How to connect Kommo to Magento — 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 Magento 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
    Magento connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Kommo and Magento 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 ⇄ Magento
    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 Magento
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Kommo and Magento 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 476 integrations available for Kommo and Magento.

Popular · 8 of 476
All Kommo integrations All Magento 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