Upgrading Odoo

calmo.cloud upgrades a service to a newer major version of Odoo (for example from 18.0 to 19.0) through Odoo's upgrade service. The upgraded database arrives in a new test service. The service you upgrade keeps running the whole time, so you can try the new version with your own data before you decide anything.

Before you start #

• An Odoo Enterprise subscription. Odoo only upgrades databases with an Enterprise subscription. calmo.cloud reads the subscription code from the database. If the database has none, enter the code when you start the upgrade.
• Your own addons for the new version. Odoo upgrades its own modules. Your addons need a branch for the new version in their repository (see Repositories). Addons without one are not deployed on the new service, and you are told which ones before the upgrade starts.
• Room on the server. The new service starts as a copy of the old one, and the database travels to Odoo and back. The checks tell you if the server is short of disk space.

Starting an upgrade #

1. Open the service, go to its Upgrades tab and click Upgrade.
2. Choose the Odoo version, and optionally a name and a server for the new service.
3. Click Next. calmo.cloud checks the database, the servers and your addons, and lists what it found:
   • Problems stop the upgrade until they are fixed, for example a missing subscription code or too little disk space.
   • Warnings need your confirmation, for example addons that have no version for the target, or the fact that the database is sent to Odoo SA.
4. Confirm the warnings and click Start upgrade.

What happens next #

The upgrade shows its progress on both services and on the Upgrades tab of the service:

1. Send — The database is dumped on your server and uploaded to Odoo. At the same time, the new service is created as a test copy of the old one, with its files.
2. At Odoo — Odoo upgrades the database on its own platform. This takes from a few minutes to several hours, depending on the size of the database. The latest lines of Odoo's log appear on the service page.
3. Receive — The upgraded database is downloaded to the new service, your addons are deployed in their versions for the new Odoo, their modules are upgraded, and the service starts on the new version.

Like every test service, the new service is neutralized: it sends no emails (they go to the mail catcher where your plan includes it) and runs no scheduled payment or synchronization jobs.

When something goes wrong #

• Odoo could not upgrade the database — The reason Odoo gives is shown on the upgrade. Odoo's request number is shown as well, which you can quote to Odoo's support.
• Loading the result failed — Often a migration script of one of your own addons. Fix the addon, then choose Load again on the upgrade. The new service is stopped meanwhile.
• You changed your mind — Choose Cancel upgrade while the upgrade is still with Odoo. The new service is deleted.

Odoo's upgrade report can be downloaded from the Upgrades tab once the upgrade is done.

Your data at Odoo #

To upgrade your database, Odoo SA receives a copy of it (without the filestore) and processes it on its own servers. By default, calmo.cloud asks Odoo to delete the data from its platform as soon as the upgrade is done. Keep the data at Odoo only if you want to open a ticket with Odoo about the upgrade.

Upgrading the live service #

Upgrades currently create a new test service. Moving your live service to the new version, including its domains, is coming in a later release.