Real-time
Two-way sync
Changes in Active Directory or Epicor ERP instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ ERP
Active Directory to Epicor ERP integration — real-time, two-way sync
Keep Active Directory and Epicor ERP 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 Epicor ERP
Keep the employee, group, and account records that Epicor ERP 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. Epicor ERP 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 Epicor ERP and their account still being active in Active Directory is a real security exposure.
Stacksync syncs Shipments, Bills of materials, Customers, Suppliers in Epicor ERP with Users, Groups, Group memberships, Devices 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 Sync shipment confirmations out to commerce platforms and customer portals as jobs complete.
- 02 Sync Epicor customers and AR invoices into a CRM so sales sees order history and credit status without ERP logins.
- 03 Read Users, Groups, and directoryRole assignments into a warehouse for periodic access reviews and SOC 2 audit evidence.
- 04 Keep security-group memberships aligned with application entitlement tables so access reflects the right teams as they change.
Common sync patterns
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.
One roster on a shared key
People are matched across both systems on an identifier you choose, such as work email or employee ID, so there is a single accurate list of who is active.
What you can sync between Active Directory and Epicor ERP
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 | Epicor ERP objects | How this pairing syncs | |
|---|---|---|---|
| Users User accounts in Entra ID and on-prem AD DS; synced two-way to create, update attributes, and enable or disable accounts. | Shipments Fulfillment confirmations synced to customer portals and commerce systems. | Users is specific to Active Directory and Shipments to Epicor ERP — each maps to any object or custom field on the other side. | |
| Groups Security and Microsoft 365 groups; synced two-way including name, type, and owner, with membership tracked separately. | Bills of materials Methods of manufacturing read for costing and planning integrations. | Groups is specific to Active Directory and Bills of materials to Epicor ERP — 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. | Customers Master records synced with CRM accounts so sales and the ERP agree on ownership and credit status. | Group memberships is specific to Active Directory and Customers to Epicor ERP — 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. | Suppliers Vendor masters kept aligned with procurement and AP automation tools. | Devices is specific to Active Directory and Suppliers to Epicor ERP — 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. | Parts Item masters that anchor inventory, BOM, and order line syncs. | Directory roles is specific to Active Directory and Parts to Epicor ERP — 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. | Sales orders Created from won CRM opportunities; status and line changes sync back out. | Service principals & applications is specific to Active Directory and Sales orders to Epicor ERP — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and Epicor ERP
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 Epicor ERP 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 Epicor ERP through its API, with automatic retries and rate-limit backoff.
Epicor ERP Active Directory Interval-based propagation
DetectionStacksync polls Epicor ERP for changes on an incremental schedule, reading only records changed since the previous pass. Polling on change-date fields.
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.
- Epicor ERP: Subject to the platform's API rate limits and per-tenant throttling on Kinetic cloud deployments.
What ships with Active Directory ⇄ Epicor ERP
Connect Active Directory and Epicor ERP for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Epicor ERP connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or Epicor ERP 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 Epicor ERP record.
Observability
Monitoring
Track your Active Directory ⇄ Epicor ERP 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 Epicor ERP.
How the Active Directory and Epicor ERP 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.
Epicor ERP
- Integration surface
- REST API (OData) over Epicor business objects, plus BAQ (Business Activity Query) endpoints
- Authentication
- API key combined with basic or token authentication, depending on version and deployment
- Change detection
- Polling on change-date fields; outbound calls can be wired through BPM directives, but there is no standard webhook subscription surface
- Capabilities
- read · write
- Rate limits
- Subject to the platform's API rate limits and per-tenant throttling on Kinetic cloud deployments
How it works
How to connect Active Directory to Epicor ERP — 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 Epicor ERP 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
Epicor ERP
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and Epicor ERP 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 ⇄ Epicor ERPCustomers 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 Epicor ERPCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and Epicor ERP integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Epicor ERP: authenticate both systems, choose the objects to sync (such as Active Directory's Users and Groups), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Epicor ERP: BAQs (Business Activity Queries) can be exposed as read endpoints, letting integrations query joined ERP data without composing multiple object calls. Active Directory: DirectoryRole, servicePrincipal, and device objects are effectively read-only for sync; Users, Groups, and memberships are the writable surface. Stacksync's field mapping accounts for these differences between Active Directory and Epicor ERP 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 Epicor ERP 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 Epicor ERP connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Active Directory–Epicor ERP integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Active Directory and Epicor ERP. 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 Epicor ERP: Polling on change-date fields; outbound calls can be wired through BPM directives, but there is no standard webhook subscription surface. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 508 integrations available for Active Directory and Epicor ERP.
Popular · 8 of 508
-
Active Directory ⇄ Manhattan Associates WMS -
Active Directory ⇄ Microsoft Dynamics GP - Active Directory ⇄ Microsoft Dynamics NAV
-
Active Directory ⇄ Plex ERP -
Epicor ERP ⇄ Jumpcloud - Epicor ERP ⇄ Azure Active Directory
-
Epicor ERP ⇄ Okta -
Epicor ERP ⇄ Onelogin
No integrations match .
