Skip to Content

How Often Should You Upgrade Odoo? Online vs Odoo.sh vs On-Premise (and Our 2-Year Rule)

Odoo Online, Odoo.sh and on-premise have different upgrade rules. Here is what is mandatory, what is risky, and why we recommend upgrading every two years.
November 16, 2026 by
How Often Should You Upgrade Odoo? Online vs Odoo.sh vs On-Premise (and Our 2-Year Rule)
Sales Team

Every Odoo version is supported for three years, but how often you actually have to upgrade depends on where your database is hosted. Here is how the rules work on Odoo Online, Odoo.sh and on-premise, and why we recommend upgrading every two years no matter where you host.

Why upgrading Odoo matters

Odoo describes an upgrade as moving a database from an older version to a newer supported one, for example from Odoo 17.0 to Odoo 20.0. Odoo calls regular upgrades crucial because each version brings:

  • New features: Odoo 20 alone adds AI agents that can create and update records, offline mode, tax-included/excluded switching on orders and invoices, and Basiq open banking for Australian bank feeds.
  • Bug fixes in the apps you already use every day.
  • Security patches. Odoo only provides security updates while a version is in standard support.

There is also a cost side: the smaller the gap between versions, the easier (and cheaper) the upgrade. Custom modules, Studio changes and integrations need less rework when you move one or two versions instead of four.

How long is each Odoo version supported?

Odoo supports each major version (17.0, 18.0, 19.0, 20.0…) in two phases:

  • Standard support: the first three years after release, on Odoo Online, Odoo.sh and on-premise. It includes security updates, bug fixes and helpdesk support.
  • Extended support: starts after standard support, costs an extra fee, and is only available on Odoo.sh (for a limited number of versions) and on-premise. It includes no security updates, and bug fixes are only provided where technically feasible.
VersionReleasedEnd of standard support
Odoo 20.0September 2026September 2029 (planned)
Odoo 19.1–19.4 (Online only)Jan–Jul 2026Replaced by the next release
Odoo 19.0September 2025September 2028 (planned)
Odoo 18.0October 2024September 2027 (planned)
Odoo 17.0November 2023September 2026 (ended)
Odoo 16.0October 2022September 2025 (ended)

Source: Odoo's standard and extended support page, October 2026.

Upgrade rules by hosting type

Odoo Online (SaaS): upgrade every version

  • On a major version (e.g. 19.0 or 20.0), an upgrade is mandatory every two years.
  • On a minor (SaaS) version (e.g. 19.3 or 19.4), an upgrade is mandatory a few weeks after the next version is released. Minor versions come out roughly every two months.
  • Odoo Online uses a rolling release process with automatic upgrades.

In practice, Odoo Online customers upgrade with almost every release. That's good news for features, but it means you need a quick testing routine and custom work that is built to survive frequent upgrades.

Odoo.sh: at least every three years

Odoo.sh databases get three years of standard support. After that, Odoo gives you another two years to complete the upgrade, and you'll be notified when it's required. Some versions can get paid extended support in that window, but without security updates. Our advice: treat three years as your hard limit, not five.

On-premise: no forced upgrade, but no security after three years

Self-hosted databases can stay on the same version indefinitely. Odoo says plainly that this is not recommended. After three years your version stops getting security updates, extended support costs extra, and every year you wait makes the eventual upgrade bigger. Like Odoo.sh, plan on upgrading at least every three years.

HostingOdoo's ruleOur recommendation
Odoo OnlineMinor versions: weeks after the next release. Majors: every 2 years.Take every release; test each one.
Odoo.sh3 years standard support + 2 years to finish the upgradeEvery 2 years (never more than 3)
On-premiseNever forced; security updates stop after 3 yearsEvery 2 years (never more than 3)

Why we recommend upgrading every two years

Odoo releases a new major version roughly every year. Upgrading every two years means you never skip more than one version, and you are always well inside the three-year support window:

  • Always supported: you never run a version that has lost its security updates.
  • Smaller jumps, lower cost: a 18→20 jump is far easier than 16→20. Fewer models, fields and views have changed under your customisations.
  • Time to test properly: you choose when to upgrade instead of racing a deadline.
  • Integrations stay current: Odoo has deprecated its XML-RPC and JSON-RPC APIs. The db service was removed in Odoo 20, and the common and object services are scheduled for removal in Odoo 22 (fall 2028). Connectors need moving to the new JSON-2 API, and a two-year rhythm gives you time to do it.
  • Your team keeps up: smaller changes are easier to train on than a big-bang interface change.

What does an upgrade cost?

With an Odoo Enterprise subscription, Odoo upgrades the standard apps for free, including support to fix issues in the upgraded database. That also covers Studio customisations (as long as Studio is installed and the subscription is active) and custom code under a maintenance-of-customisations subscription.

Odoo's upgrade service does not cover in-house or third-party custom modules without a maintenance contract, cleaning up old data and configuration, or training your team. That's where an Odoo partner comes in. Also note that an upgrade can't switch editions (Community to Enterprise), change your hosting type, or migrate you from another ERP.

How the upgrade process works

  1. Request an upgraded test database (from the Odoo Online database manager, your Odoo.sh project, or the Upgrade page / command line on-premise).
  2. Upgrade any custom modules to the target version, in parallel.
  3. Test thoroughly: everyday flows, reports, website, mail templates, integrations and automated actions. Test databases are neutralised: scheduled actions, outgoing mail, real payments and bank sync are turned off. See our Odoo upgrade testing checklist.
  4. Report any issues to Odoo and fix them before going live.
  5. Upgrade production at a quiet time. The database is unavailable during the upgrade and you can't roll back afterwards.

Frequently asked questions

Can I skip versions?

Yes. You can upgrade from any version to any major version that is still in standard support (or left it less than six months ago). For example, Odoo 17 can go straight to Odoo 20. The bigger the jump, the more testing you'll need.

Is Odoo 17 still supported?

Odoo 17.0's standard support ended in September 2026, so it no longer gets security updates. Read Odoo 20 vs Odoo 17.

Can I go back if something breaks?

No. Once a production upgrade is done, you can't revert to the previous version. This is why testing on an upgraded copy first is essential.

Plan your next Odoo upgrade with MoonSun

We request and test your upgraded database, upgrade your custom modules and connectors, and run the production upgrade for you, at a fixed price.

MoonSun is an Odoo partner in Australia with consultants in Melbourne and Sydney. See our Odoo upgrade service or contact us for a fixed-price upgrade quote.

More in this series

Sources: Odoo 20.0 documentation: Upgrade, Standard and extended support, External JSON-2 API.

How Often Should You Upgrade Odoo? Online vs Odoo.sh vs On-Premise (and Our 2-Year Rule)
Sales Team November 16, 2026
Share this post
Archive
Odoo Upgrade Testing Checklist: What to Check Before Upgrading Production
Received "Database ready for testing" from Odoo? Here is exactly what to test before you upgrade your live database.