Two-way sync
Changes in Greenplum or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Keep Greenplum 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 Greenplum continuously, handling schema, rate limits, and retries. Because the sync is bi-directional, results computed in Greenplum can also be written back into fields in Servicemax where the tool can use them.
Combine Servicemax's data with data from every other synced system to answer questions no single tool can.
Segments, scores, or reference values computed in Greenplum sync back onto records in Servicemax, putting analysis where the work happens.
A continuously synced copy in Greenplum preserves a queryable record even as data ages out of Servicemax or gets changed inside it.
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.
| Greenplum objects | Servicemax objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Namespace tables and control which objects a sync can see. | Cases Standard Salesforce Case; support records that often precede a Work Order; synced with help desk tools and reporting databases. | Schemas is specific to Greenplum and Cases to Servicemax — each maps to any object or custom field on the other side. | |
| Tables Heap or append-optimized tables mapped directly to sync targets. | Products Standard Salesforce Product2; catalog of serviceable products and spare parts referenced by Installed Products and Work Details. | Tables is specific to Greenplum and Products to Servicemax — each maps to any object or custom field on the other side. | |
| Partitions Large tables are commonly partitioned by date, which shapes incremental reads. | 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. | Partitions is specific to Greenplum and Work Orders to Servicemax — each maps to any object or custom field on the other side. | |
| Views Read-only projections used to shape data before syncing it out. | 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. | Views is specific to Greenplum and Work Details to Servicemax — each maps to any object or custom field on the other side. | |
| External tables Reference external files for bulk load paths alongside row-level syncs. | Installed Products SVMXC__Installed_Product__c; the installed-base asset record driving entitlement and service history; synced with asset and IoT databases. | External tables is specific to Greenplum and Installed Products to Servicemax — each maps to any object or custom field on the other side. | |
| Rows Read and written by key; distribution keys determine where rows live. | Service Contracts SVMXC__Service_Contract__c; coverage and entitlement agreements; synced to warehouses for renewal, SLA, and warranty reporting. | Rows is specific to Greenplum and Service Contracts 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 Greenplum for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key-based cursors.
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 Greenplum as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Greenplum–Servicemax connection.
Changes in Greenplum or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Greenplum 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 Greenplum or Servicemax record.
Track your Greenplum ⇄ Servicemax sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Greenplum 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 Greenplum 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 Greenplum 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 Greenplum and Servicemax: authenticate both systems, choose the objects to sync (such as Greenplum's Schemas and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Greenplum: Polling with timestamp or key-based cursors; Greenplum does not expose logical-decoding CDC. 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 Greenplum side: Databases, Schemas, Tables, Partitions. 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 Greenplum and Servicemax: Cross-tool reporting; Where Servicemax accepts updates: operational write-back; History that outlives the tool. Combine Servicemax's data with data from every other synced system to answer questions no single tool can.
Greenplum: PostgreSQL wire protocol (libpq), plus JDBC/ODBC drivers. Authentication: Database credentials. 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.
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 443 integrations available for Greenplum and Servicemax.