Skip to content
Database ⇄ ERP

AWS Aurora MySQL to Odoo integration — real-time, two-way sync

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.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from Mulesoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect AWS Aurora MySQL and Odoo

Give your engineers Odoo's data in AWS Aurora MySQL: read it with normal queries, write back through the sync, and skip the ERP API entirely.

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.

Common use cases

  • Give backend services read and write access to ERP or billing data by syncing it into Aurora tables the application already queries.
  • Stream row changes from Aurora into SaaS tools via binlog CDC instead of scheduled batch exports.
  • Mirror invoices and journal entries into a warehouse for consolidated financial reporting across entities.
  • Keep product and price list data aligned between Odoo and storefronts or marketplaces.

Read ERP records with a query

Records from Odoo live in AWS Aurora MySQL as ordinary tables or collections, joinable with the rest of your data.

Internal tools and automations without API code

Scripts and services read and write the synced tables; Stacksync handles the Odoo interface, limits, and retries.

React to ERP changes

Updates in Odoo arrive as row changes in AWS Aurora MySQL, so jobs and triggers can respond as the business record changes.

What you can sync between AWS Aurora MySQL and Odoo

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.
What ships with AWS Aurora MySQL ⇄ Odoo

Connect AWS Aurora MySQL and Odoo for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every AWS Aurora MySQL–Odoo connection.

Real-time

Two-way sync

Changes in AWS Aurora MySQL or Odoo instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever AWS Aurora MySQL or Odoo data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single AWS Aurora MySQL or Odoo record.

Observability

Monitoring

Track your AWS Aurora MySQL ⇄ Odoo sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between AWS Aurora MySQL and Odoo.

How the AWS Aurora MySQL and Odoo connectors work

AWS Aurora MySQL

Integration surface
SQL wire protocol (MySQL-compatible), standard MySQL drivers and JDBC
Authentication
Database credentials, optionally AWS IAM database authentication, over TLS
Change detection
Log-based CDC via the MySQL binary log (binlog), with polling on timestamp columns as a fallback
Capabilities
read · write · CDC

Odoo

Integration surface
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
Change detection
Polling on the write_date timestamp every record carries; recent versions can also send outbound webhooks from automation rules
Capabilities
read · write · webhooks
Rate limits
Self-hosted instances have no fixed rate limits; Odoo Online is subject to the platform's fair-use limits
How it works

How to connect AWS Aurora MySQL to Odoo — three steps, no code

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.

  1. 01

    Connect your apps

    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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    AWS Aurora MySQL connected
    Odoo connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · AWS Aurora MySQL ⇄ Odoo
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    AWS Aurora MySQL Odoo
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

AWS Aurora MySQL and Odoo integration FAQ

SECURITY

Security teams love Stacksync

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.

SOC 2 type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for AWS Aurora MySQL and Odoo.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.