Two-way sync
Changes in Cin7 or Close instantly reflect in both systems. No stale data, no manual imports.
Keep Cin7 and Close in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Close holds the customer relationship; Cin7 runs the operations and records behind the business. The two overlap wherever the same organizations and transactions matter to both, and when that overlap is bridged by re-keying or overnight batch, each side spends the day working from stale data.
Stacksync syncs Custom Activities, Custom Fields, Users, Smart Views in Close with Purchase orders, Contacts, Branches / locations, Stock adjustments and transfers in Cin7 field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Invoice and payment state from Cin7 shows on the account in Close, so reps see balances before promising the next order.
Where both systems keep customer or organization records, corrections in either propagate to the other, ending dual maintenance.
Owners, territories, and org structure informed by Cin7 stay current in Close.
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.
| Cin7 objects | Close objects | |
|---|---|---|
| Sales orders Orders captured from all channels; the main object for fulfillment and revenue syncs. | Users Sales reps referenced as owners on leads, opportunities, and activities. | |
| Purchase orders Supplier orders synced with procurement and accounting workflows. | Smart Views Saved lead searches that can scope which records a segment-based sync pulls. | |
| Contacts Customers and suppliers, matched to CRM records to keep account data consistent. | Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. | |
| Branches / locations Warehouse entities that scope every stock movement and order allocation. | Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. | |
| Stock adjustments and transfers Inventory movements read for audit and reconciliation reporting. | Opportunities Deal records with value, confidence, and status; commonly synced to reporting and billing systems. | |
| Credit notes / returns Return documents synced so finance and support see the same refund state. | Activities Calls, emails, SMS, notes, and meetings logged against a lead; the source for engagement analytics. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Cin7–Close connection.
Changes in Cin7 or Close instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Cin7 or Close data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Cin7 or Close record.
Track your Cin7 ⇄ Close sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Cin7 and Close.
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 Cin7 and Close 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 Cin7 and Close 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 Cin7 and Close: authenticate both systems, choose the objects to sync (such as Cin7's Sales orders and Purchase orders), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Close side: Custom Activities, Custom Fields, Users, Smart Views, plus custom fields where Close exposes them. On the Cin7 side: Purchase orders, Contacts, Branches / locations, Stock adjustments and transfers. 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 Cin7 and Close: Where Cin7 is the finance system of record: money status on the account; One customer master; Where Cin7 manages people and org data: keep Close aligned. Invoice and payment state from Cin7 shows on the account in Close, so reps see balances before promising the next order.
Cin7: REST API; note that Cin7 Omni and Cin7 Core (formerly DEAR Systems) are separate products with separate APIs. Authentication: API key credentials (paired with a username or account ID, depending on the product). Close: REST API. Authentication: API key (sent via HTTP Basic auth). Stacksync manages authentication, retries, and rate limits on both sides.
Close: Close's data model is lead-centric: the Lead is a company-level record, and contacts, opportunities, and activities all hang off it, unlike CRMs that treat accounts and contacts as separate top-level objects. Cin7: Cin7 is two distinct products under one brand: Cin7 Omni and Cin7 Core (the former DEAR Systems), each with its own API, credentials, and object shapes, so a connector must target the right one. Stacksync's field mapping accounts for these differences between Cin7 and Close without custom code.
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 386 integrations available for Cin7 and Close.