Each new Odoo release brings useful features, but older versions eventually stop receiving fixes and security updates. Upgrading is not a one-click job when you have custom modules or years of data, so here is the plan we follow.
1. Audit what you have
- List every custom module and what it is used for
- List Studio customisations (fields, views, automations)
- Check that third-party apps exist for the target version
- Remove modules nobody uses any more
This step alone often saves time: on an Odoo 15 → 16 Enterprise upgrade we delivered for a trading company in Riyadh, old code-level customisations were holding the upgrade back. Together with the client we decided on a clean installation instead of carrying legacy code forward.
2. Upgrade a copy, never production
Always start on a duplicate database, a staging branch on Odoo.sh, or a copy on a separate server. Enterprise customers can use Odoo’s upgrade service to get an upgraded database; Community users typically rely on the OpenUpgrade project or custom scripts.
3. Migrate custom modules
Every major version changes parts of the framework. Custom modules need to be updated for new APIs, views and front-end components (OWL). This is the step that needs experienced Odoo developers.
4. Test with the people who use it
- Run your key flows end to end: quote → order → delivery → invoice → payment
- Compare reports and balances between old and new databases
- Let key users test for several days and sign off
5. Plan the cut-over
Pick a quiet period (often a weekend), freeze changes in the old system, run the final upgrade on the latest data, check the numbers again and switch users over. Keep the old database read-only for reference.
6. Watch closely after go-live
Monitor logs, performance and scheduled actions in the first weeks, and keep a support channel open for users.
Planning an upgrade? book a free 30-minute consultation, we will review your modules and give you a clear plan and estimate.
ERP consultant.
Leave a Reply