Real-time
Two-way sync
Changes in Cin7 or Salesforce instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ CRM
Cin7 to Salesforce integration — real-time, two-way sync
Keep Cin7 and Salesforce in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Cin7 and Salesforce
Close the gap between front office and back office: Salesforce and Cin7 share customers and status in real time, in both directions.
Salesforce 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 Contacts, Leads, Opportunities, Cases in Salesforce with Branches / locations, Stock adjustments and transfers, Credit notes / returns, Products 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.
Common use cases
- 01 Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.
- 02 Trigger provisioning or billing changes in an operational database when an Opportunity moves to closed-won.
- 03 Write purchase orders created in a planning tool back into Cin7 for receiving.
- 04 Consolidate stock movements from multiple branches into one reporting database.
Common sync patterns
One customer master
Where both systems keep customer or organization records, corrections in either propagate to the other, ending dual maintenance.
Where Cin7 manages people and org data: keep Salesforce aligned
Owners, territories, and org structure informed by Cin7 stay current in Salesforce.
Where Cin7 handles order-to-cash: closed-won flows through
A deal won in Salesforce creates or updates the customer in Cin7 with clean data, so fulfillment and invoicing start without re-entry.
What you can sync between Cin7 and Salesforce
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 | Salesforce objects | How this pairing syncs | |
|---|---|---|---|
| Contacts Customers and suppliers, matched to CRM records to keep account data consistent. | Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. | 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. | |
| Stock adjustments and transfers Inventory movements read for audit and reconciliation reporting. | Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. | Stock adjustments and transfers is specific to Cin7 and Accounts to Salesforce — each maps to any object or custom field on the other side. | |
| Credit notes / returns Return documents synced so finance and support see the same refund state. | Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. | Credit notes / returns is specific to Cin7 and Leads to Salesforce — each maps to any object or custom field on the other side. | |
| Products SKU records with options and pricing, synced with storefront and marketplace catalogs. | Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. | Products is specific to Cin7 and Opportunities to Salesforce — each maps to any object or custom field on the other side. | |
| Inventory levels Stock on hand by branch or location, published outward for availability. | Cases Support records; synced with help desk tools or internal databases for escalation workflows. | Inventory levels is specific to Cin7 and Cases to Salesforce — each maps to any object or custom field on the other side. | |
| Sales orders Orders captured from all channels; the main object for fulfillment and revenue syncs. | Campaigns Marketing membership data; read out for attribution analysis in the warehouse. | Sales orders is specific to Cin7 and Campaigns to Salesforce — each maps to any object or custom field on the other side. |
How changes propagate between Cin7 and Salesforce
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.
Cin7 Salesforce Sub-second propagation
DetectionCin7 notifies Stacksync of record changes through webhook events. Polling on modified-date filters.
DeliveryEach detected change is written to Salesforce through its API, with automatic retries and rate-limit backoff.
Salesforce Cin7 Sub-second propagation
DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).
DeliveryEach detected change is written to Cin7 through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Cin7: Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core.
- Salesforce: Daily API request allocations vary by edition and license count.
What ships with Cin7 ⇄ Salesforce
Connect Cin7 and Salesforce for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Cin7–Salesforce connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Cin7 or Salesforce data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Cin7 or Salesforce record.
Observability
Monitoring
Track your Cin7 ⇄ Salesforce sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Cin7 and Salesforce.
How the Cin7 and Salesforce connectors work
Cin7
- Integration surface
- 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)
- Change detection
- Polling on modified-date filters; webhook support exists on some editions for order and stock events
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core
Salesforce
- Integration surface
- REST, SOAP, and Bulk APIs
- Authentication
- OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
- Change detection
- Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
- Capabilities
- read · write · CDC
- Rate limits
- Daily API request allocations vary by edition and license count.
How it works
How to connect Cin7 to Salesforce — three steps, no code
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.
- 01
Connect your apps
Authenticate Cin7 and Salesforce with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Cin7
connected
Salesforce
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Cin7 and Salesforce 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.
objects · Cin7 ⇄ SalesforceCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Cin7 SalesforceCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Cin7 and Salesforce integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Cin7 and Salesforce: authenticate both systems, choose the objects to sync (such as Cin7's Contacts and Stock adjustments and transfers), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Cin7 and Salesforce: One customer master; Where Cin7 manages people and org data: keep Salesforce aligned; Where Cin7 handles order-to-cash: closed-won flows through. Where both systems keep customer or organization records, corrections in either propagate to the other, ending dual maintenance.
-
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). Salesforce: REST, SOAP, and Bulk APIs. Authentication: OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode. Stacksync manages authentication, retries, and rate limits on both sides.
-
Salesforce: Non-writable objects, non-triggerable objects (trigger mode), and tables without a last_modified_data column (polling mode) cannot be synced yet. Cin7: Inventory is modeled per branch/location, so availability syncs choose between per-location and aggregated quantities. Stacksync's field mapping accounts for these differences between Cin7 and Salesforce without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Cin7 and Salesforce records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Cin7 and Salesforce connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Cin7–Salesforce integration in-house.
SECURITY
Security teams trust Stacksync
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.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 531 integrations available for Cin7 and Salesforce.
Popular · 7 of 531
-
Cin7 ⇄ Infor CRM -
Cin7 ⇄ Insightly -
Cin7 ⇄ Intercom -
Cin7 ⇄ Kommo -
.png)
Salesforce ⇄ Deposco -
Salesforce ⇄ Epicor ERP -
Salesforce ⇄ Extensiv (3PL Central)
No integrations match .
