Odoo has a set release cycle where a new major version comes out every year or so. The release of Odoo 20 in September 2026 means that organizations using Odoo will have to be aware of the new version, the support period for it, and other changes that affect their Odoo systems.
Nevertheless, Odoo does not only have major versions like 18.0, 19.0, or 20.0, but also intermediate SaaS versions that come out between major releases and are meant only for Odoo Online users.
Knowing the difference between the mentioned releases is important while upgrading databases, managing custom modules, and choosing hosting services.
The article will describe the release cycle and timeline of Odoo 20, intermediate SaaS versions, support periods, hosting upgrade policy, and how developers may check the Odoo version based on its source code.
1. Odoo 20 Release Date and Major Version Release Cycle
Odoo usually adheres to an annual major release strategy. Each major release includes new features, enhancements, technical changes, and changes for existing business applications.
The major release of Odoo 20.0 came out in September 2026.
What does a major release imply?
A major release comes with a new version of the Odoo framework and its default applications.
As an illustration, transitioning from Odoo 19.0 to Odoo 20.0 constitutes a major version update.
- Major versions can bring changes such as:
- New Python models and ORM features.
- Changes to JavaScript and OWL components.
- Modifications of XML views and templates.
- Changes to accounting and inventory procedures.
- New API features.
- Security updates.
- Database changes.
- Compatibility of third-party modules.
For enterprises utilizing customized Odoo installations, a major version update may necessitate checking custom modules, integrations, automated actions, and workflows.
You can check the latest release notes from Odoo Release Notes.
2. Understanding Odoo Version Numbering: Major vs Intermediate SaaS Versions
One of the most prevalent confusions amongst Odoo developers is the distinction between major versions and intermediate SaaS versions.
Odoo employs various versioning methods based on the hosting environment.
Major versions
Major versions are identified as follows:
Such versions are supported by Odoo Online, Odoo.sh, and on-premises installations.
Intermediate SaaS versions
Besides the major versions, Odoo releases intermediate versions in connection with its online platform.
For instance, the Odoo 19 range is made up of version numbers like
These intermediate versions provide improvements in between the major ones. In contrast to major versions, the SaaS versions are not available for Odoo Online. They do not have their own installation packages for Odoo.sh or the on-premises versions. From Odoo's support matrix available for November 2026, it can be seen that SaaS versions 19.1, 19.2, 19.3, and 19.4 are mentioned. The presence of version number 19.5 in the code related to upgrades cannot be taken alone as evidence of its release as a database version.
Where can developers find these version references?
Developers who are looking for any migration scripts specific to a particular version will find them here:
odoo/upgrade_code/
The upgrade_code directory stores some upgrade and migration scripts that are version-specific.
This folder can give some information about how Odoo deals with the process of transition from one version/database to another.
Nevertheless, the existence of the intermediary version number in migration-related scripts doesn’t necessarily imply that the particular version can be installed on its own.
What is the purpose of odoo/upgrade_code?
The command upgrade_code assists in rewriting an existing codebase with the help of migration scripts stored in the Odoo source repository.
It becomes especially handy while migrating custom modules across major versions.
./odoo-bin upgrade_code --from 19.0 --to 20.0 --dry-run
In this way, it finds out which source files are going to be rewritten using the available code migration scripts for moving from Odoo 18.0 to Odoo 19.0.
The –dry-run parameter makes it possible to inspect the expected changes before making any alterations to the files.
To make the changes, use the following command:
./odoo-bin upgrade_code --from 19.0 --to 20.0
The upgrade_code command accepts such parameters as:
- --from: Version from which the migration starts.
- --to: Destination version.
- --dry-run: Display changes without applying them.
- --script: Run a particular migration script.
- --glob: Filter out the files processed.
Note: The upgrade_code command is rewriting source code. It is not performing database migration and does not ensure that custom modules are going to function properly after an upgrade.
3. Odoo Support Lifecycle: How Long Is Each Version Supported?
Each version of Odoo is supported for three years after it is released.
This period is crucial since it is within this period that businesses get bug fixes and support for the installed version of Odoo.
According to the Odoo documentation, the official support for Odoo is provided for Odoo Online, Odoo.sh, and on-premise instances.
Odoo 20 Support Timeline
The table below shows the major versions of Odoo as of November 2026.
| Version | Release Date | End of Standard | Support Status |
| Odoo 16.0 | October 2022 | September 2025 | Ended |
| Odoo 17.0 | November 2023 | September 2026 | Ended |
| Odoo 18.0 | October 2024 | September 2027 (planned) | Supported |
| Odoo 19.0 | September 2025 | September 2028 (planned) | Supported |
| Odoo 20.0 | September 2026 | September 2029 (planned) | Supported |
The three latest major versions that are officially supported are Odoo 18.0, 19.0, and 20.0.
What happens when a version reaches the end of standard support?
This means that when one version becomes outdated, business organizations need to know the ramifications.
Standard support consists of:
- Security updates.
- Standard fixes.
- Helpdesk support.
- Support for the version itself.
After the expiry of the standard support period, the company will stop receiving any kind of security updates.
But it does not imply that the Odoo installation on the organization’s system is out of service.
There may be some form of extended support based on the platform hosting and subscription terms.
Standard Support vs Extended Support
Odoo has two types of support for qualified major versions.
| Feature | Standard Support | Extended Support |
| Security updates | Yes | No |
| Helpdesk support | Yes | Yes |
| Bug fixes | Yes | Where technically feasible |
| Additional support fee | No additional extended-support fee | Yes |
| Availability | Odoo Online, Odoo.sh, On-premise | Eligible Odoo.sh versions and on-premise |
Extended support is not provided for all hosting systems. Extended support is provided on-premise for eligible versions and through Odoo.sh for certain versions.
Businesses need to examine their existing subscription and support agreements before depending on extended support.
4. What Does the Support Policy Mean for Odoo 16, 17, and 18?
It is especially critical to know the support dates for earlier versions in cases when companies are using previous versions of Odoo.
Here is the current support status up to November 2026.
Odoo 16.0
Odoo 16 is at the end of its standard support cycle since September 2025.
Companies that are working with Odoo 16 have to look into upgrading because the version does not receive any further security updates.
Odoo 17.0
The last day of standard support for Odoo 17 was September 2026.
As November 2026 is shortly after this date, it means that users of Odoo 17 should start thinking about the upgrade process.
According to Odoo's documentation on upgrade eligibility, upgrades are possible even from a version that has ended the period of standard support within the last six months, taking into account upgrade conditions.
That is why Odoo 17 users should not delay upgrade planning.
Odoo 18.0
Odoo 18 is supported under standard support till September 2027 (planned).
Users of Odoo 18 do not have to move to Odoo 20 instantly.
Nevertheless, they should start considering the new version.
5. Odoo Online vs Odoo.sh vs On-Premise: Upgrade Policies
The upgrade policy in Odoo varies with respect to the hosting platform.
It is one of the key factors to consider while upgrading an Odoo version.
Odoo Online: Automatic Upgrade Policy
Odoo Online adopts the rolling release model.
Interim versions of SaaS are released periodically, and databases have to be migrated ahead of time when newer versions are released.
According to Odoo's upgrade documentation:
- Databases of major versions need to be upgraded every two years.
- Minor versions of SaaS need to be upgraded within a few weeks of the release of the next version.
- Administrators will get alerts before any mandatory upgrade.
- In case the upgrade is not performed before the deadline set, the system will perform an automatic upgrade.
Prior to the automatic upgrade, the Odoo Upgrade team will test the upgrade of the database.
If the test goes well and processing criteria are met, then the database can be upgraded using the interface.
Administrators should request an upgraded test database and confirm their workflows prior to the actual upgrade process.
This strategy allows Odoo Online users to stay with the supported versions without worrying about the server environment.
Odoo.sh: Controlled Upgrade Management
More flexibility is offered by Odoo.sh than by the Odoo Online platform.
There is the possibility to handle the development, staging, and production branches and to upgrade the databases before putting them into production.
Key features are:
- Support for major Odoo versions.
- Support for intermediate SaaS versions is absent.
- Integration with the Odoo upgrade platform is provided.
- Testing of the upgraded databases is possible in the staging environment.
- Development and testing of custom modules are possible.
Additionally, Odoo documentation allows extra time for upgrading from three years of standard support for a certain version.
The Odoo.sh FAQ also mentions that there is a surcharge for old versions and ultimate retirement of the platform for such versions. For example, according to Odoo.sh, there is a 25% surcharge for the subscription once the version reaches the age of three and a half years, and retirement after six years.
It is necessary to pay attention to Odoo.sh notifications and the current policy instead of relying on the possibility of hosting the old database forever.
On-Premise: Customer-Controlled Upgrades
On-premise solutions give you the most control over upgrading versions.
The company manages its own Odoo server and chooses when it wants to migrate to a new major version.
According to Odoo documentation, the on-premise solution theoretically can stay on the same version forever.
However, this is not recommended because after some time, the older versions will not receive security updates and bug fixes anymore.
Therefore, it becomes the business’s responsibility to do:
- server maintenance,
- database backup,
- security update,
- compatibility of custom modules,
- upgrade testing.
And all other things related to infrastructure.
6. How to Check the Odoo Version Using odoo/release.py
Those who develop using different versions of Odoo need to ensure that the version being developed is indeed what is being installed locally.
Version information is stored at:
odoo/release.py
This Python file holds the version information for the Odoo server.
What is version_info?
In release.py, developers will notice the following definition:
version_info = (20, 0, 0, FINAL, 0, '')
The version consists of the following elements:
| Position | Value | Meaning |
| 1 | 20 | Major version |
| 2 | 0 | Minor version |
| 3 | 0 | Micro version |
| 4 | FINAL | Release stage |
| 5 | 0 | Release serial |
| 6 | " | Additional version suffix |
For example, the declaration:
version_info = (20, 0, 0, FINAL, 0, '')
indicates that the source code belongs to the final Odoo 20.0 release.
How to verify the version from the terminal
Go to your Odoo source folder and execute:
grep -n "version_info\|series\|version =" odoo/release.py
This indicates the version declaration and associated variables.
In the case of a final Odoo 20.0 codebase, the above output should indicate version 20.0.
It becomes especially useful if you have to manage multiple Odoo installations or develop on different branches.
Important: The version data in release.py indicates the version of the codebase being run, but does not validate the version of another production database separately.
7. Planning Odoo Upgrades Around Support End Dates
The Odoo upgrades need to be treated as a planned exercise and not an ad-hoc activity that is done only when the support period ends.
Businesses running customized Odoo systems should plan their upgrade to the next version even before they reach the end-of-life of the existing version.
Why is it important to plan for an upgrade in advance?
An upgrade to Odoo will impact:
- Custom Python modules.
- XML views and inherited templates.
- JavaScript and OWL.
- External API integration.
- Accounting customization.
- Automated workflow.
- Third-party software.
- Reporting and dashboarding.
For instance, if an organization runs Odoo 18 with multiple custom modules, then they should not wait till September 2027 to assess the migration requirements.
This will give enough time to check and rectify all the issues related to deprecations, dependencies, and compatibility testing of critical processes.
8. Official Resources for Odoo 20 Version and Support Information
Developers and systems administrators are advised to consult official Odoo sources for release dates, support windows, and upgrades.
The following sources are especially helpful:
These resources help businesses verify current release information and understand the technical and operational requirements associated with each Odoo version.
This makes Odoo 20 the next iteration of Odoo’s yearly release schedule, where each major release is entitled to three years of support. Knowledge about the difference between major and SaaS releases, migration policies for the hosted editions, and support expiration dates will be useful in planning the process of migration to Odoo properly.
To read more about Odoo 20 Roadmap Explained: Key Updates and Future Expectations, refer to our blog, Odoo 20 Roadmap Explained: Key Updates and Future Expectations.