Two-way sync
Changes in Azure Synapse Analytics or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Keep Azure Synapse Analytics 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.
Whatever Servicemax is used for, it accumulates data the rest of the company wants to analyze, and that data usually sits behind an API rather than in the warehouse. Building and babysitting an extraction pipeline is the tax most teams pay for it.
Stacksync syncs Stock History, Accounts, Contacts, Cases from Servicemax into tables in Azure Synapse Analytics continuously, handling schema, rate limits, and retries. Because the sync is bi-directional, results computed in Azure Synapse Analytics can also be written back into fields in Servicemax where the tool can use them.
A continuously synced copy in Azure Synapse Analytics preserves a queryable record even as data ages out of Servicemax or gets changed inside it.
Records and events from Servicemax land in Azure Synapse Analytics as queryable tables, current within seconds and ready to join with the rest of the warehouse.
Combine Servicemax's data with data from every other synced system to answer questions no single tool can.
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 Synapse Analytics objects | Servicemax objects | How this pairing syncs | |
|---|---|---|---|
| SQL pools Dedicated or serverless compute contexts that determine how and where queries run. | Accounts Standard Salesforce Account; customer and site company records; synced two-way with CRM and database customer tables. | SQL pools is specific to Azure Synapse Analytics and Accounts to Servicemax — each maps to any object or custom field on the other side. | |
| Tables (dedicated SQL pool) Distributed warehouse tables that serve as sync destinations for analytics workloads. | Contacts Standard Salesforce Contact; people linked to Accounts and service sites; synced with CRM and support person records. | Tables (dedicated SQL pool) is specific to Azure Synapse Analytics and Contacts to Servicemax — each maps to any object or custom field on the other side. | |
| External tables Tables over files in the data lake, queried through serverless SQL and often read-only in syncs. | Cases Standard Salesforce Case; support records that often precede a Work Order; synced with help desk tools and reporting databases. | External tables is specific to Azure Synapse Analytics and Cases to Servicemax — each maps to any object or custom field on the other side. | |
| Views Curated projections used when downstream tools should not read base tables directly. | Products Standard Salesforce Product2; catalog of serviceable products and spare parts referenced by Installed Products and Work Details. | Views is specific to Azure Synapse Analytics and Products to Servicemax — each maps to any object or custom field on the other side. | |
| Schemas Namespaces that separate staging, integration, and presentation layers. | 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. | Schemas is specific to Azure Synapse Analytics and Work Orders to Servicemax — each maps to any object or custom field on the other side. | |
| Materialized views Precomputed aggregates that speed reads of frequently synced result sets. | 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. | Materialized views is specific to Azure Synapse Analytics and Work Details 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.
DetectionStacksync polls Azure Synapse Analytics for changes on an incremental schedule, reading only records changed since the previous pass. Polling on watermark columns.
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 applied to Azure Synapse Analytics as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Synapse Analytics–Servicemax connection.
Changes in Azure Synapse Analytics or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Azure Synapse Analytics 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 Azure Synapse Analytics or Servicemax record.
Track your Azure Synapse Analytics ⇄ Servicemax sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Azure Synapse Analytics 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 Azure Synapse Analytics 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 Azure Synapse Analytics 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 Azure Synapse Analytics and Servicemax: authenticate both systems, choose the objects to sync (such as Azure Synapse Analytics's SQL pools and Tables (dedicated SQL pool)), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both Azure Synapse Analytics and Servicemax. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Azure Synapse Analytics: Polling on watermark columns; Synapse SQL pools do not expose log-based CDC for downstream consumers. 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: Stock History, Accounts, Contacts, Cases, plus custom fields where Servicemax exposes them. On the Azure Synapse Analytics side: Materialized views, SQL pools, Tables (dedicated SQL pool), External tables. 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 Azure Synapse Analytics and Servicemax: History that outlives the tool; Analytics on Servicemax's data; Cross-tool reporting. A continuously synced copy in Azure Synapse Analytics preserves a queryable record even as data ages out of Servicemax or gets changed inside it.
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 546 integrations available for Azure Synapse Analytics and Servicemax.