Two-way sync
Changes in Intercom or Kommo instantly reflect in both systems. No stale data, no manual imports.
Keep Intercom and Kommo in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Two CRMs in one company is more common than anyone plans for: an acquisition brings its own system, regions or business units standardize differently, or a migration is under way and both are live. In every case, some of the same companies and people exist in both systems, and every day of manual double entry pushes the copies further apart.
Stacksync syncs Conversations, Tickets, Data Events, Custom Data Attributes in Intercom with Users, Chats, Leads, Contacts in Kommo in real time and in both directions, with field-level mapping and matching on identifiers you choose. Update a record in either CRM and the other reflects it within seconds.
When one CRM is replacing the other, run both fully live until cutover, with no snapshot gap and no data freeze.
Where each CRM serves a different team or region, sync just the shared accounts and contacts so handoffs and cross-sell work.
Deal stage and value on shared accounts stay visible from either CRM.
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.
| Intercom objects | Kommo objects | How this pairing syncs | |
|---|---|---|---|
| Contacts A single contact model covers both users and leads, distinguished by a role attribute. | Contacts Person records sync with other CRMs and databases for a shared contact file. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Companies Company records group contacts and carry plan and account attributes used in segmentation. | Companies Organization records map to accounts in ERPs and invoicing tools. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Data Events Behavioral events pushed in from product databases trigger messages and flows. | Chats Messenger conversations from WhatsApp, Instagram, and other channels attach to leads and contacts. | Data Events is specific to Intercom and Chats to Kommo — each maps to any object or custom field on the other side. | |
| Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. | Leads The central pipeline record; external signups and form fills sync in as leads. | Custom Data Attributes is specific to Intercom and Leads to Kommo — each maps to any object or custom field on the other side. | |
| Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. | Pipelines & Statuses Stage definitions structure lead progress and drive stage-change syncs to reporting tools. | Tags is specific to Intercom and Pipelines & Statuses to Kommo — each maps to any object or custom field on the other side. | |
| Segments Saved audience definitions are readable for targeting parity across tools. | Tasks Follow-up records keep rep activity consistent across systems. | Segments is specific to Intercom and Tasks to Kommo — each maps to any object or custom field on the other side. |
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.
DetectionIntercom notifies Stacksync of record changes through webhook events. Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill.
DeliveryEach detected change is written to Kommo through its API, with automatic retries and rate-limit backoff.
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 Intercom through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Intercom–Kommo connection.
Changes in Intercom or Kommo instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Intercom or Kommo data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Intercom or Kommo record.
Track your Intercom ⇄ Kommo sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Intercom and Kommo.
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.
Authenticate Intercom and Kommo with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Intercom and Kommo 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Intercom and Kommo: authenticate both systems, choose the objects to sync (such as Intercom's Contacts and Companies), map fields visually, and changes propagate both ways in milliseconds — no code required.
Intercom: REST API. Authentication: OAuth 2.0 for public apps or a workspace access token. Kommo: REST API. Authentication: OAuth 2.0 with refresh tokens. Stacksync manages authentication, retries, and rate limits on both sides.
Intercom: Intercom's Contacts API unifies users and leads into one object with a role attribute, replacing the older separate users and leads endpoints. Kommo: Kommo is the former amoCRM, and its data model centers on leads moving through configurable pipelines and statuses, with contacts and companies linked to each lead. Stacksync's field mapping accounts for these differences between Intercom and Kommo without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Intercom and Kommo records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Intercom and Kommo connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Intercom–Kommo integration in-house.
Yes — Stacksync ships production-grade connectors for both Intercom and Kommo. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 525 integrations available for Intercom and Kommo.