Decide how often to upgrade Odoo.

This guide helps you decide how often to upgrade Odoo to a new major version, and what each choice commits you to. The short answer: Odoo releases one major version a year and gives each three years of standard support, so a database has to move at least every two to three years to stay supported, and on Odoo Online that deadline is enforced. If your database has little or no custom code, upgrading every year, a few months after each release, keeps every upgrade small. Custom code makes each upgrade more expensive, which is the main reason to upgrade less often.

It is written for owners and operations managers. Odoo's support policy, upgrade documentation and Enterprise Subscription Agreement were checked on odoo.com on 27 October 2026; website behaviour was checked in the Odoo 19 and 20 source code.

Before you start

• Your version: the About section at the bottom of the Settings app shows it, for example "Odoo 19.0".
• Your hosting: Odoo Online (Odoo's shared cloud), Odoo.sh (Odoo's cloud platform for databases with custom code) or on-premise (your own server). Each has different upgrade rules.
• Your edition: Odoo's documentation describes its upgrade service as included with Odoo Enterprise, the paid edition. The free Community edition is outside that service.
• A list of what differs from standard: custom modules, changes made with Studio (Odoo's tool for adding fields and screens without code), third-party apps, and website pages edited in the website builder.
• Terms: a major version is the yearly release, such as 19.0, available on all hosting. A SaaS version, such as 19.4, is an interim release available only on Odoo Online. Standard support is the period in which Odoo provides bug fixes and security updates for a version. An upgrade moves a database to a newer major version.

How long each version is supported

As of 27 October 2026, Odoo's support page lists these dates:

• Odoo 17.0, released November 2023: standard support ended in September 2026.
• Odoo 18.0, released October 2024: planned to end in September 2027.
• Odoo 19.0, released September 2025: planned to end in September 2028.
• Odoo 20.0, released September 2026: planned to end in September 2029.

After that comes extended support, for an additional fee, on Odoo.sh for a limited number of versions and on-premise for any version. It keeps helpdesk support and bug fixes where technically feasible, but security updates stop when standard support ends.

The Enterprise Subscription Agreement (version 13, dated 24 September 2026) adds a cost to waiting. It covers the three most recent major versions. Once a year, and no earlier than six months after a new major release, a database on an older version is charged an extra fee of 25% of the annualized subscription price. Odoo's upgrade platform can move a database from any version to any major version still in standard support, or one that left it less than six months ago.

What your hosting decides for you

• Odoo Online: a database on a major version must be upgraded every two years. A database on a SaaS version must be upgraded a few weeks after the next one is released, and SaaS versions arrive every two to three months. Odoo sends a notice a few weeks before the deadline, and if you take no action, the upgrade runs automatically.
• Odoo.sh: after a version's three years of support, you have two more years to complete the upgrade.
• On-premise: Odoo's documentation says you can stay on a version indefinitely, although it does not recommend it, and that a smaller version gap should make the upgrade easier.

Yearly or every other version: what changes

You do not have to stop at every version on the way. What grows with the gap is the amount of change your users and any custom code must absorb at once. Every upgrade, whatever its size, needs the same steps: request an upgraded test database, test your daily processes in it, fix what broke, retrain users, and schedule the switch, during which the live database is unavailable.

• Every year: more upgrade projects, but each covers one year of changes to screens, features and data.
• Every second version: half the projects, each covering two years of change. On Odoo Online, a database on a major version cannot wait longer than this.
• Waiting for the end of support: on Enterprise, the 25% fee applies once you fall outside the three covered versions, and once standard support ends you no longer receive security updates.

Custom code changes the arithmetic. A database with custom modules cannot be upgraded until those modules have a version for the target release. Odoo's upgrade service converts the standard apps, and Studio customizations as long as Studio is still installed and its subscription active. Custom modules are converted only if you pay Odoo's maintenance fee, charged monthly per 100 lines of code, and Odoo may charge for missing months of coverage when you request the upgrade. Otherwise, adapting them falls to you or your developer. In every case, checking the upgraded database is your responsibility under the agreement.

Recommendation: with little or no custom code, upgrade every year, a few months after the release, so each upgrade stays small and you can test outside your busy season. With many custom modules, consider every second version, because each upgrade means adapting every module again, and fewer upgrades mean fewer rounds of that work. Either way, stay inside your hosting's deadline.

Website pages edited in the website builder

If your website matters to sales, much of the upgrade risk sits in pages you have edited. When you edit a page or template in the website builder, Odoo leaves the standard template untouched and saves a copy specific to your website, with your edits in the copy. In Odoo 19 and 20, when an upgrade updates the standard template, it passes the change on to your copy only for the parts you never changed. The content you edited stays as you saved it, so it does not receive the new version's changes to that template.

Odoo's upgrade documentation adds that a view, the template behind a page or screen, that causes problems during the upgrade is disabled, and that disabled views are listed in the upgrade report. The report arrives with the email for a completed upgrade and appears in the Discuss app for users with access to Settings.

Recommendation: in every test upgrade, open each edited page, not only the home page, and test your forms and checkout. If an edited page breaks, redoing the edit on the new version can be quicker than repairing the old copy.

Check your upgrade plan against this list

• You know your version's end of standard support and, on Odoo Online or Odoo.sh, your upgrade deadline.
• Every custom module has a named person responsible for adapting it, or is covered by Odoo's maintenance fee.
• You have a list of edited website pages to check.
• You have requested an upgraded test database and tested your sales, purchasing, invoicing and website processes in it. Test databases are neutralized, so scheduled actions and outgoing email are switched off.
• You have read the upgrade report for disabled views.
• Go-live falls in a quiet period, and you request a fresh test upgrade shortly before it, since Odoo recommends a full rehearsal the day before.

Steps verified on Odoo 19 and 20. Menus and labels can differ on other versions.

Common questions

How long is each Odoo version supported?

Odoo gives each major version three years of standard support. As of 27 October 2026, Odoo 18.0 is planned to reach the end of standard support in September 2027, Odoo 19.0 in September 2028 and Odoo 20.0 in September 2029.

Do I have to upgrade Odoo every year?

No. On Odoo Online a database on a major version must be upgraded every two years, and on Odoo.sh you have two years after a version's support ends. On-premise you can stay longer, but security updates stop when standard support ends, and an Enterprise database on a version older than the three most recent can be charged an extra 25% fee once a year.

Can I skip Odoo versions when upgrading?

Yes. Odoo's upgrade platform can move a database from any version to any major version still in standard support, or one that left it less than six months ago. A larger jump means more change to test, and custom modules must first be adapted to the target version.

Does an Odoo upgrade keep my website builder edits?

Your edits are kept in a website-specific copy of each template, but the parts you edited do not receive the new version's changes to that template. Views that cause problems during the upgrade are disabled and listed in the upgrade report, so check every edited page in a test upgrade.

Is the Odoo upgrade service free?

With Odoo Enterprise, the upgrade of standard apps and of Studio customizations is included. Custom modules are covered only under Odoo's maintenance fee per 100 lines of code, and cleaning data or training users is not included.