Two-way sync
Changes in Cin7 or MySQL instantly reflect in both systems. No stale data, no manual imports.
Keep Cin7 and MySQL in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
ERP data sits behind interfaces built for the ERP's own modules, not for your internal systems. Teams that need those records, for reporting services, internal tools, or automations, end up writing integration code against a strict API and maintaining it through every upgrade.
Stacksync mirrors Purchase orders, Contacts, Branches / locations, Stock adjustments and transfers from Cin7 into MySQL and keeps both sides consistent in real time. Whatever Cin7 is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in MySQL sync back into Cin7 with its validations respected.
Worker and org records stay current in MySQL for provisioning, access, and reporting systems that read from the database.
Choose exactly which tables and fields may flow from MySQL back into Cin7, keeping the ERP authoritative.
Records from Cin7 live in MySQL as ordinary tables or collections, joinable with the rest of your data.
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 | MySQL objects | |
|---|---|---|
| Products SKU records with options and pricing, synced with storefront and marketplace catalogs. | Primary and Unique Keys Match keys for idempotent upserts and conflict handling. | |
| Inventory levels Stock on hand by branch or location, published outward for availability. | JSON Columns Validated semi-structured payloads for nested SaaS data. | |
| Sales orders Orders captured from all channels; the main object for fulfillment and revenue syncs. | Stored Procedures Server-side logic that can post-process synced rows. | |
| Purchase orders Supplier orders synced with procurement and accounting workflows. | Triggers An alternative change-capture mechanism when binlog access is unavailable. | |
| Contacts Customers and suppliers, matched to CRM records to keep account data consistent. | Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. | |
| Branches / locations Warehouse entities that scope every stock movement and order allocation. | Tables The primary sync target; rows map to records in connected systems. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Cin7–MySQL connection.
Changes in Cin7 or MySQL instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Cin7 or MySQL 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 MySQL record.
Track your Cin7 ⇄ MySQL sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Cin7 and MySQL.
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 MySQL 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 MySQL 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 MySQL: authenticate both systems, choose the objects to sync (such as Cin7's Products and Inventory levels), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Cin7: Polling on modified-date filters; webhook support exists on some editions for order and stock events. On MySQL: Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when binary logging is enabled). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the MySQL side: Tables, Views, Columns, Primary and Unique Keys, plus custom fields where MySQL 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 MySQL: Where Cin7 is the HR system of record: people data for internal systems; Controlled write-back; Read ERP records with a query. Worker and org records stay current in MySQL for provisioning, access, and reporting systems that read from the database.
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). MySQL: SQL wire protocol (MySQL client/server protocol). Authentication: Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host). Stacksync manages authentication, retries, and rate limits on both sides.
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 MySQL.