Skip to content
Business productivity ⇄ Data warehouse

Servicemax to Starburst Enterprise integration — real-time, two-way sync

Keep Servicemax and Starburst Enterprise 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 Servicemax and Starburst Enterprise

Get the data locked inside Servicemax into Starburst Enterprise as live tables, and send results back where Servicemax can use them, without writing a pipeline.

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 Starburst Enterprise continuously, handling schema, rate limits, and retries. Because the sync is bi-directional, results computed in Starburst Enterprise can also be written back into fields in Servicemax where the tool can use them.

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 Read federated views that join warehouse, lake, and database tables, then sync the result into operational tools like a CRM
  • 04 Expose Iceberg or Hive lake tables to sync jobs through one SQL endpoint without moving the data first

Common sync patterns

Analytics on Servicemax's data

Records and events from Servicemax land in Starburst Enterprise as queryable tables, current within seconds and ready to join with the rest of the warehouse.

Cross-tool reporting

Combine Servicemax's data with data from every other synced system to answer questions no single tool can.

Where Servicemax accepts updates: operational write-back

Segments, scores, or reference values computed in Starburst Enterprise sync back onto records in Servicemax, putting analysis where the work happens.

What you can sync between Servicemax and Starburst Enterprise

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 Starburst Enterprise objects How this pairing syncs
Service Contracts SVMXC__Service_Contract__c; coverage and entitlement agreements; synced to warehouses for renewal, SLA, and warranty reporting. Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. Service Contracts is specific to Servicemax and Catalogs to Starburst Enterprise — 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. Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. Stock History is specific to Servicemax and Schemas to Starburst Enterprise — 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. Tables Queryable relations; writes pass through to sources whose connectors support them. Accounts is specific to Servicemax and Tables to Starburst Enterprise — 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. Views Engine-level SQL views used to shape federated data before syncing it out. Contacts is specific to Servicemax and Views to Starburst Enterprise — 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. Materialized views Precomputed results that make repeated sync reads cheaper. Cases is specific to Servicemax and Materialized views to Starburst Enterprise — 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. Columns Typed per the Trino type system, mapped from each source's native types. Products is specific to Servicemax and Columns to Starburst Enterprise — each maps to any object or custom field on the other side.

How changes propagate between Servicemax and Starburst Enterprise

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.

Servicemax Starburst Enterprise 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 Starburst Enterprise as a row-level write, with types converted between the two schemas.

Starburst Enterprise Servicemax Interval-based propagation

DetectionStacksync polls Starburst Enterprise for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling.

DeliveryEach detected change is written to Servicemax through its API, with automatic retries and rate-limit backoff.

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.
  • Starburst Enterprise: Throughput is governed by cluster sizing and resource groups rather than API quotas.
What ships with Servicemax ⇄ Starburst Enterprise

Connect Servicemax and Starburst Enterprise for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Servicemax–Starburst Enterprise connection.

Real-time

Two-way sync

Changes in Servicemax or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Servicemax or Starburst Enterprise 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 Servicemax or Starburst Enterprise record.

Observability

Monitoring

Track your Servicemax ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Servicemax and Starburst Enterprise.

How the Servicemax and Starburst Enterprise connectors work

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

Starburst Enterprise

Integration surface
ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol
Authentication
Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos
Change detection
Query-based polling; Starburst is a query engine and exposes no change log of its own
Capabilities
read · write
Rate limits
Throughput is governed by cluster sizing and resource groups rather than API quotas
How it works

How to connect Servicemax to Starburst Enterprise — 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.

  1. 01

    Connect your apps

    Authenticate Servicemax and Starburst Enterprise with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Servicemax connected
    Starburst Enterprise connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Servicemax and Starburst Enterprise 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Servicemax ⇄ Starburst Enterprise
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Servicemax Starburst Enterprise
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Servicemax and Starburst Enterprise integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 441 integrations available for Servicemax and Starburst Enterprise.

Popular · 6 of 441
All Servicemax integrations All Starburst Enterprise integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own