Two-way sync
Changes in Acumatica or Azure Active Directory instantly reflect in both systems. No stale data, no manual imports.
Keep Acumatica and Azure Active Directory 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. Acumatica holds the authoritative record of who works at the company, and often their department, title, manager, and cost center. Azure 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 Azure Active Directory is a real security exposure.
Stacksync syncs Payments, Journal Transactions, Projects, Opportunities and Cases in Acumatica with Service principals, Directory roles, Devices, Users in Azure 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 name, email, title, manager, or department corrected in either system updates the other, so directory entries and employee records don't drift apart.
When someone changes team or department, their group or organizational-unit membership updates to match, keeping access tied to their current role.
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.
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.
| Acumatica objects | Azure Active Directory objects | How this pairing syncs | |
|---|---|---|---|
| Stock Items Inventory master data with quantities shared with external sales channels. | Devices /devices registered or joined to the tenant; typically read-only into asset and security databases. | Stock Items is specific to Acumatica and Devices to Azure Active Directory — each maps to any object or custom field on the other side. | |
| Shipments Fulfillment documents read to update tracking in storefronts and CRMs. | Users /users in Microsoft Graph; synced two-way — profile attributes, accountEnabled, and assignedLicenses are read out while provisioning writes (create, update, disable, delete) are pushed back. | Shipments is specific to Acumatica and Users to Azure Active Directory — each maps to any object or custom field on the other side. | |
| Payments Customer payment records reconciled against invoices from payment platforms. | Groups /groups covering security and Microsoft 365 groups; created, updated, and deleted through Graph, and read into warehouses for entitlement reporting. | Payments is specific to Acumatica and Groups to Azure Active Directory — each maps to any object or custom field on the other side. | |
| Journal Transactions GL entries replicated into reporting databases. | Group memberships Member and owner relationships on /groups/{id}/members; added and removed via the $ref endpoint and tracked for changes with delta query on $select=members. | Journal Transactions is specific to Acumatica and Group memberships to Azure Active Directory — each maps to any object or custom field on the other side. | |
| Projects Project cost and billing structures synced with delivery tools. | Applications App registrations under /applications; usually read into a database or CMDB for app ownership and credential-expiry tracking. | Projects is specific to Acumatica and Applications to Azure Active Directory — each maps to any object or custom field on the other side. | |
| Opportunities and Cases Built-in CRM records synced with external sales and support tools. | Service principals /servicePrincipals (enterprise apps) plus appRoleAssignments; read for app inventory and access-posture reporting. | Opportunities and Cases is specific to Acumatica and Service principals to Azure Active Directory — 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.
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 Azure Active Directory through its API, with automatic retries and rate-limit backoff.
DetectionAzure Active Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (deltaLink tokens returning only changed users and groups, with @removed deletions) paired with change-notification.
DeliveryEach detected change is written to Acumatica through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Acumatica–Azure Active Directory connection.
Changes in Acumatica or Azure Active Directory instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Acumatica or Azure Active Directory data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Acumatica or Azure Active Directory record.
Track your Acumatica ⇄ Azure Active Directory sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Acumatica and Azure Active Directory.
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 Acumatica and Azure Active Directory 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 Acumatica and Azure Active Directory 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 Acumatica and Azure Active Directory: authenticate both systems, choose the objects to sync (such as Acumatica's Stock Items and Shipments), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Acumatica: Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields. On Azure Active Directory: Microsoft Graph delta query (deltaLink tokens returning only changed users and groups, with @removed deletions) paired with change-notification webhook subscriptions for near-real-time push. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Acumatica side: Payments, Journal Transactions, Projects, Opportunities and Cases, plus custom fields where Acumatica exposes them. On the Azure Active Directory side: Service principals, Directory roles, Devices, Users. 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 Acumatica and Azure Active Directory: 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.
Acumatica: 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. Azure Active Directory: Microsoft Graph REST API (v1.0). Authentication: OAuth 2.0 via the Microsoft identity platform using an Entra ID app registration; app-only (client credentials) or delegated flows, with directory scopes such as User.ReadWrite.All and Group.ReadWrite.All requiring tenant admin consent. Stacksync manages authentication, retries, and rate limits on both sides.
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 514 integrations available for Acumatica and Azure Active Directory.