Real-time
Two-way sync
Changes in Active Directory or Cin7 instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ ERP
Active Directory to Cin7 integration — real-time, two-way sync
Keep Active Directory and Cin7 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 Active Directory and Cin7
Keep the employee, group, and account records that Cin7 and Active Directory share aligned in real time, so a person added, moved, or offboarded in one system shows up correctly in the other within seconds.
An ERP and an identity system describe the same workforce from two angles. Cin7 holds the authoritative record of who works at the company, and often their department, title, manager, and cost center. Active Directory controls the accounts, groups, and access those same people use every day. When the two aren't connected, every hire, transfer, and departure has to be keyed twice, and the window between someone leaving in Cin7 and their account still being active in Active Directory is a real security exposure.
Stacksync syncs Inventory levels, Sales orders, Purchase orders, Contacts in Cin7 with Directory roles, Service principals & applications, Organizational units, Organizational contacts in Active Directory in real time, with field-level mapping and conflict resolution in place of CSV exports and nightly jobs. A new hire, a department change, or a termination propagates within seconds, and where you want changes to flow both ways — the ERP's org data into the directory, account status back into the ERP — the same mapping handles it.
That matters most at offboarding and audit time. When the directory reflects the ERP's current headcount and org structure, disabling access no longer depends on someone remembering to update a second system, and access reviews start from a roster both sides already agree on.
Common use cases
- 01 Write purchase orders created in a planning tool back into Cin7 for receiving.
- 02 Consolidate stock movements from multiple branches into one reporting database.
- 03 Two-way sync Users and Groups between Microsoft Entra ID and an HRIS or Postgres so joiners, movers, and leavers provision and deprovision automatically.
- 04 Read Users, Groups, and directoryRole assignments into a warehouse for periodic access reviews and SOC 2 audit evidence.
Common sync patterns
Disable access at offboarding
When a person is marked terminated or inactive in one system, the matching account is disabled in the other within seconds, closing the gap that leaves ex-employees with live access.
Keep profile attributes current
A name, email, title, manager, or department corrected in either system updates the other, so directory entries and employee records don't drift apart.
Align group and department membership
When someone changes team or department, their group or organizational-unit membership updates to match, keeping access tied to their current role.
What you can sync between Active Directory and Cin7
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.
| Active Directory objects | Cin7 objects | How this pairing syncs | |
|---|---|---|---|
| Groups Security and Microsoft 365 groups; synced two-way including name, type, and owner, with membership tracked separately. | Products SKU records with options and pricing, synced with storefront and marketplace catalogs. | Groups is specific to Active Directory and Products to Cin7 — each maps to any object or custom field on the other side. | |
| Group memberships Member and owner links between users and groups; membership add/remove changes are surfaced by delta query. | Inventory levels Stock on hand by branch or location, published outward for availability. | Group memberships is specific to Active Directory and Inventory levels to Cin7 — each maps to any object or custom field on the other side. | |
| Devices Registered and joined device objects; typically read into a database for inventory and compliance reporting. | Sales orders Orders captured from all channels; the main object for fulfillment and revenue syncs. | Devices is specific to Active Directory and Sales orders to Cin7 — each maps to any object or custom field on the other side. | |
| Directory roles Admin role assignments (directoryRole); read for access reviews and least-privilege governance. | Purchase orders Supplier orders synced with procurement and accounting workflows. | Directory roles is specific to Active Directory and Purchase orders to Cin7 — each maps to any object or custom field on the other side. | |
| Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. | Contacts Customers and suppliers, matched to CRM records to keep account data consistent. | Service principals & applications is specific to Active Directory and Contacts to Cin7 — each maps to any object or custom field on the other side. | |
| Organizational units On-prem AD DS containers (LDAP organizationalUnit) used to scope which users and groups a sync includes. | Branches / locations Warehouse entities that scope every stock movement and order allocation. | Organizational units is specific to Active Directory and Branches / locations to Cin7 — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and Cin7
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.
Active Directory Cin7 Sub-second propagation
DetectionActive Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers.
DeliveryEach detected change is written to Cin7 through its API, with automatic retries and rate-limit backoff.
Cin7 Active Directory Sub-second propagation
DetectionCin7 notifies Stacksync of record changes through webhook events. Polling on modified-date filters.
DeliveryEach detected change is written to Active Directory through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Active Directory: Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
- Cin7: Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core.
What ships with Active Directory ⇄ Cin7
Connect Active Directory and Cin7 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Cin7 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or Cin7 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 Active Directory or Cin7 record.
Observability
Monitoring
Track your Active Directory ⇄ Cin7 sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Active Directory and Cin7.
How the Active Directory and Cin7 connectors work
Active Directory
- Integration surface
- Microsoft Graph REST API (Entra ID / cloud) and LDAP/LDAPS (on-premises AD DS)
- Authentication
- OAuth 2.0 via the Microsoft identity platform — an app registration with application or delegated permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) and admin consent; on-prem AD DS uses a bound service account over LDAPS.
- Change detection
- Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling.
- Capabilities
- read · write · webhooks
- Rate limits
- Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
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
How it works
How to connect Active Directory to Cin7 — 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 Active Directory and Cin7 with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Active Directory
connected
Cin7
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and Cin7 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 · Active Directory ⇄ Cin7Customers 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.
Active Directory Cin7Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and Cin7 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Cin7: authenticate both systems, choose the objects to sync (such as Active Directory's Groups and Group memberships), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Active Directory: Microsoft Graph REST API (Entra ID / cloud) and LDAP/LDAPS (on-premises AD DS). Authentication: OAuth 2.0 via the Microsoft identity platform — an app registration with application or delegated permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) and admin consent; on-prem AD DS uses a bound service account over LDAPS. 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). Stacksync manages authentication, retries, and rate limits on both sides.
-
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. Active Directory: For hybrid users mastered on-premises, some attributes (e.g. userPrincipalName) cannot be changed in Entra ID because the object is sourced from AD DS. Stacksync's field mapping accounts for these differences between Active Directory and Cin7 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 Active Directory and Cin7 records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Active Directory and Cin7 connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Active Directory–Cin7 integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Active Directory and Cin7. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 498 integrations available for Active Directory and Cin7.
Popular · 8 of 498
-
Active Directory ⇄ Dynamics 365 Business Central -
Active Directory ⇄ SAP Business ByDesign -
Active Directory ⇄ SAP Business One -
Active Directory ⇄ Oracle Fusion ERP -
Cin7 ⇄ Jumpcloud - Cin7 ⇄ Azure Active Directory
-
Cin7 ⇄ Okta -
Cin7 ⇄ Onelogin
No integrations match .
