Skip to content
ERP ⇄ Business productivity

Dynamics 365 F&O to Servicemax integration — real-time, two-way sync

Keep Dynamics 365 F&O 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.

  • 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 Dynamics 365 F&O and Servicemax

Bridge the tools people work in and the system the business runs on: real-time, two-way sync between Servicemax and Dynamics 365 F&O.

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 Cases, Products, Work Orders, Work Details in Servicemax with On-hand Inventory, Customers, Vendors, Released Products in Dynamics 365 F&O 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.

Common use cases

  • 01 Mirror Accounts and Contacts between ServiceMax and the CRM system of record so customer and site data stays consistent.
  • 02 Sync Work Orders (SVMXC__Service_Order__c) and Work Details bi-directionally with Postgres so ops and analytics teams read and write field-service data in plain SQL.
  • 03 Distribute product and price master data from F&O to downstream channels through a synced database.
  • 04 Sync customers, vendors, and released products into an operational database that internal apps read instead of calling OData directly.

Common sync patterns

Master data corrections travel

A customer, supplier, or contact detail corrected in either system updates the other, ending duplicate maintenance.

Where Servicemax faces customers and Dynamics 365 F&O carries account records

Order, invoice, or account status from Dynamics 365 F&O appears alongside the customer in Servicemax, so front-line teams answer from live data.

Where Servicemax collects payments: transactions post through

Payment events sync into Dynamics 365 F&O as they occur, keeping the enterprise records current without manual entry.

What you can sync between Dynamics 365 F&O and Servicemax

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 F&O objects Servicemax objects How this pairing syncs
On-hand Inventory Stock positions; read out to storefronts and internal apps for availability. Products Standard Salesforce Product2; catalog of serviceable products and spare parts referenced by Installed Products and Work Details. On-hand Inventory is specific to Dynamics 365 F&O and Products to Servicemax — each maps to any object or custom field on the other side.
Customers Customer master records; kept aligned with CRM accounts in two-way syncs. 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. Customers is specific to Dynamics 365 F&O and Work Orders to Servicemax — each maps to any object or custom field on the other side.
Vendors Supplier master records; synced with procurement and AP tools. 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. Vendors is specific to Dynamics 365 F&O and Work Details to Servicemax — each maps to any object or custom field on the other side.
Released Products Sellable product master; read out to commerce channels and CRM catalogs. Installed Products SVMXC__Installed_Product__c; the installed-base asset record driving entitlement and service history; synced with asset and IoT databases. Released Products is specific to Dynamics 365 F&O and Installed Products to Servicemax — each maps to any object or custom field on the other side.
Sales Orders Order transactions; written in from storefronts or CRM and tracked through fulfillment. Service Contracts SVMXC__Service_Contract__c; coverage and entitlement agreements; synced to warehouses for renewal, SLA, and warranty reporting. Sales Orders is specific to Dynamics 365 F&O and Service Contracts to Servicemax — each maps to any object or custom field on the other side.
Purchase Orders Procurement transactions; extracted for spend and supply chain reporting. Stock History SVMXC__Stock_History__c; append-only log of inventory transactions (RMA, shipment, parts receipt); read out for parts and inventory analytics. Purchase Orders is specific to Dynamics 365 F&O and Stock History to Servicemax — each maps to any object or custom field on the other side.

How changes propagate between Dynamics 365 F&O and Servicemax

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.

Dynamics 365 F&O Servicemax Sub-second propagation

DetectionDynamics 365 F&O pushes changes as they happen — webhook events backed by change data capture. Change data capture via the Dynamics 365 Change Tracking feature, enabled per entity.

DeliveryEach detected change is written to Servicemax through its API, with automatic retries and rate-limit backoff.

Servicemax Dynamics 365 F&O Sub-second propagation

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 F&O through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Dynamics 365 F&O: OData requests are subject to platform throttling; high-volume loads belong in the Data Management Framework.
  • Servicemax: Governed by the Salesforce org-wide daily API request allocation, shared across all integrations and scaled by edition and license count.
What ships with Dynamics 365 F&O ⇄ Servicemax

Connect Dynamics 365 F&O and Servicemax for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 F&O–Servicemax connection.

Real-time

Two-way sync

Changes in Dynamics 365 F&O or Servicemax instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Dynamics 365 F&O or Servicemax 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 Dynamics 365 F&O or Servicemax record.

Observability

Monitoring

Track your Dynamics 365 F&O ⇄ Servicemax sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Dynamics 365 F&O and Servicemax.

How the Dynamics 365 F&O and Servicemax connectors work

Dynamics 365 F&O

Integration surface
OData REST endpoint over data entities, plus the Data Management Framework for batch
Authentication
OAuth via Microsoft sign-in: provide the D365 F&O environment URL, sign in with Microsoft credentials, and grant the Stacksync app consent (admin consent may be required — "Need admin approval for this app")
Change detection
Change data capture via the Dynamics 365 Change Tracking feature, enabled per entity; falls back to periodic full-sync where change tracking is unavailable
Capabilities
read · write · CDC · webhooks
Rate limits
OData requests are subject to platform throttling; high-volume loads belong in the Data Management Framework.
Dynamics 365 F&O setup guide

Servicemax

Integration surface
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
Change detection
Salesforce mechanisms — Apex triggers or polling on SystemModstamp/LastModifiedDate, with Change Data Capture / Platform Events available per object where enabled
Capabilities
read · write · CDC
Rate limits
Governed by the Salesforce org-wide daily API request allocation, shared across all integrations and scaled by edition and license count
How it works

How to connect Dynamics 365 F&O to Servicemax — 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 Dynamics 365 F&O 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Dynamics 365 F&O connected
    Servicemax connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Dynamics 365 F&O 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Dynamics 365 F&O ⇄ Servicemax
    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
    Dynamics 365 F&O Servicemax
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Dynamics 365 F&O and Servicemax 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
CSA STAR
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 419 integrations available for Dynamics 365 F&O and Servicemax.

Popular · 3 of 419
All Dynamics 365 F&O integrations All Servicemax 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