Step-by-Step Guide: Running a Test Upgrade on Odoo.sh

1) Prepare and Push the Upgrade Test Branch

Create a dedicated branch for the upgrade test, if you have not done so already.

This branch should contain all migrated code, including:

• Updated custom modules

• Any third-party/external modules compatible with Odoo v18 (your target version)

Once the branch is ready, push it to your Odoo.sh repository.

This branch will be used during the Test Upgrade process, so it must accurately represent the code intended for the upgraded environment.

2) Move the Upgrade Branch to the Staging Environment

In Odoo.sh:

1. Move your upgrade branch into the Staging environment.

2. Select the branch within the Staging section.

3. Navigate to the Upgrade tab.

4. Choose the Odoo version you want to upgrade from and to (e.g., upgrading to v18).

3) Start the Test Upgrade

Click the “Test Upgrade” button.

Odoo.sh will now begin the upgrade process, which includes:

• Executing Odoo’s official upgrade scripts

• Upgrading standard Odoo modules

• Updating the database schema to match the target version

Please wait now, allow the process to complete.

If any errors occur during the base Odoo upgrade stage, contact Odoo Support for assistance, as these typically relate to core modules or the database upgrade scripts.

4) Continue the Upgrade with Your Custom Modules

After Odoo successfully completes the core upgrade, the platform will prompt you to push an empty commit to your upgrade branch.

This step triggers the upgrade of your custom modules.

If an error appears after pushing the empty commit, it is likely caused by issues in your migrated custom code.
Read the error logs to understand the issue, resolve the issue in the code and then commit you changes again, odoo-sh will automatically continue the upgrade process from that point.

Wishing you Luck, 
Team Bloopark