Review focus
- Installed module inventory and dependency visibility
- Manifest and version compatibility checks
- Custom module risk notes for Odoo 19
- Obvious view, model and security changes that may break
- Prioritized list of work before a full migration
Deliverable
- A readable issue list grouped by severity
- A short recommendation for next steps
- Clear separation between quick fixes, risky refactors and unknowns
- No production migration unless separately approved
Example deliverable
The result is delivered as a separate module, setup change, report or review with clear limitations, related links and follow-up steps.
Review process
- Collect the target Odoo version and module list.
- Inspect custom modules and known dependency risks.
- Flag likely Odoo 19 compatibility issues.
- Deliver a migration-readiness summary.
Estimate timing
The first estimate is prepared after reviewing the Odoo version, installed apps, workflow screenshots and sample records. If the input is incomplete, the first reply is a focused clarification list.
Limits
- The review does not guarantee a full successful migration by itself.
- Deep data migration, accounting reconciliation and production cutover are separate tasks.
- Third-party proprietary modules can only be assessed from the code or documentation you are allowed to share.
FAQ
Is this the same as migration implementation?
No. This page is for the analysis stage before implementation.
Can you review only custom modules?
Yes. That is often the safest first step.
Do you need a database dump?
Usually the first review can start from module code and metadata; database access is a separate decision.