Documentation › Day to day
Upgrades
Move to a newer Odoo version (up to Odoo 19 today) with the upgrade assistant: readiness, a test on a copy with automated checks, then a scheduled production upgrade with automatic rollback.
Six months before your Odoo version reaches its end of support, a banner appears on the project. Upgrades are done from the Upgrade section of a production or staging branch: open the branch and pick More → Upgrade . The target versions go up to Odoo 19 today. Community databases are upgraded with OpenUpgrade (one major version at a time); Enterprise databases use Odoo's upgrade service with your subscription code (register it in your production Odoo first).
The upgrade assistant
At the top of the Upgrade section, pick the target version. The assistant then guides you through three steps:
1. Readiness Check readiness reads the modules installed on production and where each one's code comes from: Odoo itself, Odoo Enterprise, an OCA repository (does it have a branch and the module for the target version?), your own repository (is there a branch with the target version's code, for example 18.0 ?), or nowhere at all. It also flags apps renamed or merged between the versions, and shows the database size and the expected duration. The verdict is Ready to test , Review before upgrading or Not ready yet , with the modules that need attention listed first.
2. Test on a copy Start the test creates a staging branch upgrade-<version> from the branch with the target-version code (the branch named like the version, or one you pick), backs up production and upgrades that copy: production keeps running and is not modified. The branch restores the upgraded copy and updates your modules, then smoke checks run: the server, /web/login , each app's menu as the admin, key models, record counts before and after (partners, invoices, sale orders, products, stock moves) and the errors in the logs. Push fixes to the branch and use Try again to check its newest build. You are notified when the report is ready.
3. Schedule Choose when the window starts and how long it lasts, and whether the tested branch is merged into production with the upgrade ( Code for Odoo … ), then Schedule the upgrade (project admins). In the window, visitors see a maintenance page, a fresh backup is taken, production is upgraded and the same smoke checks run. Visitors are let in only when they pass; otherwise production is rolled back automatically to its previous version, build and backup. Admins are notified, also by email, at each step.
Each run's report and log stay listed under the assistant. Scheduling without a passed test needs an explicit tick ( Schedule it without a passed test ).
Upgrading step by step
Below the assistant, the same upgrade can be run by hand:
On a staging branch : Test upgrade on staging upgrades a copy of the latest daily production backup and loads it on that branch. The branch is then in upgrade mode : every push loads the upgraded database and updates your modules, so port them there until the build is green. Exit upgrade mode goes back to a normal staging copy.
On the production branch : Upgrade production upgrades the live database to the tested version right away; merge your ported code into production too. The upgrade runs with that production build (right away when the repository has no custom modules).
During the production upgrade Production is unavailable and visitors see a maintenance page. A backup is taken first, and it is restored automatically if anything fails. You are notified in the bell (and by email) when it starts and ends. A project's Settings → Maintenance window sets when disruptive work is allowed.
Tip: a development branch can build on another major version (in its Settings tab, Odoo version ) while you port your modules.