Three things changed without much notice: Enterprise now charges a 25 % surcharge on old versions, standard support expires every September, and the e-invoicing modules that European mandates require simply do not exist in older releases. Check your own case below — every claim links to its source.
Sources verified 16/09/2026
By hand: open Odoo, go to Settings and scroll to the bottom of the page — you will see something like "Odoo 15.0". A trailing e means Enterprise.
The surcharge applies to Enterprise only. Community has no surcharge — but no security patches or assisted upgrade path once out of support either.
Odoo supports each major version for three years, and you can only upgrade towards supported versions. Older releases cannot be hosted on Odoo Online, which means anyone still on them is on-premise or Odoo.sh — the most customised deployments, and the most expensive to move.
| Version | Released | End of standard support | Odoo Online | Enterprise surcharge |
|---|---|---|---|---|
| Odoo 19 | Sep 2025 | Sep 2028 (expected) | Yes | No |
| Odoo 18 | Oct 2024 | Sep 2027 (expected) | Yes | No |
| Odoo 17 | Nov 2023 | Sep 2026 (expected) | Yes | Likely from around April 2027 |
| Odoo 16 | Oct 2022 | Sep 2025 — passed | No | Yes, already running |
| Odoo 15 | Oct 2021 | Oct 2024 — passed | No | Yes, already running |
| Odoo 14 and older | — | Passed | No | Yes, already running |
Source: Odoo's official standard and extended support documentation · verified 16/09/2026
The Enterprise agreement only covers the three most recent major versions — today, 17, 18 and 19. Below that:
"…if the Customer's database is on a version older than the Covered Versions, the Customer agrees to pay an extra fee equal to 25% of the annualized price." Reviewed once a year, and those charges can rise by up to 7 % annually. For v16 and older it has been running since April 2026; v17 databases enter surcharge territory once Odoo 20 ships.
Source: Odoo Enterprise Subscription Agreement · verified 16/09/2026
Odoo does not backport its e-invoicing modules to older releases. If your version predates the one that introduced the module, it is not a matter of configuration: it does not exist — and you can verify that branch by branch in the public repository.
| Country and obligation | Module | Exists from | Legal date |
|---|---|---|---|
| Belgium — structured B2B invoicing over Peppol | account_peppol | v16 | In force since 1/1/2026 · fines of €1,500 to €5,000 |
| Poland — KSeF | l10n_pl_edi | v18 | In force since Feb–Apr 2026 |
| France — receiving through a certified PDP | l10n_fr_pdp | v17 | 1/9/2026 |
| Germany — B2B e-invoice issuing | account_edi_ubl_cii | v14 | 1/1/2027 (>€800k) · 2028 for all |
| Spain — Veri*Factu | l10n_es_edi_verifactu | v17 | 1/1/2027 companies · 1/7/2027 the rest |
| United States — no federal B2B mandate | — | — | Not applicable |
Two exceptions worth knowing in Spain: companies filing under SII are outside the Veri*Factu obligation, and the Basque provinces run TicketBAI instead. In the US the drivers are the surcharge, security patching and integration drift — not regulation.
Source: module presence checked branch by branch in github.com/odoo/odoo · legal dates from each national authority · verified 16/09/2026
With an active Enterprise subscription, Odoo converts your database for free. It is worth reading what the agreement puts back on you:
"It is the responsibility of the Customer to verify and validate the upgraded database… to analyze the impact of changes… and to convert and adapt… any third-party extensions." Validating the upgraded database, analysing the impact of the target version's changes, and adapting third-party extensions. Custom modules are only covered if you pay a monthly fee per 100 lines of code.
What is free is the conversion. Validation, impact analysis, your own code and the cutover plan — the part that decides whether a migration goes well or badly — sit outside the contract.
Source: Enterprise Subscription Agreement — Upgrade Services · verified 16/09/2026
Jesús Ramoneda
Systems architect, Barcelona. Working with Odoo since 2017 across functional consulting and technical development, with five major migrations delivered — including v12 to v16/v18 jumps on Community and Enterprise, custom code in the middle. If you want a second opinion on your own case, email me your version and I will tell you what I see.