Upgrading Odoo brings new features, performance improvements and continued support, but organisations with customisations often postpone it. A structured approach makes upgrades predictable.
1. Inventory what is installed
List every installed module: standard, third-party and custom. For each one, decide whether it is still needed, whether a target-version equivalent exists, and whether it must be ported.
2. Port, do not copy
Custom modules must be adapted to the target version. APIs, view syntax and models change between versions. Porting is also the right time to retire unused features.
3. Define control figures
- Trial balance at the cut-over date
- Aged receivables and payables
- Stock quantities and valuation
- Record counts for key documents
- Open documents such as unpaid invoices and pending orders
4. Rehearse
Run the full upgrade at least once on a copy of production, let key users test their daily work, and measure how long each step takes. The rehearsal becomes the cut-over plan.
5. Plan the switch and support
Choose a cut-over window, freeze changes, run the final migration, verify control figures and provide close support in the first days after go-live.