Skip to content
Security and identity ⇄ ERP

Active Directory to Sage 100 integration — real-time, two-way sync

Keep Active Directory and Sage 100 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 Sage 100

Keep the employee, group, and account records that Sage 100 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. Sage 100 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 Sage 100 and their account still being active in Active Directory is a real security exposure.

Stacksync syncs GL Accounts, Journal Entries, Customers, Vendors in Sage 100 with Groups, Group memberships, Devices, Directory roles 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 Replicate GL and sales history to a warehouse or Postgres database for reporting off the on-premise system.
  • 02 Sync customers, invoices, and payment status into a CRM so sales sees AR standing without opening the ERP.
  • 03 Read Devices and service principals into a database for identity, asset, and license inventory across the tenant.
  • 04 Two-way sync Users and Groups between Microsoft Entra ID and an HRIS or Postgres so joiners, movers, and leavers provision and deprovision automatically.

Common sync patterns

Create accounts from new records

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.

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.

What you can sync between Active Directory and Sage 100

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 Sage 100 objects How this pairing syncs
Group memberships Member and owner links between users and groups; membership add/remove changes are surfaced by delta query. Purchase Orders Procurement documents read for spend and receiving workflows. Group memberships is specific to Active Directory and Purchase Orders to Sage 100 — 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. GL Accounts Chart of accounts read for mapping transactions in finance integrations. Devices is specific to Active Directory and GL Accounts to Sage 100 — 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. Journal Entries Posted GL activity replicated to warehouses for FP&A. Directory roles is specific to Active Directory and Journal Entries to Sage 100 — 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 customer master records synced to CRMs for account and credit visibility. Service principals & applications is specific to Active Directory and Customers to Sage 100 — 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 AP vendor master records synced with procurement and payment tools. Organizational units is specific to Active Directory and Vendors to Sage 100 — 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. Inventory Items Item master with pricing and quantities, synced to e-commerce catalogs. Organizational contacts is specific to Active Directory and Inventory Items to Sage 100 — each maps to any object or custom field on the other side.

How changes propagate between Active Directory and Sage 100

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 Sage 100 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 applied to Sage 100 as a row-level write, with types converted between the two schemas.

Sage 100 Active Directory Interval-based propagation

DetectionStacksync polls Sage 100 for changes on an incremental schedule, reading only records changed since the previous pass. Scheduled polling.

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 ⇄ Sage 100

Connect Active Directory and Sage 100 for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Sage 100 connection.

Real-time

Two-way sync

Changes in Active Directory or Sage 100 instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Active Directory or Sage 100 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 Sage 100 record.

Observability

Monitoring

Track your Active Directory ⇄ Sage 100 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 Sage 100.

How the Active Directory and Sage 100 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.

Sage 100

Integration surface
ODBC (ProvideX driver) for reads; Business Object Interface (BOI) or Sage-provided web services for writes
Authentication
Sage 100 company and user credentials; ODBC DSN credentials for direct reads
Change detection
Scheduled polling; no webhooks or change log on the integration surface
Capabilities
read · write
How it works

How to connect Active Directory to Sage 100 — 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.

  1. 01

    Connect your apps

    Authenticate Active Directory and Sage 100 with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Active Directory connected
    Sage 100 connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Active Directory and Sage 100 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Active Directory ⇄ Sage 100
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Active Directory Sage 100
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Active Directory and Sage 100 integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 505 integrations available for Active Directory and Sage 100.

Popular · 7 of 505
All Active Directory integrations All Sage 100 integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own