Two-way sync
Changes in Odoo or TiDB instantly reflect in both systems. No stale data, no manual imports.
Keep Odoo 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 Employees (hr.employee), Projects and Tasks (project.project / project.task), Contacts (res.partner), Sales Orders (sale.order) from Odoo into TiDB and keeps both sides consistent in real time. Whatever Odoo 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 Odoo with its validations respected.
Choose exactly which tables and fields may flow from TiDB back into Odoo, keeping the ERP authoritative.
Records from Odoo 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 Odoo 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.
| Odoo objects | TiDB objects | |
|---|---|---|
| CRM Leads (crm.lead) Leads and opportunities synced with marketing and enrichment systems. | Sequences Server-side ID generation relevant when external systems write rows. | |
| Purchase Orders (purchase.order) Procurement documents shared with supplier-facing systems. | Databases MySQL-style schemas addressed by any MySQL-compatible client. | |
| Inventory Transfers (stock.picking) Delivery and receipt operations synced for fulfillment visibility. | Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. | |
| Employees (hr.employee) HR records read for directory and provisioning syncs. | Views Logical views for shaping reads before syncing outward. | |
| Projects and Tasks (project.project / project.task) Work items synced with external project tools. | Columns MySQL-compatible types mapped to fields in the paired system. | |
| Contacts (res.partner) The unified person/company record used across sales, invoicing, and purchasing; the anchor for CRM syncs. | Indexes Secondary indexes that keep incremental sync queries efficient. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Odoo–TiDB connection.
Changes in Odoo or TiDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Odoo 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 Odoo or TiDB record.
Track your Odoo ⇄ TiDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Odoo 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 Odoo 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 Odoo 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 Odoo and TiDB: authenticate both systems, choose the objects to sync (such as Odoo's CRM Leads (crm.lead) and Purchase Orders (purchase.order)), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the TiDB side: Views, Columns, Indexes, Sequences, plus custom fields where TiDB exposes them. On the Odoo side: Employees (hr.employee), Projects and Tasks (project.project / project.task), Contacts (res.partner), Sales Orders (sale.order). 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 Odoo 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 Odoo, keeping the ERP authoritative.
Odoo: XML-RPC and JSON-RPC external API exposing the full ORM (search_read, create, write, unlink). Authentication: Database user credentials or per-user API keys. TiDB: MySQL wire protocol (SQL). Authentication: Database credentials (MySQL-compatible username/password). Stacksync manages authentication, retries, and rate limits on both sides.
TiDB: TiFlash maintains columnar replicas of row data, letting analytical queries run on current data without a separate warehouse. Odoo: Every record carries create_date and write_date fields, which makes timestamp-based incremental polling reliable across all models. Stacksync's field mapping accounts for these differences between Odoo and TiDB without custom code.
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 Odoo and TiDB.