Review first
- List the module dependencies and check whether they exist in Odoo 19.
- Inspect models, fields, XML views, security and scheduled actions.
- Check custom JavaScript or assets separately.
Adapt carefully
- Update the manifest only after compatibility work is understood.
- Fix removed fields or changed model names with explicit code changes.
- Test installation on a clean Odoo 19 database before touching production data.
What to document
- Changed dependencies.
- Views or fields that were replaced.
- Known limitations that still require user acceptance.
Commands, screenshot and common errors
The block below keeps the article practical: one command/check, one visual reference and the first errors to inspect.
grep -R "version\|depends" __manifest__.py
# review models, views, security and assets before changing version numbers- Odoo cannot see the module because the addons path or folder nesting is wrong.
- The manifest declares a dependency that is missing from the current environment.
- The first real log error is often above later cascade errors.
Next step
A migration review can turn unknown risk into a scoped task list.