Skip to content
Database ⇄ Business productivity

Azure Cosmos DB to Servicemax integration — real-time, two-way sync

Keep Azure Cosmos DB 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 Azure Cosmos DB and Servicemax

Mirror Servicemax's data into Azure Cosmos DB so your own code can read and write it like any other table, with changes flowing both ways in seconds.

Engineers integrate with tools like Servicemax through APIs, which means auth, pagination, rate limits, webhooks, and retry logic, all maintained forever and all different for every tool. Meanwhile the data would be trivial to use if it simply lived in Azure Cosmos DB.

Stacksync mirrors Contacts, Cases, Products, Work Orders from Servicemax into Change feed entries, Stored procedures and triggers, Databases, Containers in Azure Cosmos DB and keeps both sides in sync in real time. Your services query the database directly, and inserts or updates your code makes flow back into Servicemax, so the tool and the database never disagree.

Common use cases

  • 01 Consolidate Service Contracts and entitlement data into a warehouse for renewal forecasting and SLA compliance dashboards.
  • 02 Mirror Accounts and Contacts between ServiceMax and the CRM system of record so customer and site data stays consistent.
  • 03 Two-way sync between a Cosmos DB-backed product catalog and a PIM or commerce platform.
  • 04 Consolidate documents from multiple containers into a single reporting store.

Common sync patterns

React to changes as they happen

Updates in Servicemax arrive as row changes in Azure Cosmos DB, so triggers, jobs, and services can respond in near real time.

One integration pattern for the whole stack

Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.

Read Servicemax with a query

Records from Servicemax are ordinary rows in Azure Cosmos DB; join them, index them, and use them in application logic without touching the vendor API.

What you can sync between Azure Cosmos DB 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.

Azure Cosmos DB objects Servicemax objects How this pairing syncs
Containers The unit of partitioning and throughput; each container maps to a synced collection. Contacts Standard Salesforce Contact; people linked to Accounts and service sites; synced with CRM and support person records. Containers is specific to Azure Cosmos DB and Contacts to Servicemax — each maps to any object or custom field on the other side.
Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. Cases Standard Salesforce Case; support records that often precede a Work Order; synced with help desk tools and reporting databases. Items (JSON documents) is specific to Azure Cosmos DB and Cases to Servicemax — each maps to any object or custom field on the other side.
Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. Products Standard Salesforce Product2; catalog of serviceable products and spare parts referenced by Installed Products and Work Details. Partition keys is specific to Azure Cosmos DB and Products to Servicemax — each maps to any object or custom field on the other side.
Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. 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. Change feed entries is specific to Azure Cosmos DB and Work Orders to Servicemax — each maps to any object or custom field on the other side.
Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. 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. Stored procedures and triggers is specific to Azure Cosmos DB and Work Details to Servicemax — each maps to any object or custom field on the other side.
Databases Top-level namespaces that scope containers and throughput provisioning. Installed Products SVMXC__Installed_Product__c; the installed-base asset record driving entitlement and service history; synced with asset and IoT databases. Databases is specific to Azure Cosmos DB and Installed Products to Servicemax — each maps to any object or custom field on the other side.

How changes propagate between Azure Cosmos DB 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.

Azure Cosmos DB Servicemax Sub-second propagation

DetectionChanges in Azure Cosmos DB are captured at the source via change data capture — no polling loop against its API. Built-in change feed exposing inserts and updates in order within each partition key range.

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

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

Rate-limit considerations

  • 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 Azure Cosmos DB ⇄ Servicemax

Connect Azure Cosmos DB and Servicemax for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Cosmos DB–Servicemax connection.

Real-time

Two-way sync

Changes in Azure Cosmos DB or Servicemax instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Azure Cosmos DB 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 Azure Cosmos DB or Servicemax record.

Observability

Monitoring

Track your Azure Cosmos DB ⇄ Servicemax sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure Cosmos DB and Servicemax.

How the Azure Cosmos DB and Servicemax connectors work

Azure Cosmos DB

Integration surface
REST API and SDKs over HTTPS (API for NoSQL, formerly the SQL API); also MongoDB, Cassandra, Gremlin, and Table API surfaces
Authentication
Account keys, resource tokens, or Microsoft Entra ID role-based access
Change detection
Built-in change feed exposing inserts and updates in order within each partition key range
Capabilities
read · write · CDC

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 Azure Cosmos DB 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 Azure Cosmos DB 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
    Azure Cosmos DB connected
    Servicemax connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure Cosmos DB 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 · Azure Cosmos DB ⇄ 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
    Azure Cosmos DB Servicemax
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Azure Cosmos DB 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 443 integrations available for Azure Cosmos DB and Servicemax.

Popular · 7 of 443
All Azure Cosmos DB 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