Odoo Updates · Support policy

Odoo 17 is out of standard support: what it means and what to do

Odoo 17 reached the end of its three years of standard support in September 2026, the month Odoo 20 shipped. Here is what that changes on each hosting type and for Community users, what staying costs, and how to choose between 18, 19 and 20.

By Octagotech Team9 min readUpdated

Key takeaways

  • Odoo gives every major version three years of standard support. For 17, that ended in September 2026.
  • Extended support is a paid bridge: bug fixes where feasible, and security updates are listed only under standard support.
  • Odoo Online forces the upgrade, Odoo.sh gives two more years, on-premise lets you stay.
  • For most 17 databases, 19 is the landing we recommend. 18 buys about a year.
  • From 17, the custom module work centers on the Odoo 18 renames.

Odoo gives every major version three years of standard support. For Odoo 17, released in November 2023, that ended in September 2026, the month Odoo 20 shipped. If your database still runs 17, nothing stops working today. What changes is who fixes it when something breaks, what it costs to stay, and how far you will have to jump later.

This post sets out what Odoo's policy says, what it means on each hosting type and for Community users, the risks of staying, and the three upgrade targets open to you. It assumes you know Odoo. For the code-level detail of the jump, our guide to upgrading custom modules from 16 to 19 covers every change from 17 onward.

Odoo's support policy: three years of standard support

Odoo releases one major version a year. Its documentation page on standard and extended support states the policy in two parts. Every major version gets three years of standard support, which includes helpdesk support, bug fixing and security updates. After those three years, extended support is available for a mandatory additional fee, and it covers helpdesk support and bug fixes, depending on feasibility. Odoo lists security updates only under standard support.

The support table on the same page gives Odoo 17 a planned end of standard support in September 2026. When we checked it on September 25, 2026, the table had not yet added Odoo 20. With one major release a year, three years of standard support works out to roughly the three most recent versions, and the covered versions in the Enterprise Subscription Agreement follow the same logic: the three most recently released major versions, now 18, 19 and 20. The table plans the end of standard support for 18 in September 2027 and for 19 in September 2028.

Read extended support as a paid bridge. It keeps a helpdesk and, where feasible, bug fixes available while you plan the upgrade. Security updates are not on its list, and the agreement sets out what it costs to stay.

Enterprise customers: watch the six-month mark. The Enterprise Subscription Agreement (version 13, dated September 24, 2026) states that the customer agrees to pay an extra fee when a database is on a version older than the covered versions: charged once per year, no earlier than six months after a new major version is released. With Odoo 20 released in September 2026, that could apply to a 17 database from around March 2027. Check the terms of your own subscription. Community users have no subscription and are not affected.

What it means on Odoo Online, Odoo.sh and on-premise

Odoo's upgrade documentation treats the three hosting types differently, and the difference decides how much time you have.

On Odoo Online, the decision is mostly made for you. A database on a major version has to be upgraded every two years. Odoo notifies you in the database a few weeks before a mandatory upgrade, runs a silent test upgrade first, and triggers the upgrade automatically if nobody acts by the due date. The support table offers no extended support on Odoo Online: every major version older than 17 is marked not supported there, so expect none for 17. Odoo Online does not run custom modules, so the work is testing your configuration and briefing your users.

On Odoo.sh, the documentation gives you another two years after the initial three years of support to complete the upgrade, and Odoo notifies you when an upgrade is required. The table shows versions 14 to 16 on Odoo.sh under extended support, with its mandatory fee, so expect 17 to follow the same pattern once the table is updated. Odoo.sh is also the easiest place to rehearse. It sends your latest daily production backup to the upgrade platform, restores the result on a staging branch, and updates your custom modules on every commit you push.

On-premise, the documentation says you can stay on the same version indefinitely, even if it is not recommended. Enterprise customers keep their subscription, but the agreement still applies. Security advisories are written for the covered versions, and if you report a bug on an older version, Odoo may ask you to upgrade to a covered version as the remedy. The table lists paid extended support for every version older than 17 on-premise.

If you run Odoo 17 Community

Community users never had a support contract with Odoo, so on paper the end of standard support changes less. In practice it changes one important thing. Community has always benefited from the fixes Odoo publishes for supported versions. Odoo's disclosure process sends security advisories and corrections to Enterprise customers first and publishes them after a delay. Odoo lists security updates only under standard support, which has ended for 17, so plan on that basis rather than on fixes continuing to appear.

The second thing to watch is the OCA. Modules from the Odoo Community Association are ported to each new version by contributors, module by module, so availability on your target version varies. Check every OCA module you run for a branch on the version you are aiming at before you set a date. The same goes for the upgrade tool. Odoo's upgrade platform asks for an Enterprise subscription code, so Community databases usually move with the OCA's OpenUpgrade project, which migrates one version at a time. Update: OpenUpgrade opened its 20.0 branch on September 28, 2026, but module coverage for 20 will take time to build. For now, 17 to 19 is two runs, and 17 to 20 would be three.

If you are weighing a move to Enterprise at the same time, read how the switch from Community to Enterprise works, including the order of operations when it comes with a version upgrade.

The risks of staying on 17

Some companies stay on a version outside standard support on purpose, and for a short, planned period that can be reasonable. The risks grow with time, and they are worth naming.

The first is fixes. Outside standard support, bug fixes come through extended support, for a fee and depending on feasibility, and the agreement lets Odoo answer a bug with a request to upgrade. Security issues found from now on are the bigger exposure, because Odoo lists security updates only under standard support.

The second is everything around Odoo. Marketplace vendors and OCA contributors put their effort into the versions people are moving to, so apps and modules for 17 will see fewer updates, and new ones will target the versions still in standard support. An app that has no release for your target version is one more thing to replace during the upgrade.

