Real-time
Two-way sync
Changes in Servicemax or TiDB instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Database
Servicemax to TiDB integration — real-time, two-way sync
Keep Servicemax and TiDB 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 TiDB
Mirror Servicemax's data into TiDB 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 TiDB.
Stacksync mirrors Accounts, Contacts, Cases, Products from Servicemax into Sequences, Databases, Tables, Views in TiDB 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 Consolidate Service Contracts and entitlement data into a warehouse for renewal forecasting and SLA compliance dashboards.
- 02 Mirror Accounts and Contacts between ServiceMax and the CRM system of record so customer and site data stays consistent.
- 03 Serve mixed transactional and analytical workloads on synced data using TiFlash columnar replicas
- 04 Two-way sync between TiDB tables and SaaS tools so operational edits made in either system converge
Common sync patterns
Read Servicemax with a query
Records from Servicemax are ordinary rows in TiDB; join them, index them, and use them in application logic without touching the vendor API.
Automate Servicemax from your codebase
Write to the synced tables in TiDB 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 TiDB, so triggers, jobs, and services can respond in near real time.
What you can sync between Servicemax and TiDB
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 | TiDB objects | How this pairing syncs | |
|---|---|---|---|
| Stock History SVMXC__Stock_History__c; append-only log of inventory transactions (RMA, shipment, parts receipt); read out for parts and inventory analytics. | Sequences Server-side ID generation relevant when external systems write rows. | Stock History is specific to Servicemax and Sequences to TiDB — 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. | Databases MySQL-style schemas addressed by any MySQL-compatible client. | Accounts is specific to Servicemax and Databases to TiDB — 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. | Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. | Contacts is specific to Servicemax and Tables to TiDB — 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. | Views Logical views for shaping reads before syncing outward. | Cases is specific to Servicemax and Views to TiDB — 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 MySQL-compatible types mapped to fields in the paired system. | Products is specific to Servicemax and Columns to TiDB — each maps to any object or custom field on the other side. | |
| 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. | Indexes Secondary indexes that keep incremental sync queries efficient. | Work Orders is specific to Servicemax and Indexes to TiDB — each maps to any object or custom field on the other side. |
How changes propagate between Servicemax and TiDB
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 TiDB 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 TiDB as a row-level write, with types converted between the two schemas.
TiDB Servicemax Sub-second propagation
DetectionChanges in TiDB are captured at the source via change data capture — no polling loop against its API. Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks.
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.
- TiDB: Throughput scales with cluster size rather than fixed API quotas.
What ships with Servicemax ⇄ TiDB
Connect Servicemax and TiDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Servicemax–TiDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Servicemax or TiDB 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 TiDB record.
Observability
Monitoring
Track your Servicemax ⇄ TiDB 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 TiDB.
How the Servicemax and TiDB 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
TiDB
- Integration surface
- MySQL wire protocol (SQL)
- Authentication
- Database credentials (MySQL-compatible username/password)
- Change detection
- Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works
- Capabilities
- read · write · CDC
- Rate limits
- Throughput scales with cluster size rather than fixed API quotas
How it works
How to connect Servicemax to TiDB — 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 Servicemax and TiDB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Servicemax
connected
TiDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Servicemax and TiDB 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 · Servicemax ⇄ TiDBCustomers 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.
Servicemax TiDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Servicemax and TiDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Servicemax and TiDB: authenticate both systems, choose the objects to sync (such as Servicemax's Stock History and Accounts), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Servicemax and TiDB. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
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 TiDB: Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Servicemax side: Accounts, Contacts, Cases, Products, plus custom fields where Servicemax exposes them. On the TiDB side: Sequences, Databases, Tables, Views. 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 TiDB: Read Servicemax with a query; Automate Servicemax from your codebase; React to changes as they happen. Records from Servicemax are ordinary rows in TiDB; join them, index them, and use them in application logic without touching the vendor API.
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 434 integrations available for Servicemax and TiDB.
Popular · 7 of 434
-
Servicemax ⇄ Google AlloyDB -
Servicemax ⇄ Dynamo DB -
Servicemax ⇄ IBM Db2 -
Servicemax ⇄ Firebase -
TiDB ⇄ Gainsight -
TiDB ⇄ Ironclad -
TiDB ⇄ Adobe Sign
No integrations match .
