Real-time
Two-way sync
Changes in Citus or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Business productivity
Citus to Servicemax integration — real-time, two-way sync
Keep Citus 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 Citus and Servicemax
Mirror Servicemax's data into Citus 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 Citus.
Stacksync mirrors Accounts, Contacts, Cases, Products from Servicemax into Local tables, Schemas, Views, Sequences in Citus 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 Sync Work Orders (SVMXC__Service_Order__c) and Work Details bi-directionally with Postgres so ops and analytics teams read and write field-service data in plain SQL.
- 02 Keep Installed Products (SVMXC__Installed_Product__c) aligned with an asset or IoT database for warranty, entitlement, and service-history reporting.
- 03 Sync high-volume event or tenant data from a Citus cluster into a warehouse for cross-tenant analytics.
- 04 Write CRM or billing records into reference tables so distributed queries can join operational context locally on every node.
Common sync patterns
Automate Servicemax from your codebase
Write to the synced tables in Citus and Stacksync propagates the change into Servicemax, replacing custom integration code.
React to changes as they happen
Updates in Servicemax arrive as row changes in Citus, 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.
What you can sync between Citus 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.
| Citus objects | Servicemax objects | How this pairing syncs | |
|---|---|---|---|
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Contacts Standard Salesforce Contact; people linked to Accounts and service sites; synced with CRM and support person records. | Distributed tables is specific to Citus and Contacts to Servicemax — each maps to any object or custom field on the other side. | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Cases Standard Salesforce Case; support records that often precede a Work Order; synced with help desk tools and reporting databases. | Reference tables is specific to Citus and Cases to Servicemax — each maps to any object or custom field on the other side. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Products Standard Salesforce Product2; catalog of serviceable products and spare parts referenced by Installed Products and Work Details. | Local tables is specific to Citus and Products to Servicemax — each maps to any object or custom field on the other side. | |
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | 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 Citus and Work Orders to Servicemax — each maps to any object or custom field on the other side. | |
| Views Curated projections over distributed data, often used as read-only sync sources. | 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 Citus and Work Details to Servicemax — each maps to any object or custom field on the other side. | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | Installed Products SVMXC__Installed_Product__c; the installed-base asset record driving entitlement and service history; synced with asset and IoT databases. | Sequences is specific to Citus and Installed Products to Servicemax — each maps to any object or custom field on the other side. |
How changes propagate between Citus 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.
Citus Servicemax Sub-second propagation
DetectionChanges in Citus are captured at the source via change data capture — no polling loop against its API. PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres.
DeliveryEach detected change is written to Servicemax through its API, with automatic retries and rate-limit backoff.
Servicemax Citus 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 Citus 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 Citus ⇄ Servicemax
Connect Citus and Servicemax for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Servicemax connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus 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 Citus or Servicemax record.
Observability
Monitoring
Track your Citus ⇄ Servicemax sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Citus and Servicemax.
How the Citus and Servicemax connectors work
Citus
- Integration surface
- PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
- Authentication
- Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
- Change detection
- PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
- 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 Citus 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.
- 01
Connect your apps
Authenticate Citus 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.
Citus
connected
Servicemax
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus 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.
objects · Citus ⇄ ServicemaxCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Citus ServicemaxCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and Servicemax integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Citus and Servicemax: authenticate both systems, choose the objects to sync (such as Citus's Distributed tables and Reference tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Servicemax: Change Data Capture and Platform Events give near-real-time change feeds but must be enabled per object, and managed-package objects may need the vendor to expose them. Citus: The managed cloud offering is Azure Cosmos DB for PostgreSQL, which is Citus under a Microsoft brand. Stacksync's field mapping accounts for these differences between Citus 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 Citus and Servicemax records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Citus and Servicemax connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Citus–Servicemax integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Citus and Servicemax. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Citus: PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres. 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.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 437 integrations available for Citus and Servicemax.
Popular · 6 of 437
-
Citus ⇄ ConnectWise -
Citus ⇄ eClinicalWorks -
Servicemax ⇄ SQL Server -
Servicemax ⇄ Postgres Heroku -
Servicemax ⇄ Airtable -
Servicemax ⇄ AWS Aurora MySQL
No integrations match .
