Real-time
Two-way sync
Changes in Active Directory or Acumatica instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ ERP
Active Directory to Acumatica integration — real-time, two-way sync
Keep Active Directory and Acumatica 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 Acumatica
Keep the employee, group, and account records that Acumatica 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. Acumatica 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 Acumatica and their account still being active in Active Directory is a real security exposure.
Stacksync syncs Journal Transactions, Projects, Opportunities and Cases, Customers in Acumatica 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.
Common use cases
- 01 Mirror stock items and quantities to external channels so availability stays accurate across systems.
- 02 Replicate journal transactions and financial data into a SQL database for reporting and consolidation.
- 03 Keep security-group memberships aligned with application entitlement tables so access reflects the right teams as they change.
- 04 Read Devices and service principals into a database for identity, asset, and license inventory across the tenant.
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 Acumatica
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 | Acumatica objects | How this pairing syncs | |
|---|---|---|---|
| Group memberships Member and owner links between users and groups; membership add/remove changes are surfaced by delta query. | Journal Transactions GL entries replicated into reporting databases. | Group memberships is specific to Active Directory and Journal Transactions to Acumatica — 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. | Projects Project cost and billing structures synced with delivery tools. | Devices is specific to Active Directory and Projects to Acumatica — 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. | Opportunities and Cases Built-in CRM records synced with external sales and support tools. | Directory roles is specific to Active Directory and Opportunities and Cases to Acumatica — 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. | Customers AR master data synced with CRMs and billing tools. | Service principals & applications is specific to Active Directory and Customers to Acumatica — 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. | Vendors Supplier records aligned with procurement and AP automation. | Organizational units is specific to Active Directory and Vendors to Acumatica — 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. | Sales Orders Order documents created from e-commerce and CRM systems, read back for fulfillment status. | Organizational contacts is specific to Active Directory and Sales Orders to Acumatica — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and Acumatica
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 Acumatica 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 Acumatica through its API, with automatic retries and rate-limit backoff.
Acumatica Active Directory Sub-second propagation
DetectionAcumatica notifies Stacksync of record changes through webhook events. Push notifications configurable on data changes, plus polling on LastModifiedDateTime 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.
What ships with Active Directory ⇄ Acumatica
Connect Active Directory and Acumatica for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Acumatica connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or Acumatica 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 Acumatica record.
Observability
Monitoring
Track your Active Directory ⇄ Acumatica 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 Acumatica.
How the Active Directory and Acumatica 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.
Acumatica
- Integration surface
- Contract-based REST API (JSON over versioned endpoints), plus SOAP web services and OData access to Generic Inquiries
- Authentication
- OAuth 2.0 or cookie-based session login with Acumatica credentials
- Change detection
- Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields
- Capabilities
- read · write · webhooks
How it works
How to connect Active Directory to Acumatica — 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 Acumatica 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
Acumatica
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and Acumatica 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 ⇄ AcumaticaCustomers 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 AcumaticaCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and Acumatica integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Acumatica: 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 Acumatica. 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 Acumatica: Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Acumatica side: Journal Transactions, Projects, Opportunities and Cases, Customers, plus custom fields where Acumatica 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 Acumatica: Keep profile attributes current; Align group and department membership; One roster on a shared key. A name, email, title, manager, or department corrected in either system updates the other, so directory entries and employee records don't drift apart.
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 514 integrations available for Active Directory and Acumatica.
Popular · 5 of 514
-
Active Directory ⇄ Linnworks - Acumatica ⇄ Azure Active Directory
-
Acumatica ⇄ Okta -
Acumatica ⇄ Onelogin -
Acumatica ⇄ Auth0
No integrations match .
