Two-way sync
Changes in Dynamics 365 Business Central or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Keep Dynamics 365 Business Central 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.
The ERP holds the records the business is run on, and it is rarely where day-to-day work happens. Servicemax is closer to the work, and the two often need the same facts about the same people, organizations, and transactions. Bridging them by hand, or by nightly file transfer, leaves each side out of date for hours at a time.
Stacksync syncs Installed Products, Service Contracts, Stock History, Accounts in Servicemax with Payments, Customers, Vendors, Items in Dynamics 365 Business Central bi-directionally and in real time, with field-level mapping and rules for which system wins on conflict. Changes made where the work happens reach the system of record within seconds, and the reverse.
Payment events sync into Dynamics 365 Business Central as they occur, keeping the enterprise records current without manual entry.
Worker and organization data from Dynamics 365 Business Central stays current in Servicemax, so the tools people use daily reflect the org as it actually is.
A customer, supplier, or contact detail corrected in either system updates the other, ending duplicate maintenance.
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.
| Dynamics 365 Business Central objects | Servicemax objects | How this pairing syncs | |
|---|---|---|---|
| Sales Invoices Billing documents synced to CRMs and payment platforms. | Products Standard Salesforce Product2; catalog of serviceable products and spare parts referenced by Installed Products and Work Details. | Sales Invoices is specific to Dynamics 365 Business Central and Products to Servicemax — each maps to any object or custom field on the other side. | |
| Purchase Orders Procurement documents exchanged with supplier-facing systems. | 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. | Purchase Orders is specific to Dynamics 365 Business Central and Work Orders to Servicemax — each maps to any object or custom field on the other side. | |
| General Ledger Entries Posted financial transactions read for reporting; posted entries are immutable. | 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. | General Ledger Entries is specific to Dynamics 365 Business Central and Work Details to Servicemax — each maps to any object or custom field on the other side. | |
| Journals Staging records for financial postings created by integrations before posting. | Installed Products SVMXC__Installed_Product__c; the installed-base asset record driving entitlement and service history; synced with asset and IoT databases. | Journals is specific to Dynamics 365 Business Central and Installed Products to Servicemax — each maps to any object or custom field on the other side. | |
| Dimensions Analytical tags (department, project) that syncs preserve for reporting integrity. | Service Contracts SVMXC__Service_Contract__c; coverage and entitlement agreements; synced to warehouses for renewal, SLA, and warranty reporting. | Dimensions is specific to Dynamics 365 Business Central and Service Contracts to Servicemax — each maps to any object or custom field on the other side. | |
| Payments Customer and vendor payment records reconciled against invoices. | Stock History SVMXC__Stock_History__c; append-only log of inventory transactions (RMA, shipment, parts receipt); read out for parts and inventory analytics. | Payments is specific to Dynamics 365 Business Central and Stock History 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.
DetectionDynamics 365 Business Central notifies Stacksync of record changes through webhook events. API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime.
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 Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 Business Central–Servicemax connection.
Changes in Dynamics 365 Business Central or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Dynamics 365 Business Central 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 Dynamics 365 Business Central or Servicemax record.
Track your Dynamics 365 Business Central ⇄ Servicemax sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Dynamics 365 Business Central 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 Dynamics 365 Business Central 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 Dynamics 365 Business Central 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 Dynamics 365 Business Central and Servicemax: authenticate both systems, choose the objects to sync (such as Dynamics 365 Business Central's Sales Invoices and Purchase Orders), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Dynamics 365 Business Central: API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime. On Servicemax: Salesforce mechanisms — Apex triggers or polling on SystemModstamp/LastModifiedDate, with Change Data Capture / Platform Events available per object where enabled. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Servicemax side: Installed Products, Service Contracts, Stock History, Accounts, plus custom fields where Servicemax exposes them. On the Dynamics 365 Business Central side: Payments, Customers, Vendors, Items. 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 Dynamics 365 Business Central and Servicemax: Where Servicemax collects payments: transactions post through; Where Dynamics 365 Business Central is the HR or people system of record; Master data corrections travel. Payment events sync into Dynamics 365 Business Central as they occur, keeping the enterprise records current without manual entry.
Dynamics 365 Business Central: REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL. Authentication: OAuth 2.0 via Microsoft Entra ID. 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.
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 Dynamics 365 Business Central and Servicemax.