Two-way sync
Changes in Active Directory or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Keep Active Directory and Servicemax in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Active Directory is where a company records who its people are: their accounts, the groups and roles they hold, and the attributes attached to each one. Servicemax is where a slice of those same people do their work, as agents, members, or seats, and every one of them needs a matching account with the right access. When a directory and a productivity tool are maintained by hand, someone added, moved, or offboarded in one becomes a stale entry in the other within the hour.
Stacksync syncs Cases, Products, Work Orders, Work Details in Servicemax with Users, Groups, Group memberships, Devices in Active Directory bi-directionally and in real time. A user created, renamed, moved between groups, or deactivated in either system updates the matching record in the other within seconds, with field-level mapping and conflict resolution in place of CSV uploads and nightly IT batch jobs.
That matters most at the edges of employment. When both systems agree on who has an account, which groups they belong to, and whether they are still active, granting access on day one and revoking it on the last day stops being a manual checklist that trails the directory.
A person's name, email, department, manager, or phone number corrected in either system updates the other, so the productivity tool shows the same details the directory holds of record.
Moving a user between groups or roles in Active Directory updates their team, permission set, or seat in Servicemax, so what someone can do reflects where they sit in the directory.
People matched across both systems on email or an external ID stay linked, so every account and action in Servicemax ties back to the right identity in Active Directory.
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 | Servicemax objects | How this pairing syncs | |
|---|---|---|---|
| Organizational units On-prem AD DS containers (LDAP organizationalUnit) used to scope which users and groups a sync includes. | Work Orders SVMXC__Service_Order__c; the core field-service job record for install, repair, and maintenance; synced two-way with databases and pushed to ERPs at close. | Organizational units is specific to Active Directory and Work Orders to Servicemax — 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. | Work Details SVMXC__Service_Order_Line__c; line items on a Work Order for labor, parts used, and expenses; read out for billing or written back with usage. | Organizational contacts is specific to Active Directory and Work Details to Servicemax — each maps to any object or custom field on the other side. | |
| Users User accounts in Entra ID and on-prem AD DS; synced two-way to create, update attributes, and enable or disable accounts. | Installed Products SVMXC__Installed_Product__c; the installed-base asset record driving entitlement and service history; synced with asset and IoT databases. | Users is specific to Active Directory and Installed Products to Servicemax — 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. | Service Contracts SVMXC__Service_Contract__c; coverage and entitlement agreements; synced to warehouses for renewal, SLA, and warranty reporting. | Groups is specific to Active Directory and Service Contracts to Servicemax — 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. | Stock History SVMXC__Stock_History__c; append-only log of inventory transactions (RMA, shipment, parts receipt); read out for parts and inventory analytics. | Group memberships is specific to Active Directory and Stock History to Servicemax — 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. | Accounts Standard Salesforce Account; customer and site company records; synced two-way with CRM and database customer tables. | Devices is specific to Active Directory and Accounts to Servicemax — 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 Servicemax through its API, with automatic retries and rate-limit backoff.
DetectionChanges in Servicemax are captured at the source via change data capture — no polling loop against its API. Salesforce mechanisms — Apex triggers or polling on SystemModstamp/LastModifiedDate, with Change Data Capture / Platform Events available per object.
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–Servicemax connection.
Changes in Active Directory or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Active Directory or Servicemax 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 Servicemax record.
Track your Active Directory ⇄ Servicemax sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Active Directory and Servicemax.
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 Servicemax 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 Servicemax 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 Servicemax: authenticate both systems, choose the objects to sync (such as Active Directory's Organizational units and Organizational contacts), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Servicemax side: Cases, Products, Work Orders, Work Details, plus custom fields where Servicemax exposes them. On the Active Directory side: Users, Groups, Group memberships, Devices. 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 Servicemax: Keep profile attributes current; Mirror group and role membership; One record per person. A person's name, email, department, manager, or phone number corrected in either system updates the other, so the productivity tool shows the same details the directory holds of record.
Active Directory: 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. Servicemax: Salesforce REST, SOAP, and Bulk APIs (ServiceMax is a managed package on the Salesforce platform). Authentication: Salesforce OAuth login via a user with API access; the connecting profile needs object and field permissions on ServiceMax's SVMXC__ objects. Stacksync manages authentication, retries, and rate limits on both sides.
Servicemax: Syncs consume the Salesforce org-wide daily API allocation shared by every integration; it varies by edition and license count. Active Directory: Microsoft Graph delta tokens for directory objects expire after about seven days; a sync paused longer must reinitialize with a full read. Stacksync's field mapping accounts for these differences between Active Directory and Servicemax without custom code.
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 509 integrations available for Active Directory and Servicemax.