Two-way sync
Changes in Sage 100 or TiDB instantly reflect in both systems. No stale data, no manual imports.
Keep Sage 100 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 GL Accounts, Journal Entries, Customers, Vendors from Sage 100 into TiDB and keeps both sides consistent in real time. Whatever Sage 100 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 Sage 100 with its validations respected.
Choose exactly which tables and fields may flow from TiDB back into Sage 100, keeping the ERP authoritative.
Records from Sage 100 live in TiDB as ordinary tables or collections, joinable with the rest of your data.
Scripts and services read and write the synced tables; Stacksync handles the Sage 100 interface, limits, and retries.
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.
| Sage 100 objects | TiDB objects | |
|---|---|---|
| Journal Entries Posted GL activity replicated to warehouses for FP&A. | Columns MySQL-compatible types mapped to fields in the paired system. | |
| Customers AR customer master records synced to CRMs for account and credit visibility. | Indexes Secondary indexes that keep incremental sync queries efficient. | |
| Vendors AP vendor master records synced with procurement and payment tools. | Sequences Server-side ID generation relevant when external systems write rows. | |
| Inventory Items Item master with pricing and quantities, synced to e-commerce catalogs. | Databases MySQL-style schemas addressed by any MySQL-compatible client. | |
| Sales Orders Order headers and lines, the usual write target for web and EDI orders. | Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. | |
| AR Invoices Billing documents synced outward for payment status and revenue reporting. | Views Logical views for shaping reads before syncing outward. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Sage 100–TiDB connection.
Changes in Sage 100 or TiDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Sage 100 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 Sage 100 or TiDB record.
Track your Sage 100 ⇄ TiDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Sage 100 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 Sage 100 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 Sage 100 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 Sage 100 and TiDB: authenticate both systems, choose the objects to sync (such as Sage 100's Journal Entries and Customers), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Sage 100 and TiDB: Controlled write-back; Read ERP records with a query; Internal tools and automations without API code. Choose exactly which tables and fields may flow from TiDB back into Sage 100, keeping the ERP authoritative.
Sage 100: ODBC (ProvideX driver) for reads; Business Object Interface (BOI) or Sage-provided web services for writes. Authentication: Sage 100 company and user credentials; ODBC DSN credentials for direct reads. TiDB: MySQL wire protocol (SQL). Authentication: Database credentials (MySQL-compatible username/password). Stacksync manages authentication, retries, and rate limits on both sides.
TiDB: Storage and compute scale horizontally by adding TiKV and TiDB nodes rather than resizing a single server. Sage 100: Sage 100 (formerly MAS 90/200) is an on-premise ERP; its data files are exposed for reads through a ProvideX ODBC driver with module-prefixed tables such as AR_Customer and SO_SalesOrderHeader. Stacksync's field mapping accounts for these differences between Sage 100 and TiDB 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 Sage 100 and TiDB records are not retained after a sync operation.
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 Sage 100 and TiDB.