Upgrades

Six months before your Odoo version reaches its end of support, a banner appears on the project. Upgrades are done in two steps, from the Upgrade tab of a branch:

Test the upgrade on staging On a staging branch, pick the target version and start Test an upgrade . A copy of the latest daily production backup is upgraded: production is never touched. Community databases use OpenUpgrade (one major version at a time); Enterprise databases use Odoo's upgrade service with your subscription code.

Port your modules The staging branch is now in upgrade mode : every push loads the upgraded database and updates your modules. Port your custom modules to the new version on this branch until the build is green, and test in Odoo.

Upgrade production On the production branch, request the upgrade to the tested version, then merge your ported code into production. 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.

Tip: a development branch can build on another major version (in its Settings tab) while you port your modules.