Two-way sync
Changes in Close or Intercom instantly reflect in both systems. No stale data, no manual imports.
Keep Close and Intercom 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 Users, Smart Views, Leads, Contacts in Close with Articles, Contacts, Companies, Conversations in Intercom 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.
| Close objects | Intercom objects | How this pairing syncs | |
|---|---|---|---|
| Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. | Contacts A single contact model covers both users and leads, distinguished by a role attribute. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Users Sales reps referenced as owners on leads, opportunities, and activities. | Admins & Teams Teammate records map conversation ownership to CRM users. | Users is specific to Close and Admins & Teams to Intercom — each maps to any object or custom field on the other side. | |
| Smart Views Saved lead searches that can scope which records a segment-based sync pulls. | Articles Help center content is accessible via API for knowledge sync and audits. | Smart Views is specific to Close and Articles to Intercom — each maps to any object or custom field on the other side. | |
| Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. | Companies Company records group contacts and carry plan and account attributes used in segmentation. | Leads is specific to Close and Companies to Intercom — each maps to any object or custom field on the other side. | |
| Opportunities Deal records with value, confidence, and status; commonly synced to reporting and billing systems. | Conversations Support and sales threads sync outward for analytics and CRM context. | Opportunities is specific to Close and Conversations to Intercom — each maps to any object or custom field on the other side. | |
| Activities Calls, emails, SMS, notes, and meetings logged against a lead; the source for engagement analytics. | Tickets Structured ticket records track issues alongside conversational threads. | Activities is specific to Close and Tickets to Intercom — 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.
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 Intercom through its API, with automatic retries and rate-limit backoff.
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 Close through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Close–Intercom connection.
Changes in Close or Intercom instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Close or Intercom data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Close or Intercom record.
Track your Close ⇄ Intercom sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Close and Intercom.
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 Close and Intercom 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 Close and Intercom 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 Close and Intercom: authenticate both systems, choose the objects to sync (such as Close's Contacts and Users), 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 Close and Intercom connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Close–Intercom integration in-house.
Yes — Stacksync ships production-grade connectors for both Close and Intercom. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Close: Webhook subscriptions for record events, with polling on date_updated fields for backfills. On Intercom: Webhook topic subscriptions for contact, company, and conversation 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 Close side: Users, Smart Views, Leads, Contacts, plus custom fields where Close exposes them. On the Intercom side: Articles, Contacts, Companies, Conversations. 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 536 integrations available for Close and Intercom.