Two-way sync
Changes in Intercom or Kustomer instantly reflect in both systems. No stale data, no manual imports.
Keep Intercom and Kustomer 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 Companies, Conversations, Tickets, Data Events in Intercom with Custom Objects (Klasses), Users, Teams, Tags in Kustomer 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.
Keep both CRMs accurate while the merged team decides on a target system, instead of freezing one and losing months of updates.
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.
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 | Kustomer objects | How this pairing syncs | |
|---|---|---|---|
| Companies Company records group contacts and carry plan and account attributes used in segmentation. | Companies Organization records group customers and map to CRM accounts. | 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. | |
| Conversations Support and sales threads sync outward for analytics and CRM context. | Conversations Support threads across channels sync outward for analytics and CRM context. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. | Tags Labels on conversations and customers sync for categorization and analytics. | 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. | |
| Tickets Structured ticket records track issues alongside conversational threads. | Customers The central record whose timeline aggregates every interaction; external attributes sync onto it. | Tickets is specific to Intercom and Customers to Kustomer — each maps to any object or custom field on the other side. | |
| Data Events Behavioral events pushed in from product databases trigger messages and flows. | Messages Individual messages within conversations support full-thread replication. | Data Events is specific to Intercom and Messages to Kustomer — 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. | Custom Objects (Klasses) Structured external records such as orders and subscriptions synced in to appear on the customer timeline. | Custom Data Attributes is specific to Intercom and Custom Objects (Klasses) to Kustomer — 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 Kustomer through its API, with automatic retries and rate-limit backoff.
DetectionKustomer notifies Stacksync of record changes through webhook events. Outbound webhooks on record 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–Kustomer connection.
Changes in Intercom or Kustomer instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Intercom or Kustomer 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 Kustomer record.
Track your Intercom ⇄ Kustomer sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Intercom and Kustomer.
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 Kustomer 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 Kustomer 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 Kustomer: authenticate both systems, choose the objects to sync (such as Intercom's Companies and Conversations), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Intercom and Kustomer connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Intercom–Kustomer integration in-house.
Yes — Stacksync ships production-grade connectors for both Intercom and Kustomer. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Intercom: Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill. On Kustomer: Outbound webhooks on record events, plus polling for backfill. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Intercom side: Companies, Conversations, Tickets, Data Events, plus custom fields where Intercom exposes them. On the Kustomer side: Custom Objects (Klasses), Users, Teams, Tags. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
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 425 integrations available for Intercom and Kustomer.