How long is each Odoo version supported?

Odoo gives every major version three years of standard support, covering helpdesk, bug fixes and security updates. As of September 2026, Odoo 17.0's standard support is planned to end in September 2026, 18.0's in September 2027 and 19.0's in September 2028.

Is upgrading Odoo free?

For Odoo Enterprise, Odoo states that upgrading to the latest version is free, covering standard apps, Studio customisations while Studio and its subscription are active, and code covered by a maintenance-of-customisations subscription. Upgrading your own or third-party modules, data clean-up and training are not included.

Can I upgrade Odoo Community?

Odoo's upgrade service is part of the Enterprise subscription. Community databases are usually upgraded with the Odoo Community Association's open-source OpenUpgrade project or by a partner, and custom modules still need porting to the new version.

Can I skip versions when upgrading Odoo?

With Odoo's upgrade service you can upgrade from any version to a supported version, for example from 16.0 to 18.0. The last unsupported version can still be used as a target for up to six months after its end of life.

How long does an Odoo upgrade take?

It depends mostly on custom modules and data. A standard database may be upgraded in one test round, while a customised one needs code porting and several test databases. Odoo recommends testing thoroughly and rehearsing the day before the production upgrade.

How to Upgrade Odoo to a New Version

Staying on an old Odoo version feels safe until something breaks and there is no fix, or Odoo Online schedules an upgrade for you. Upgrading is a planned project with a well-defined path: request an upgraded test database, port any custom modules, test it properly, then upgrade production. This guide covers the deadlines, the process for each hosting type, and what Odoo's upgrade service does and does not include, based on Odoo's documentation as of September 2026.

Short answer: each major Odoo version gets three years of standard support. Request an upgraded test database (from the database manager on Odoo Online, a staging branch on Odoo.sh, or the upgrade script on-premise), upgrade your custom modules for the target version, test real workflows, then request the production upgrade at a quiet time. On Enterprise the upgrade of standard apps is free; your own and third-party modules are your or your partner's work.

Which versions are supported, and until when?

Version	Release	End of standard support
Odoo 19.0	September 2025	September 2028 (planned)
Odoo 18.0	October 2024	September 2027 (planned)
Odoo 17.0	November 2023	September 2026 (planned)
Odoo 16.0	October 2022	September 2025
Odoo 15.0	October 2021	October 2024

Source: Odoo standard and extended support. Intermediate SaaS versions (19.1 to 19.4 in 2026) exist only on Odoo Online and are not eligible for extended support. Beyond three years, extended support carries a mandatory extra fee.

If you are on 17.0, standard support is ending now; on 16.0 or older, you are already outside it.

Is the upgrade mandatory?

It depends on hosting (Odoo upgrade documentation):

Hosting	Rule
Odoo Online	Major versions must be upgraded every two years; intermediate versions a few weeks after the next is released. Odoo runs a silent test upgrade and, if you don't act, upgrades automatically at the deadline.
Odoo.sh	After the three years of standard support, you have two more years to complete the upgrade; you are notified when it is required.
On-premise	You can stay on a version indefinitely, though Odoo does not recommend it.

Not sure which hosting you are on? See Odoo Online vs Odoo.sh vs on-premise.

What an upgrade does not cover

Odoo is explicit that an upgrade is not: downgrading, switching edition (Community to Enterprise), changing hosting type, or migrating from another ERP. Each of those is a separate project.

The upgrade process, step by step

Inventory your customisations. List custom modules, third-party apps, Studio changes and integrations. A database with custom modules cannot be upgraded until each module has a version for the target.
Request an upgraded test database.
- Odoo Online: database manager → Manage → Upgrade, choose the target version, purpose Test.
- Odoo.sh: the upgrade platform upgrades your latest production backup onto a staging branch; each commit restores it and updates your custom modules, so you test code against a clean upgraded copy.
- On-premise: python <(curl -s https://upgrade.odoo.com/upgrade) test -d <db> -t <version>, or the Upgrade page. The script needs outbound TCP 443 and the 32768–60999 port range.
Port custom modules in parallel. Odoo recommends requesting the test database while your developers update the source code.
Test thoroughly. Test databases are neutralised: scheduled actions and outgoing mail are disabled, payment providers and carriers reset. Walk through real flows: a sale to invoice to payment, a purchase to receipt, stock moves, payroll if used, reports, and ZATCA submission in a non-production mode.
Report issues to Odoo from the Support page ("An issue related to my future upgrade"), fix your modules, and request fresh test databases until everything passes.
Rehearse, then upgrade production at a quiet time. The database is unavailable during the upgrade. On Odoo Online you cannot revert once it completes; on Odoo.sh a failed upgrade is reverted automatically and a backup is kept on success.
On-premise only: merge the filestore. Upgraded databases come back without your production filestore; merge it before going live.

Plan your upgrade with the TECFY Odoo team

What Odoo's upgrade service includes

Covered for Enterprise (Online, Odoo.sh, on-premise)	Not covered
Upgrade of all standard apps	Cleaning existing data and configuration
Studio customisations, while Studio is installed and its subscription active	In-house or third-party modules, including those built by Odoo partners, unless under a maintenance contract
Code under a maintenance-of-customisations subscription	Training on the new version

For Community, Odoo's upgrade service is not available: upgrades are typically done with the Odoo Community Association's OpenUpgrade project, which has branches up to 19.0, or by a partner.

After the upgrade: integrations

Anything that talks to Odoo needs checking. If you use the TECFY connector for Salla or Zid:

Update the Odoo version number in the connector's configuration. The version changes which fields the connector writes — from 17.1, for example, the field for returned quantities was renamed — and features such as automatic ZATCA submission appear from 19.3 (why the version matters).
On Odoo.sh or self-hosted, make sure TECFY's addon is installed for the new version, like any third-party module, then run Check Only to confirm its fields are in place.
Place a test order end to end before switching automation back on.

Getting help

An upgrade touches everything your team relies on, so it helps to have engineers who have done it before. TECFY's Odoo support team is a dedicated team working on your instance; the Full Time package includes version upgrade planning and execution. We start with a system review of your version, edition and customisations so the scope is honest before anything moves. Budgeting a new implementation instead? See Odoo implementation prices in Saudi Arabia.