Two-way sync
Changes in Exasol or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Keep Exasol 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 Cases, Products, Work Orders, Work Details from Servicemax into tables in Exasol continuously, handling schema, rate limits, and retries. Because the sync is bi-directional, results computed in Exasol can also be written back into fields in Servicemax where the tool can use them.
A continuously synced copy in Exasol preserves a queryable record even as data ages out of Servicemax or gets changed inside it.
Records and events from Servicemax land in Exasol 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.
| Exasol objects | Servicemax objects | How this pairing syncs | |
|---|---|---|---|
| Users and roles Grant read/write access for the dedicated integration account. | Products Standard Salesforce Product2; catalog of serviceable products and spare parts referenced by Installed Products and Work Details. | Users and roles is specific to Exasol and Products to Servicemax — each maps to any object or custom field on the other side. | |
| Schemas Namespaces that group the tables a sync reads from or writes into. | 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 Exasol and Work Orders to Servicemax — each maps to any object or custom field on the other side. | |
| Tables Primary sync target; columnar relational tables written with standard SQL. | 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. | Tables is specific to Exasol and Work Details to Servicemax — each maps to any object or custom field on the other side. | |
| Views Read-only query surfaces often used as curated sources for reverse ETL. | Installed Products SVMXC__Installed_Product__c; the installed-base asset record driving entitlement and service history; synced with asset and IoT databases. | Views is specific to Exasol and Installed Products to Servicemax — each maps to any object or custom field on the other side. | |
| Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. | Service Contracts SVMXC__Service_Contract__c; coverage and entitlement agreements; synced to warehouses for renewal, SLA, and warranty reporting. | Virtual schemas is specific to Exasol and Service Contracts to Servicemax — each maps to any object or custom field on the other side. | |
| UDF scripts In-database functions that can transform synced data after load. | Stock History SVMXC__Stock_History__c; append-only log of inventory transactions (RMA, shipment, parts receipt); read out for parts and inventory analytics. | UDF scripts is specific to Exasol 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.
DetectionStacksync polls Exasol for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key 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 Exasol as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Exasol–Servicemax connection.
Changes in Exasol or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Exasol 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 Exasol or Servicemax record.
Track your Exasol ⇄ Servicemax sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Exasol 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 Exasol 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 Exasol 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 Exasol and Servicemax: authenticate both systems, choose the objects to sync (such as Exasol's Users and roles and Schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Exasol and Servicemax: History that outlives the tool; Analytics on Servicemax's data; Cross-tool reporting. A continuously synced copy in Exasol preserves a queryable record even as data ages out of Servicemax or gets changed inside it.
Exasol: SQL over JDBC/ODBC drivers and a WebSocket-based client protocol. Authentication: Database credentials (username and password). 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. Exasol: Bulk loading uses the IMPORT statement, which is more efficient than row-by-row inserts for sync workloads. Stacksync's field mapping accounts for these differences between Exasol and Servicemax without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Exasol and Servicemax records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Exasol and Servicemax connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Exasol–Servicemax integration in-house.
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 437 integrations available for Exasol and Servicemax.