Odoo 17 is out of standard support: what changes if you run it

September 2026 brought two pieces of news for anyone running Odoo, and they pull in opposite directions. Odoo released version 20 at Odoo Experience, in Brussels. In the same month, version 17 left standard support.

If you are on 17, you look at the new release and think about jumping straight to it. Today you can’t, and the reason is less obvious than it seems. But first, the support rule, because it changed.

How Odoo handles each version today

A lot of people still have the old rule in their heads. Odoo used to support the last three major versions. Today the official documentation talks about time: each version gets three years of standard support from its release date. After that comes extended support, which is billed separately.

Since Odoo ships one major version a year, there are always three versions under standard support. With 20 on the market, those are 18, 19 and 20. Version 17, released in November 2023, dropped out in September.

Version	Release	End of standard support
20	September 2026	September 2029 (expected)
19	September 2025	September 2028 (expected)
18	October 2024	September 2027 (expected)
17	November 2023	September 2026

What changes depends on where your Odoo runs

The end of standard support weighs differently on each hosting option, according to Odoo’s upgrade page:

• Odoo Online, Odoo’s own SaaS: upgrading is mandatory every two years. Staying put is not an option.
• Odoo.sh: after the three years of standard support, Odoo gives you two more years to complete the upgrade, with extended support billed during that window.
• On-premise: you can stay on the version indefinitely. The price is having no fixes and no support from Odoo, unless you pay for extended support.

And then there is the contract. Section 5.1 of the Enterprise agreement sets an extra fee of 25% of the annualized price for customers on a version older than the three most recent ones, charged from six months after each new release. With 20 out, anyone who stays on 17 with Enterprise falls under this rule.

Why you cannot jump to 20 yet

Version 20 is out, but the roads leading to it are still under construction.

Converting a database from one version to the next is the job of migration scripts, and they don’t ship on release day. They take weeks, because the conversion of hundreds of modules has to be ported and tested. You can see this today on both paths:

• on Odoo’s official upgrade service, the form offers 19, 18 and 17 as targets. Version 20 is not there yet;
• on OpenUpgrade, the OCA community project that plays this role for Odoo Community users, the 20.0 branch was created at the end of September and work has just started.

Every new version goes through this. For anyone on 17 today, though, 20 will have to wait.

In Brazil there is one more layer

If you issue invoices through Odoo in Brazil, the target version doesn’t depend on Odoo alone. It depends on the Brazilian fiscal localization, which also has to be ported version by version, with its own scripts. Porting it to 20 has already started, with KMEE opening most of the migration pull requests, but it is still under review and not ready for production. That is the subject of the next post: why Odoo 18 is the safe migration target in Brazil today.

What I would do if I were on 17

No panic over “out of support”: your database won’t stop working tomorrow. But I would start planning now, because a good migration is the one that happens before it becomes urgent.

I would start with an inventory of what runs in your Odoo beyond the standard modules: OCA community modules, third-party modules, custom modules, and how much was built in Studio. That inventory defines the migration effort, far more than the source version does. With the inventory in hand, you pick the target by looking at the localization, not just at the latest release. If you are on 17, the choice is between 18 now and 20 later, which KMEE is already porting. The criteria are in the next post.

If you want, KMEE runs this inventory in a free migration assessment: we map the four layers of your system and hand back a plan with a clear scope.