Two-way sync
Changes in BigQuery or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Keep BigQuery 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 BigQuery continuously, handling schema, rate limits, and retries. Because the sync is bi-directional, results computed in BigQuery can also be written back into fields in Servicemax where the tool can use them.
A continuously synced copy in BigQuery preserves a queryable record even as data ages out of Servicemax or gets changed inside it.
Records and events from Servicemax land in BigQuery 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.
| BigQuery objects | Servicemax objects | How this pairing syncs | |
|---|---|---|---|
| Partitioned tables Synced like regular tables; partition columns map to target fields. | 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. | Partitioned tables is specific to BigQuery and Work Orders to Servicemax — each maps to any object or custom field on the other side. | |
| Clustered tables Supported; clustering is transparent to the sync. | 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. | Clustered tables is specific to BigQuery and Work Details to Servicemax — each maps to any object or custom field on the other side. | |
| Datasets Organizational container — you pick which dataset’s tables to sync. | Installed Products SVMXC__Installed_Product__c; the installed-base asset record driving entitlement and service history; synced with asset and IoT databases. | Datasets is specific to BigQuery and Installed Products to Servicemax — each maps to any object or custom field on the other side. | |
| Projects Connection scope: the service account grants access per project. | Service Contracts SVMXC__Service_Contract__c; coverage and entitlement agreements; synced to warehouses for renewal, SLA, and warranty reporting. | Projects is specific to BigQuery and Service Contracts to Servicemax — each maps to any object or custom field on the other side. | |
| Tables The syncable unit: only tables can be synced per the Stacksync docs. | Stock History SVMXC__Stock_History__c; append-only log of inventory transactions (RMA, shipment, parts receipt); read out for parts and inventory analytics. | Tables is specific to BigQuery 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.
DetectionChanges in BigQuery are captured at the source via change data capture — no polling loop against its API. Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen").
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 BigQuery as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every BigQuery–Servicemax connection.
Changes in BigQuery or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever BigQuery 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 BigQuery or Servicemax record.
Track your BigQuery ⇄ Servicemax sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between BigQuery 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 BigQuery 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 BigQuery 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 BigQuery and Servicemax: authenticate both systems, choose the objects to sync (such as BigQuery's Partitioned tables and Clustered tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both BigQuery and Servicemax. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on BigQuery: Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen") with a Cloud Run "secure portal for real-time notification service in. 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 BigQuery side: Partitioned tables, Clustered tables, Datasets, Projects. 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 BigQuery and Servicemax: History that outlives the tool; Analytics on Servicemax's data; Cross-tool reporting. A continuously synced copy in BigQuery preserves a queryable record even as data ages out of Servicemax or gets changed inside it.
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 547 integrations available for BigQuery and Servicemax.