Real-time
Two-way sync
Changes in Cin7 or Microsoft 365 instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Business productivity
Cin7 to Microsoft 365 integration — real-time, two-way sync
Keep Cin7 and Microsoft 365 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 Microsoft 365
Bridge the tools people work in and the system the business runs on: real-time, two-way sync between Microsoft 365 and Cin7.
The ERP holds the records the business is run on, and it is rarely where day-to-day work happens. Microsoft 365 is closer to the work, and the two often need the same facts about the same people, organizations, and transactions. Bridging them by hand, or by nightly file transfer, leaves each side out of date for hours at a time.
Stacksync syncs Teams, Planner & To Do Tasks, Users, Groups in Microsoft 365 with Contacts, Branches / locations, Stock adjustments and transfers, Credit notes / returns in Cin7 bi-directionally and in real time, with field-level mapping and rules for which system wins on conflict. Changes made where the work happens reach the system of record within seconds, and the reverse.
Common use cases
- 01 Archive mail and file metadata into a warehouse for compliance and activity analytics.
- 02 Keep CRM contacts and Microsoft 365 contacts aligned in both directions.
- 03 Consolidate stock movements from multiple branches into one reporting database.
- 04 Publish Cin7 inventory levels to storefronts, marketplaces, and a CRM so every channel quotes real availability.
Common sync patterns
Where Cin7 is the HR or people system of record
Worker and organization data from Cin7 stays current in Microsoft 365, so the tools people use daily reflect the org as it actually is.
Master data corrections travel
A customer, supplier, or contact detail corrected in either system updates the other, ending duplicate maintenance.
Where Microsoft 365 faces customers and Cin7 carries account records
Order, invoice, or account status from Cin7 appears alongside the customer in Microsoft 365, so front-line teams answer from live data.
What you can sync between Cin7 and Microsoft 365
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 | Microsoft 365 objects | How this pairing syncs | |
|---|---|---|---|
| Contacts Customers and suppliers, matched to CRM records to keep account data consistent. | Contacts Personal and org contacts kept consistent with CRM contact 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. | |
| Branches / locations Warehouse entities that scope every stock movement and order allocation. | Mail Messages Exchange Online messages read for logging, archiving, or activity capture. | Branches / locations is specific to Cin7 and Mail Messages to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Stock adjustments and transfers Inventory movements read for audit and reconciliation reporting. | Calendar Events Events synced with scheduling tools and CRMs for meeting visibility. | Stock adjustments and transfers is specific to Cin7 and Calendar Events to Microsoft 365 — 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. | OneDrive Files (driveItems) File and folder metadata synced for document workflows and audits. | Credit notes / returns is specific to Cin7 and OneDrive Files (driveItems) to Microsoft 365 — 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. | SharePoint Sites & Lists List items read and written like lightweight database tables. | Products is specific to Cin7 and SharePoint Sites & Lists to Microsoft 365 — 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. | Teams Team and membership data provisioned from upstream systems. | Inventory levels is specific to Cin7 and Teams to Microsoft 365 — each maps to any object or custom field on the other side. |
How changes propagate between Cin7 and Microsoft 365
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 Microsoft 365 Sub-second propagation
DetectionCin7 notifies Stacksync of record changes through webhook events. Polling on modified-date filters.
DeliveryEach detected change is written to Microsoft 365 through its API, with automatic retries and rate-limit backoff.
Microsoft 365 Cin7 Sub-second propagation
DetectionMicrosoft 365 notifies Stacksync of record changes through webhook events. Graph change notifications (webhooks) plus delta queries for incremental sync.
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.
What ships with Cin7 ⇄ Microsoft 365
Connect Cin7 and Microsoft 365 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Cin7–Microsoft 365 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Cin7 or Microsoft 365 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 Microsoft 365 record.
Observability
Monitoring
Track your Cin7 ⇄ Microsoft 365 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 Microsoft 365.
How the Cin7 and Microsoft 365 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
Microsoft 365
- Integration surface
- REST API (Microsoft Graph)
- Authentication
- OAuth 2.0 via Microsoft Entra ID, with delegated or application permissions
- Change detection
- Graph change notifications (webhooks) plus delta queries for incremental sync
- Capabilities
- read · write · webhooks
How it works
How to connect Cin7 to Microsoft 365 — 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 Microsoft 365 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
Microsoft 365
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Cin7 and Microsoft 365 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 ⇄ Microsoft 365Customers 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 Microsoft 365Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Cin7 and Microsoft 365 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Cin7 and Microsoft 365: authenticate both systems, choose the objects to sync (such as Cin7's Contacts and Branches / locations), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Microsoft 365: Where Cin7 is the HR or people system of record; Master data corrections travel; Where Microsoft 365 faces customers and Cin7 carries account records. Worker and organization data from Cin7 stays current in Microsoft 365, so the tools people use daily reflect the org as it actually is.
-
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). Microsoft 365: REST API (Microsoft Graph). Authentication: OAuth 2.0 via Microsoft Entra ID, with delegated or application permissions. Stacksync manages authentication, retries, and rate limits on both sides.
-
Microsoft 365: Delta queries return only resources changed since the last sync token, which keeps incremental syncs cheap on large tenants. Cin7: Order objects carry channel context (POS, B2B, e-commerce), which downstream reporting syncs typically preserve for channel-level margin analysis. Stacksync's field mapping accounts for these differences between Cin7 and Microsoft 365 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 Microsoft 365 records are not retained after a sync operation.
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 451 integrations available for Cin7 and Microsoft 365.
Popular · 5 of 451
No integrations match .
