Two-way sync
Changes in JobBOSS² or TiDB instantly reflect in both systems. No stale data, no manual imports.
Keep JobBOSS² 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.
ERP data sits behind interfaces built for the ERP's own modules, not for your internal systems. Teams that need those records, for reporting services, internal tools, or automations, end up writing integration code against a strict API and maintaining it through every upgrade.
Stacksync mirrors Time Entries, Invoices, Shipments, Customers from JobBOSS² into TiDB and keeps both sides consistent in real time. Whatever JobBOSS² is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in TiDB sync back into JobBOSS² with its validations respected.
Worker and org records stay current in TiDB for provisioning, access, and reporting systems that read from the database.
Choose exactly which tables and fields may flow from TiDB back into JobBOSS², keeping the ERP authoritative.
Records from JobBOSS² live in TiDB as ordinary tables or collections, joinable with the rest of your data.
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.
| JobBOSS² objects | TiDB objects | |
|---|---|---|
| Vendors Vendor records keep procurement and accounting tools consistent. | Views Logical views for shaping reads before syncing outward. | |
| Time Entries Shop-floor time data consolidates into costing and payroll reporting. | Columns MySQL-compatible types mapped to fields in the paired system. | |
| Invoices Billing documents flow to accounting and BI systems. | Indexes Secondary indexes that keep incremental sync queries efficient. | |
| Shipments Shipment records close the loop to customers and CRM records. | Sequences Server-side ID generation relevant when external systems write rows. | |
| Customers Customer records sync with CRM accounts so sales and the shop share one file. | Databases MySQL-style schemas addressed by any MySQL-compatible client. | |
| Quotes / Estimates Estimating records sync to CRM pipelines so quote status is visible outside the ERP. | Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every JobBOSS²–TiDB connection.
Changes in JobBOSS² or TiDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever JobBOSS² or TiDB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single JobBOSS² or TiDB record.
Track your JobBOSS² ⇄ TiDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between JobBOSS² and TiDB.
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 JobBOSS² 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.
Pick the JobBOSS² 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.
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 JobBOSS² and TiDB: authenticate both systems, choose the objects to sync (such as JobBOSS²'s Vendors and Time Entries), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on JobBOSS²: Polling. 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 TiDB side: Columns, Indexes, Sequences, Databases, plus custom fields where TiDB exposes them. On the JobBOSS² side: Time Entries, Invoices, Shipments, Customers. 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 JobBOSS² and TiDB: Where JobBOSS² is the HR system of record: people data for internal systems; Controlled write-back; Read ERP records with a query. Worker and org records stay current in TiDB for provisioning, access, and reporting systems that read from the database.
JobBOSS²: REST API (vendor-provided; coverage varies by edition and deployment). Authentication: API key or vendor-issued credentials. TiDB: MySQL wire protocol (SQL). Authentication: Database credentials (MySQL-compatible username/password). Stacksync manages authentication, retries, and rate limits on both sides.
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 386 integrations available for JobBOSS² and TiDB.