Two-way sync
Changes in MariaDB or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Keep MariaDB 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.
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 MariaDB.
Stacksync mirrors Work Details, Installed Products, Service Contracts, Stock History from Servicemax into Stored Procedures, Databases (Schemas), Tables, Views in MariaDB 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.
Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
Records from Servicemax are ordinary rows in MariaDB; join them, index them, and use them in application logic without touching the vendor API.
Write to the synced tables in MariaDB and Stacksync propagates the change into Servicemax, replacing custom integration code.
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.
| MariaDB objects | Servicemax objects | How this pairing syncs | |
|---|---|---|---|
| Stored Procedures Server-side logic that can post-process synced rows. | Cases Standard Salesforce Case; support records that often precede a Work Order; synced with help desk tools and reporting databases. | Stored Procedures is specific to MariaDB and Cases to Servicemax — each maps to any object or custom field on the other side. | |
| Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. | Products Standard Salesforce Product2; catalog of serviceable products and spare parts referenced by Installed Products and Work Details. | Databases (Schemas) is specific to MariaDB and Products to Servicemax — each maps to any object or custom field on the other side. | |
| Tables The primary sync target; rows map to records in connected systems. | 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. | Tables is specific to MariaDB and Work Orders to Servicemax — each maps to any object or custom field on the other side. | |
| Views Read-side projections used as outbound 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 MariaDB and Work Details to Servicemax — each maps to any object or custom field on the other side. | |
| Columns Field-level mapping targets with engine-typed values. | Installed Products SVMXC__Installed_Product__c; the installed-base asset record driving entitlement and service history; synced with asset and IoT databases. | Columns is specific to MariaDB and Installed Products to Servicemax — each maps to any object or custom field on the other side. | |
| Primary and Unique Keys Match keys for idempotent upserts. | Service Contracts SVMXC__Service_Contract__c; coverage and entitlement agreements; synced to warehouses for renewal, SLA, and warranty reporting. | Primary and Unique Keys is specific to MariaDB 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.
DetectionChanges in MariaDB are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing.
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 MariaDB as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MariaDB–Servicemax connection.
Changes in MariaDB or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever MariaDB 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 MariaDB or Servicemax record.
Track your MariaDB ⇄ Servicemax sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between MariaDB 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 MariaDB 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 MariaDB 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 MariaDB and Servicemax: authenticate both systems, choose the objects to sync (such as MariaDB's Stored Procedures and Databases (Schemas)), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for MariaDB and Servicemax: One integration pattern for the whole stack; Read Servicemax with a query; Automate Servicemax from your codebase. Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
MariaDB: SQL wire protocol (MySQL-compatible client/server protocol). Authentication: Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host). 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.
Servicemax: Syncs consume the Salesforce org-wide daily API allocation shared by every integration; it varies by edition and license count. MariaDB: MariaDB is protocol- and binlog-compatible with MySQL, so most MySQL drivers and CDC tooling work unchanged. Stacksync's field mapping accounts for these differences between MariaDB 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 MariaDB and Servicemax records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed MariaDB and Servicemax connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom MariaDB–Servicemax integration in-house.
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 448 integrations available for MariaDB and Servicemax.