Home › Curriculum › Deploy, Operate & Upgrade › Version upgrades: the process and testing
Upgrades and migrations · 18 min · 17–20Version upgrades: the process and testing
Odoo's upgrade service, upgrade paths, the test-upgrade cycle, what breaks, and support windows.
In this lesson
- Release cadence, support and the upgrade service
- The test-upgrade cycle
- What breaks, by version
Key points
- Yearly majors; ~3 years standard support; 17 out of standard support around 20's launch
- upgrade.odoo.com for Enterprise (Online, Odoo.sh, on-prem script); OpenUpgrade for Community
- Test upgrade → port modules → test → repeat with fresh data → production with freeze
- Breakers: API changes, XPaths, Studio on merged apps, labels, security, unported third-party, runtime versions
Real-world example
A 19→20 test upgrade succeeded technically, but the client's field technicians couldn't find their interventions: Field Service had moved into Planning. The consultant remapped two Studio views and the dashboard, retrained the dispatchers, and the production upgrade went smoothly two weeks later.
Questions and answers
What is the upgrade script's test command target flag?
-t 20.0 (target version).
Name two Odoo 20 app merges that affect upgrades.
Field Service into Planning; Remote Work into Employees.