The third is the size of the next move. From 17 today, the jump to 19 crosses two releases. A year from now, the next major release will end standard support for 18 as well, the sensible target will be further away, and your custom code will have another year of API changes to absorb. Our guide to what an Odoo upgrade costs explains why the version gap and the amount of custom code drive the number.

Your options: 18, 19 or 20

Odoo's support page says you can upgrade to supported versions only. As of September 30, 2026, Odoo's upgrade platform offered 17, 18 and 19 as targets, and 20 was not yet selectable, so from a 17 database the targets open today are 18 and 19. Check whether 20 has been added before you set a date. Here is how we weigh the three, in line with the version matrix on our Odoo upgrade and migration page.

TargetReleases crossedStandard supportOur view
Odoo 181Planned to end September 2027The smallest step, but 18 is now the oldest supported version and leaves standard support at the next major release. You would be planning the next upgrade within a year.
Odoo 192Planned to end September 2028The landing we recommend for most 17 databases, with two years of standard support ahead. Plan the move to 20 for 2027.
Odoo 203Not in Odoo's table when we checked; three years from its release under the stated policyThe newest release. Unless a version 20 feature is critical to you, move once the first rounds of fixes have landed.

Going straight to 19 does not mean two cutovers. Odoo's upgrade service moves an Enterprise database from an older version to a newer supported one in a single request, and the documentation's own example is 16.0 to 18.0. Your custom modules are rewritten once, for 19, though we apply the changes in version order so nothing is skipped. For scale, SF Dyes moved from Odoo 13 to 18 in one migration, with every custom module rewritten, barcode scanning and custom vendor reports added, and zero disruption at go-live.

What changes for custom modules from 17 onward

If you came to 17 from an older version, you have already paid for the largest view-layer change of recent years, the removal of attrs and states from views. The jump from 17 carries fewer sweeping changes, but a few of them touch almost every module.

In 18, list views are declared with a <list> root element instead of <tree>, and window actions use list in view_mode. The field attribute that sets how a column totals in grouped views, group_operator, became aggregator. And the storable product type was folded into goods with an is_storable flag, so a check against the old product type quietly stops matching. That last one is the dangerous kind: no error, just logic that no longer runs.

For 19, the fastest way to build the list is to install each module on a clean 19 database with tests enabled and read the server log. Our guide to custom modules from 16 to 19 shows the old and new code side by side; skip its Odoo 17 sections if you are already there.

Be clear about what Odoo's upgrade service does not do. Its documentation says a database with custom modules cannot be upgraded until a version of those modules exists for the target version, and that making a customization compatible is the job of whoever maintains it. The service covers the standard apps, Studio customizations while Studio is installed and subscribed, and code under a maintenance of customizations subscription.

A short plan for leaving 17

This is the sequence we follow, compressed. Each step maps to a stage of our upgrade method, and each has exit criteria that are met before the next one starts.

  1. Confirm where you stand. Version, edition, hosting type and subscription. On Odoo Online or Odoo.sh, look for an upgrade notice and its due date.
  2. Inventory everything that is not standard. Custom modules, OCA modules, marketplace apps and Studio changes, each marked keep, replace with standard, or retire, and each checked for a release on the target version.
  3. Run a test upgrade on a copy. Request an upgraded test database, or run OpenUpgrade for Community, and rewrite the modules in parallel, as Odoo's documentation recommends.
  4. Test by role. Business flows end to end, every report a customer or vendor checks, integrations, automated actions and data exports. Odoo neutralizes test databases, so scheduled actions and outgoing mail are off while you test.
  5. Rehearse, then cut over. Run the full upgrade again on a fresh production copy, reconcile it and time it. Then run the new version beside live and cut over in a quiet window.

We audit your modules before we quote, and the price is fixed before kickoff. Any change after that is scoped, quoted and approved before it is built.

Frequently asked questions

When did Odoo 17 support end?

Odoo gives every major version three years of standard support, and its support table lists September 2026 as the planned end for Odoo 17, the month Odoo 20 was released. After that, paid extended support covers helpdesk and bug fixes where feasible; Odoo lists security updates only under standard support.

Can we keep running Odoo 17?

On-premise, yes: Odoo's documentation says you can stay on a version indefinitely, though it does not recommend it. On Odoo.sh you get two more years after the three years of support to complete the upgrade. On Odoo Online, major versions must be upgraded every two years, and Odoo triggers the upgrade itself if nobody acts by the due date.

Should we upgrade from Odoo 17 to 18, 19 or 20?

For most databases, 19. Standard support for 18 is planned to end in September 2027, so it buys about a year. Odoo 20 is the newest release; unless a version 20 feature matters to your business, wait for the first rounds of fixes to land before moving production.

Does upgrading from Odoo 17 mean rewriting our custom modules?

Some of them. Odoo's upgrade service converts the database and standard apps, not your own modules. From 17, the main changes arrive in 18: tree views became list, group_operator became aggregator, and storable products moved to an is_storable flag. The server log on 19 lists the rest.

Octagotech Team

Certified Odoo Ready partner · San Francisco, New York, Ahmedabad and Rajkot

Our engineering team in Ahmedabad audits and rewrites custom modules for upgrades from any Odoo version, and a named project manager in New York plans the cutover with you. About Octagotech, Odoo Ready partner.

Still on Odoo 17?

Bring your version, hosting and module list, and in 30 minutes we will tell you what the move to 19 touches.

Book a discovery call

Find out what leaving Odoo 17 will take

The first call takes 30 minutes.

Or email sales@octagotech.com