Odoo Migration Audit Tool
The Migration Audit scans your custom module for breaking changes between Odoo versions before you begin the upgrade. It identifies deprecated XML view attributes (attrs/states), legacy JavaScript patterns (odoo.define, web.Widget), XPath view inheritance risks, field and model compatibility issues, and runtime-only constructs (ir.actions.server, record rules, mail.thread) that require manual testing.
Who It's For
- Odoo developers and partners planning version migrations (for example, Odoo 14 to 17 or Odoo 15 to 18)
- Technical leads estimating migration effort
- QA teams preparing test plans
Common Problems It Solves
- Deprecated
attrsandstatesview attributes (Odoo 16+) - Legacy
odoo.defineJavaScript (OWL migration in Odoo 15+) - Legacy
web.Widgetusage (OWL migration in Odoo 15+) - XPath view inheritance targeting nodes that changed
- Fields that were removed or renamed between versions
- Runtime-only server actions (
ir.actions.server) needing manual verification - Record rules needing retesting
- Model incompatibilities (
mail.thread, tracking changes)
How It Works
Select source and target Odoo versions, then upload a module ZIP. Static analysis scans XML, Python, JavaScript, and data files. Each finding includes a risk level, a recommendation, and verification steps. The audit generates a report organized by severity.
Limitations
The audit does not migrate the module automatically and does not execute code in a target Odoo instance. Runtime constructs such as server actions, workflows, and computed methods require clean target database testing.
Audit your migration risks
Pick source and target versions, upload your module, and review findings by severity.
Run Migration Audit