Odoo 20 is here. Move your Odoo ERP to the latest version with a tested plan for your data, custom modules and integrations, and stop paying extra for an outdated system.
Odoo 20 was released in September 2026 and is now the latest major version of Odoo ERP. Many businesses are already planning their next upgrade. Others are still holding back.
The hesitation is understandable. Companies worry about downtime, unexpected costs, technical effort, or a system that no longer works the way it used to.
But keeping Odoo up to date is essential for the security and long-term stability of your ERP, and Odoo’s support policy now makes waiting more expensive.
Odoo’s support policy at a glance
Odoo now supports every version indefinitely, but only the three most recent major versions are covered at the standard price. Since April 2026, Odoo Enterprise customers on older versions pay a 25% surcharge on their annual subscription to keep that support.
With Odoo 20 released, the covered versions under this rule are Odoo 18, 19 and 20, so databases on Odoo 17 or older fall outside the standard window. Check your contract for when this applies to you.
The good news: a well-planned upgrade makes daily work in Odoo easier and helps your business grow. Below, we explain how to upgrade your Odoo system safely and without stress.
An Odoo upgrade moves your existing Odoo database from an older version to a newer supported version.
The goal is not to start again. Your existing Odoo environment is upgraded so your business can benefit from newer functionality, security improvements, performance enhancements and the changes introduced in newer Odoo releases.
For customized environments, the process can also involve reviewing and adapting custom modules, third-party applications, integrations, workflows and code so they stay compatible with the target Odoo version.
Odoo’s support policy affects your upgrade because the version you run now decides what you pay. Odoo Enterprise covers the three most recent major versions at the standard price. Older versions remain supported, but cost 25% more per year.
| Odoo version | Status | Support cost |
|---|---|---|
| Odoo 20, 19 and 18 | Covered versions | Standard subscription |
| Odoo 17 and older | Legacy versions | +25% of the annual subscription, every year |
| Odoo Online (SaaS) | Upgraded by Odoo | No legacy surcharge |
Hosting matters too. Odoo.sh only hosts each version for a limited lifespan, so very old versions cannot stay on Odoo.sh indefinitely. For plan prices, see our Odoo pricing guide.
Running an older Odoo version slowly widens the gap between your ERP and the platform’s latest capabilities. Upgrading keeps your Odoo environment current and gives your teams the improvements of each new release.
Each major release improves apps such as CRM, Sales, Accounting, Inventory, Purchase, Manufacturing, Point of Sale, eCommerce, Projects, HR and Helpdesk. Odoo 20 also expands AI and automation across business workflows.
Covered versions get bug fixes, security updates and Odoo support at the standard price, without the 25% legacy surcharge.
New Odoo versions bring performance improvements and redesigned workflows that make everyday operations easier for users.
An upgrade is the right moment to review old customizations, obsolete modules and integrations you no longer need, instead of carrying them forward.
Older ERP versions get harder to connect with new apps, APIs, payment services and third-party modules. A current Odoo is easier to integrate and maintain.
Upgrading regularly is cheaper than jumping several versions at once, and it keeps you clear of the yearly 25% surcharge on legacy versions.
You should consider an Odoo version upgrade when your current environment starts to limit the business. Common signs include:
Odoo 20, released in September 2026, is the latest major Odoo release. Upgrading to Odoo 20 gives businesses the newest capabilities across the Odoo ecosystem, including developments in AI, automation, accounting, inventory, eCommerce, Point of Sale, website management and business workflows. See what’s new in Odoo 20.
Odoo 20 also introduces the Odoo Light User, a cheaper licence for employees who only need self-service features. Light User pricing is only available on Odoo 20 or later.
But moving to Odoo 20 should not begin with the new features. It should begin with your current system. Before upgrading, review your database, installed apps, custom modules, integrations, hosting and critical business processes to understand what the upgrade requires.
An Odoo upgrade moves your existing database to the target version. It does not create a new, empty ERP. To protect your data, the upgraded database is tested first, confirming that critical records and workflows still work, including:
The production upgrade only happens after the upgraded environment has been properly tested.
Custom modules need special attention during an Odoo upgrade. Changes between Odoo versions can affect the framework, models, fields and views that custom developments depend on, so custom code may need to be reviewed, adapted, cleaned and tested against the target version.
Before carrying a customization forward, Azkatech checks whether it is still needed. If standard Odoo now covers what an old custom module does, removing it reduces technical debt and makes future upgrades easier.
Every business-critical integration should be validated against the target Odoo version, so compatibility issues show up during testing, not after go-live. Depending on your setup, this includes:
Learn more about our Odoo integration services.
There are two ways to upgrade Odoo. You can use Odoo’s own upgrade platform, which converts your database to the new version, or work with an Odoo partner, who also prepares, tests and supports the upgrade around your business. The basic steps are the same; what changes is who does the work.
| Step | Odoo upgrade platform | With an Odoo partner |
|---|---|---|
| Preparation | You prepare and submit your database. | The partner reviews the database, custom code and integrations first. |
| Test database | You restore and check the upgraded test copy yourself. | The partner validates workflows, reports and apps with your team. |
| Fixing issues | Odoo fixes technical upgrade errors in standard modules. | The partner also fixes functional issues, custom modules and integrations. |
| Go-live | You request the final upgrade and switch over. | The partner plans the cutover, backups and timing to limit downtime. |
| After the upgrade | Support for upgrade-related errors only. | Ongoing support, user guidance and monitoring. |
Six steps that take your Odoo from its current version to a tested, stable new release.
We review your Odoo version, hosting, apps, database, customizations, third-party modules, integrations and business-critical workflows to define the real scope.
We choose the target release based on your environment, business needs, custom developments and compatibility, including planning the move to Odoo 20.
Each custom module and integration is checked and given a decision: keep, update, rebuild, replace or remove. The aim is a cleaner ERP, not a copy of the old one.
The upgrade runs first on a staging copy, away from your live system, so technical and functional issues are found before cutover.
A converted database is not the same as a business ready to go live. Your key workflows are tested end to end before the production upgrade.
The cutover plan covers the live database, backups, deployment, user access, integrations and the right upgrade window, often outside business hours.
An upgrade affects the people and processes behind Sales, Accounting, Inventory, Procurement, Manufacturing, CRM, Projects, eCommerce and HR. We look at it from both the technical and the business side.
Customizations should solve real business needs, not make your ERP hard to maintain. Where standard Odoo now does the job, we replace old custom code, which makes future upgrades simpler.
We support the full upgrade lifecycle: environment assessment, compatibility review, testing, production deployment, training and post-upgrade support.
Azkatech covers implementation, customization, development, integration, upgrades, training and ongoing support, so you manage Odoo as a long-term platform, not a one-off project.
No. An Odoo version upgrade migrates your existing database to the target version. The upgraded database is tested before production to confirm that business-critical data and workflows are intact.
No. An Odoo upgrade does not wipe or rebuild your system. It converts your existing database and code to a newer version, and your current system keeps running until the tested cutover.
Not automatically in every case. Custom modules may need code changes to stay compatible with the target Odoo version, so each one should be reviewed and tested as part of the upgrade.
Not always. Third-party modules need separate compatibility checks and updates. Whether a compatible version exists depends on the module and its developer.
Yes. Odoo recommends requesting and testing an upgraded copy of your database before the production upgrade. Testing is especially important for databases with custom modules and integrations.
It depends on your environment. A mostly standard Odoo database can be upgraded in days, while one with many custom modules and integrations can take weeks. Version gap, database complexity, workflows and hosting all affect the timeline.
The cost depends on scope. A standard database needs far less work than one with extensive custom development, third-party modules, integrations and complex workflows. Upgrading regularly is usually cheaper than skipping several versions.
It applies if you run Odoo Enterprise on Odoo.sh or On-Premise with a version older than the three most recent releases. Odoo Online customers are upgraded by Odoo and do not pay it. Check your contract for the exact terms.
Yes. An older Odoo database can be upgraded to Odoo 20, but the right path depends on your current version and environment. A larger version gap generally needs more preparation and testing.
Only partly. Odoo’s standard upgrade service converts the database components it covers. Custom modules outside Odoo’s maintenance services usually need separate development work.
Only briefly. Most preparation and testing happens before the cutover. The production database is unavailable during the final upgrade, so the cutover is planned around your operations, often outside business hours.
Not necessarily. The decision should weigh your current version, support costs, required features, customizations, integrations and business priorities. Staying within the three covered versions avoids the legacy surcharge.
Odoo 20 is the latest major Odoo version. It was released in September 2026.
