Two-way sync
Changes in Active Directory or Extensiv (3PL Central) instantly reflect in both systems. No stale data, no manual imports.
Keep Active Directory and Extensiv (3PL Central) in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
An ERP and an identity system describe the same workforce from two angles. Extensiv (3PL Central) 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 Extensiv (3PL Central) and their account still being active in Active Directory is a real security exposure.
Stacksync syncs Customers, Items, Inventory, Orders in Extensiv (3PL Central) with Devices, Directory roles, Service principals & applications, Organizational units 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.
A person added in one system gets a matching account or record in the other automatically, so a new hire can be granted access without anyone re-keying their details.
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.
A name, email, title, manager, or department corrected in either system updates the other, so directory entries and employee records don't drift apart.
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 | Extensiv (3PL Central) objects | How this pairing syncs | |
|---|---|---|---|
| Group memberships Member and owner links between users and groups; membership add/remove changes are surfaced by delta query. | Items SKU masters kept aligned between the merchant's systems and the warehouse. | Group memberships is specific to Active Directory and Items to Extensiv (3PL Central) — 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. | Inventory On-hand and available quantities by warehouse, mirrored out to drive channel availability. | Devices is specific to Active Directory and Inventory to Extensiv (3PL Central) — 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. | Orders Outbound fulfillment orders pushed in from commerce or ERP systems. | Directory roles is specific to Active Directory and Orders to Extensiv (3PL Central) — 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. | Receivers Inbound receiving records (receipts/ASNs) that confirm stock arrival back to purchasing systems. | Service principals & applications is specific to Active Directory and Receivers to Extensiv (3PL Central) — 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. | Shipments Carrier and tracking details synced back once orders ship. | Organizational units is specific to Active Directory and Shipments to Extensiv (3PL Central) — each maps to any object or custom field on the other side. | |
| Organizational contacts Directory contact objects (orgContact); synced for shared address-book and CRM person records. | Warehouses Facility records that partition inventory and order routing. | Organizational contacts is specific to Active Directory and Warehouses to Extensiv (3PL Central) — each maps to any object or custom field on the other side. |
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.
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 Extensiv (3PL Central) through its API, with automatic retries and rate-limit backoff.
DetectionExtensiv (3PL Central) notifies Stacksync of record changes through webhook events. Webhook events for order, receipt, item, and inventory changes, with polling on modified-date filters as a fallback.
DeliveryEach detected change is written to Active Directory through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Extensiv (3PL Central) connection.
Changes in Active Directory or Extensiv (3PL Central) instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Active Directory or Extensiv (3PL Central) data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Active Directory or Extensiv (3PL Central) record.
Track your Active Directory ⇄ Extensiv (3PL Central) sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Active Directory and Extensiv (3PL Central).
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 Active Directory and Extensiv (3PL Central) 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 Active Directory and Extensiv (3PL Central) 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 Active Directory and Extensiv (3PL Central): authenticate both systems, choose the objects to sync (such as Active Directory's Group memberships and Devices), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both Active Directory and Extensiv (3PL Central). The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Active Directory: 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. On Extensiv (3PL Central): Webhook events for order, receipt, item, and inventory changes, with polling on modified-date filters as a fallback. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Extensiv (3PL Central) side: Customers, Items, Inventory, Orders, plus custom fields where Extensiv (3PL Central) exposes them. On the Active Directory side: Devices, Directory roles, Service principals & applications, Organizational units. 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 Active Directory and Extensiv (3PL Central): Create accounts from new records; Disable access at offboarding; Keep profile attributes current. A person added in one system gets a matching account or record in the other automatically, so a new hire can be granted access without anyone re-keying their details.
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 403 integrations available for Active Directory and Extensiv (3PL Central).