Tools
Migration Audit
Upload a module ZIP and scan all files for breaking changes when migrating between Odoo versions. Get a readiness score, per-file findings, and a structured checklist.
Important Disclaimer
Odoo Doctor provides static analysis and AI-assisted recommendations only. It does not:
- Guarantee complete migration compatibility
- Perform automatic Odoo migration
- Replace manual code review or runtime testing
Users are responsible for reviewing and testing all changes before applying to production.
What it analyzes
The audit scans every file type in your module:
- Manifest (
__manifest__.py) — Version-specific keys, dependencies - Python (
.py) — Deprecated APIs, renamed methods, import changes, field definition changes - XML (
.xml) — View inheritance changes, deprecated attributes, action changes - JavaScript (
.js) — OWL framework migration, deprecated APIs - Data files (
.csv) — Field name changes, required columns - Field definitions — Removed/renamed fields between versions
- Security — ACL/record rule format changes
- Manual review hints — Patterns requiring human judgment
How it works (static analysis)
- Package-level reports — Generates per-module findings within a multi-module ZIP
- Field Compatibility Coverage — Compares field definitions between source and target Odoo versions
- Target field index — When a target version's field index is unavailable, field-level compatibility checks are limited
- AI is not used to scan uploaded source code — Migration analysis uses static rule-based scanning, not AI inspection of your source files
- Runtime testing is still required — Static analysis cannot detect all runtime issues; always test in staging
Output
- Score — 0-100 migration readiness score
- Risk Level — low, medium, high, critical
- Findings — Detailed list per file with severity and confidence
- Checklist — Migration steps grouped by type
- Insights — Suggested migration order, module analysis
- Client Summary — Plain-language conclusion and recommended next steps
- Field Compatibility — Field-level changes between versions
- Follow-up Chat — Ask questions about specific findings
What it does NOT do
- Does not migrate your database or data
- Does not handle third-party module compatibility
- Does not test runtime behavior — this is static analysis only
- Does not scan Odoo core or OCA modules for migration readiness
- Does not automatically migrate code
Best practices
- Run the audit on a clean, version-controlled copy of your module
- Review the checklist systematically before starting manual migration work
- Use the follow-up chat to explore specific findings in detail
- Combine with the Error Analyzer for migration-related errors after manual testing
- Always test in a staging environment before deploying to production
- ZIP-based Migration Audits cannot be automatically re-run because uploaded ZIP files are not stored after analysis. To run a new audit, upload the ZIP again.