Two-way sync
Changes in AWS Aurora MySQL or Odoo instantly reflect in both systems. No stale data, no manual imports.
Keep AWS Aurora MySQL and Odoo 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 Sales Orders (sale.order), Invoices (account.move), Products (product.template / product.product), CRM Leads (crm.lead) from Odoo into AWS Aurora MySQL 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 AWS Aurora MySQL sync back into Odoo with its validations respected.
Records from Odoo live in AWS Aurora MySQL 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.
Updates in Odoo arrive as row changes in AWS Aurora MySQL, so jobs and triggers can respond as the business record changes.
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.
| AWS Aurora MySQL objects | Odoo objects | |
|---|---|---|
| Primary keys and indexes Used to match rows across systems and keep incremental syncs efficient. | Contacts (res.partner) The unified person/company record used across sales, invoicing, and purchasing; the anchor for CRM syncs. | |
| Views Can serve as read-only sync sources for derived or filtered datasets. | Sales Orders (sale.order) Quotations and confirmed orders synced with e-commerce and external CRMs. | |
| Foreign keys Express relationships that syncs preserve when mapping to related objects elsewhere. | Invoices (account.move) Customer invoices and journal entries synced with accounting and reporting tools. | |
| Stored procedures and triggers Existing database logic keeps firing on rows written by a sync. | Products (product.template / product.product) Catalog and variant data distributed to storefronts and quoting tools. | |
| Databases (schemas) Logical namespaces that scope which tables a sync connection can see. | CRM Leads (crm.lead) Leads and opportunities synced with marketing and enrichment systems. | |
| Tables The primary sync unit; each table maps one-to-one to a table or object in the paired system. | Purchase Orders (purchase.order) Procurement documents shared with supplier-facing systems. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every AWS Aurora MySQL–Odoo connection.
Changes in AWS Aurora MySQL or Odoo instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever AWS Aurora MySQL or Odoo data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single AWS Aurora MySQL or Odoo record.
Track your AWS Aurora MySQL ⇄ Odoo sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between AWS Aurora MySQL and Odoo.
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 AWS Aurora MySQL and Odoo 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 AWS Aurora MySQL and Odoo 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 AWS Aurora MySQL and Odoo: authenticate both systems, choose the objects to sync (such as AWS Aurora MySQL's Primary keys and indexes and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on AWS Aurora MySQL: Log-based CDC via the MySQL binary log (binlog), with polling on timestamp columns as a fallback. On Odoo: Polling on the write_date timestamp every record carries; recent versions can also send outbound webhooks from automation rules. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the AWS Aurora MySQL side: Databases (schemas), Tables, Rows, Columns, plus custom fields where AWS Aurora MySQL exposes them. On the Odoo side: Sales Orders (sale.order), Invoices (account.move), Products (product.template / product.product), CRM Leads (crm.lead). 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 AWS Aurora MySQL and Odoo: Read ERP records with a query; Internal tools and automations without API code; React to ERP changes. Records from Odoo live in AWS Aurora MySQL as ordinary tables or collections, joinable with the rest of your data.
AWS Aurora MySQL: SQL wire protocol (MySQL-compatible), standard MySQL drivers and JDBC. Authentication: Database credentials, optionally AWS IAM database authentication, over TLS. 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. 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 AWS Aurora MySQL and Odoo.