Skip to content
CRM

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

Keep Close 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.

  • 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 Close and Kommo

Run Close and Kommo side by side with the same accounts and contacts in both, whether they serve different teams or one is replacing the other.

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 Users, Smart Views, Leads, Contacts in Close with Notes, Custom Fields, Users, Chats 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.

Common use cases

  • 01 Two-way sync between Close and a billing or ERP system so closed-won opportunities create customers and invoices automatically.
  • 02 Keep Close contacts aligned with a marketing automation platform so outreach lists stay current.
  • 03 Replicate Kommo leads and contacts into a database or warehouse for reporting beyond built-in dashboards
  • 04 Push web form and product signups into Kommo pipelines as they are submitted so messenger-based follow-up starts quickly

Common sync patterns

Post-acquisition consolidation

Keep both CRMs accurate while the merged team decides on a target system, instead of freezing one and losing months of updates.

Migration with a parallel run

When one CRM is replacing the other, run both fully live until cutover, with no snapshot gap and no data freeze.

Divisional or regional split

Where each CRM serves a different team or region, sync just the shared accounts and contacts so handoffs and cross-sell work.

What you can sync between Close and Kommo

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.

Close objects Kommo objects How this pairing syncs
Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. Leads The central pipeline record; external signups and form fills sync in as leads. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. 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.
Tasks Follow-up items assigned to users; synced for workload and SLA reporting. Tasks Follow-up records keep rep activity consistent across systems. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. Custom Fields Per-entity custom fields hold data written from external databases and enrichment. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping.
Activities Calls, emails, SMS, notes, and meetings logged against a lead; the source for engagement analytics. Users Account users map lead ownership to people in other systems. Activities is specific to Close and Users to Kommo — each maps to any object or custom field on the other side.
Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. Chats Messenger conversations from WhatsApp, Instagram, and other channels attach to leads and contacts. Custom Activities is specific to Close and Chats to Kommo — each maps to any object or custom field on the other side.

How changes propagate between Close and Kommo

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.

Close Kommo Sub-second propagation

DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.

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

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

Rate-limit considerations

  • Close: Subject to per-endpoint rate limits communicated in response headers.
  • Kommo: Subject to per-account request rate limits.
What ships with Close ⇄ Kommo

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Close and Kommo connectors work

Close

Integration surface
REST API
Authentication
API key (sent via HTTP Basic auth)
Change detection
Webhook subscriptions for record events, with polling on date_updated fields for backfills
Capabilities
read · write · webhooks
Rate limits
Subject to per-endpoint rate limits communicated in response headers

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
How it works

How to connect Close to Kommo — 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 Close 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.

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

    Choose tables

    Pick the Close 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Close ⇄ Kommo
    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
    Close Kommo
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Close and Kommo 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 541 integrations available for Close and Kommo.

Popular · 8 of 541
All Close integrations All Kommo 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