Two-way sync
Changes in Close or Insightly instantly reflect in both systems. No stale data, no manual imports.
Keep Close and Insightly 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 Leads, Contacts, Opportunities, Activities in Close with Leads, Opportunities, Projects, Tasks in Insightly 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.
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.
Keep both CRMs accurate while the merged team decides on a target system, instead of freezing one and losing months of updates.
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 | Insightly objects | How this pairing syncs | |
|---|---|---|---|
| Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. | Leads Unqualified prospects sync in from forms and enrichment sources before conversion. | 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 marketing and support tools to keep one contact list. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Opportunities Deal records with value, confidence, and status; commonly synced to reporting and billing systems. | Opportunities Pipeline records feed forecasting and warehouse-based reporting. | 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 Activity records keep follow-ups consistent across systems. | 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. | Products Product catalog entries support line-item syncing on opportunities and quotes. | Users is specific to Close and Products to Insightly — 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. | Custom Fields Per-object custom fields carry enrichment and billing data written from external systems. | Smart Views is specific to Close and Custom Fields to Insightly — 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 Insightly through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls Insightly for changes on an incremental schedule, reading only records changed since the previous pass. Polling on record updated-date fields.
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–Insightly connection.
Changes in Close or Insightly instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Close or Insightly 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 Insightly record.
Track your Close ⇄ Insightly sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Close and Insightly.
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 Insightly 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 Insightly 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 Insightly: authenticate both systems, choose the objects to sync (such as Close's Leads and Contacts), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both Close and Insightly. 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 Insightly: Polling on record updated-date fields. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Close side: Leads, Contacts, Opportunities, Activities, plus custom fields where Close exposes them. On the Insightly side: Leads, Opportunities, Projects, Tasks. 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.
Common patterns for Close and Insightly: Divisional or regional split; Where both track pipeline: deal visibility across systems; Post-acquisition consolidation. Where each CRM serves a different team or region, sync just the shared accounts and contacts so handoffs and cross-sell work.
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 539 integrations available for Close and Insightly.