Two-way sync
Changes in Servicemax or VoltDB instantly reflect in both systems. No stale data, no manual imports.
Keep Servicemax and VoltDB in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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 VoltDB.
Stacksync mirrors Products, Work Orders, Work Details, Installed Products from Servicemax into Stored Procedures, Materialized Views, Streams, Export Targets and Topics in VoltDB 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.
Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
Records from Servicemax are ordinary rows in VoltDB; join them, index them, and use them in application logic without touching the vendor API.
Write to the synced tables in VoltDB and Stacksync propagates the change into Servicemax, replacing custom integration code.
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.
| Servicemax objects | VoltDB objects | How this pairing syncs | |
|---|---|---|---|
| Service Contracts SVMXC__Service_Contract__c; coverage and entitlement agreements; synced to warehouses for renewal, SLA, and warranty reporting. | Replicated Tables Small reference tables copied to every partition, a common landing spot for synced lookup data. | Service Contracts is specific to Servicemax and Replicated Tables to VoltDB — each maps to any object or custom field on the other side. | |
| Stock History SVMXC__Stock_History__c; append-only log of inventory transactions (RMA, shipment, parts receipt); read out for parts and inventory analytics. | Stored Procedures Precompiled transactional units that serve as the primary write interface. | Stock History is specific to Servicemax and Stored Procedures to VoltDB — each maps to any object or custom field on the other side. | |
| Accounts Standard Salesforce Account; customer and site company records; synced two-way with CRM and database customer tables. | Materialized Views Synchronously maintained aggregates over tables, useful as pre-computed read sources. | Accounts is specific to Servicemax and Materialized Views to VoltDB — each maps to any object or custom field on the other side. | |
| Contacts Standard Salesforce Contact; people linked to Accounts and service sites; synced with CRM and support person records. | Streams Insert-only constructs that feed the export subsystem with committed rows. | Contacts is specific to Servicemax and Streams to VoltDB — each maps to any object or custom field on the other side. | |
| Cases Standard Salesforce Case; support records that often precede a Work Order; synced with help desk tools and reporting databases. | Export Targets and Topics Connectors that push committed data to external systems such as Kafka or JDBC sinks. | Cases is specific to Servicemax and Export Targets and Topics to VoltDB — each maps to any object or custom field on the other side. | |
| Products Standard Salesforce Product2; catalog of serviceable products and spare parts referenced by Installed Products and Work Details. | Partitioned Tables Tables sharded across partitions by a partitioning column; the primary transactional store and sync target. | Products is specific to Servicemax and Partitioned Tables to VoltDB — 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.
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 VoltDB as a row-level write, with types converted between the two schemas.
DetectionStacksync polls VoltDB for changes on an incremental schedule, reading only records changed since the previous pass. Export streams and topics push committed changes to configured targets.
DeliveryEach detected change is written to Servicemax through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Servicemax–VoltDB connection.
Changes in Servicemax or VoltDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Servicemax or VoltDB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Servicemax or VoltDB record.
Track your Servicemax ⇄ VoltDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Servicemax and VoltDB.
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 Servicemax and VoltDB 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 Servicemax and VoltDB 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 Servicemax and VoltDB: authenticate both systems, choose the objects to sync (such as Servicemax's Service Contracts and Stock History), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Servicemax: Salesforce mechanisms — Apex triggers or polling on SystemModstamp/LastModifiedDate, with Change Data Capture / Platform Events available per object where enabled. On VoltDB: Export streams and topics push committed changes to configured targets; otherwise polling. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Servicemax side: Products, Work Orders, Work Details, Installed Products, plus custom fields where Servicemax exposes them. On the VoltDB side: Stored Procedures, Materialized Views, Streams, Export Targets and Topics. 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 Servicemax and VoltDB: One integration pattern for the whole stack; Read Servicemax with a query; Automate Servicemax from your codebase. Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
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. VoltDB: SQL over JDBC plus native client libraries and an HTTP/JSON interface. Authentication: Database credentials. 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 450 integrations available for Servicemax and VoltDB.