Odoo 17 reached the end of its standard support in September 2026. If your company still runs it, nothing stops tomorrow, but protection and options now shrink over time. This article explains what end of support means according to Odoo's official documentation, your upgrade options, and a practical plan to upgrade without surprises.
What end of standard support means
According to Odoo's standard and extended support page:
- Each major version gets three years of standard support from its release, on Odoo Online, Odoo.sh and on-premise.
- Security updates are provided during standard support only.
- Extended support follows for an additional fee, on Odoo.sh for a limited number of versions and on-premise for any version, with helpdesk support and bug fixes where technically feasible.
Odoo 17.0 was released in November 2023 and its standard support ended in September 2026. In practice: no new security updates for 17, and future changes in external or regulatory requirements will not reach this version through standard support.
Which version to upgrade to
The documentation says upgrades should target a major version still under standard support, or one whose standard support ended less than six months ago. Current options:
| Version | Released | End of standard support |
|---|---|---|
| Odoo 18.0 | October 2024 | September 2027 (planned) |
| Odoo 19.0 | September 2025 | September 2028 (planned) |
| Odoo 20.0 | September 2026 | September 2029 (planned) |
Moving to 18 leaves less than a year before the same decision returns, so most companies look at Odoo 19 or the current Odoo 20 and decide after reviewing their customizations and add-ons. See Odoo 19 features and our Odoo 20 guide.
What Odoo's upgrade service covers, and what it does not
According to the upgrade documentation, upgrading a database is included with Odoo Enterprise and covers:
- all standard applications;
- customizations made with Studio, as long as Studio is installed and the subscription active;
- developments covered by a maintenance of customizations subscription.
It does not cover:
- additional modules created in-house or by third parties, including Odoo partners, unless under a maintenance contract;
- cleaning existing data and configuration;
- training on the new version.
These exclusions are where the real effort lies: the more custom and third-party modules you have, the more upgrade and testing work is needed.
A five-stage upgrade plan
1. Inventory customizations and integrations
- List every custom and third-party module, who owns the code, and whether a version exists for the target release.
- List integrations: payment providers, online stores, POS systems and the Fatoora connection.
- Identify what can be dropped because the new version now covers it as standard.
Deliverable: a customization register marking each item as upgrade, rebuild or retire.
2. Test upgrade
Request an upgraded test copy through the Upgrade page, the database manager or Odoo.sh, depending on hosting. The documentation notes that test databases are neutralized: scheduled actions, outgoing mail, payment providers, carriers and bank synchronization are disabled.
Deliverable: a test database on the new version and a list of issues.
3. Testing and acceptance
- Check views, reports, templates, filters and exports.
- Run a full flow: purchase, receipt, sale, delivery, invoice, payment.
- Reconcile the trial balance, stock levels and receivables between both versions.
- Test each invoice, credit note and debit note type against the Fatoora test environment before production. See ZATCA Phase 2.
Deliverable: acceptance sign-off from process owners in finance, inventory and sales.
4. Production upgrade
The documentation states that the database is unavailable from the moment the upgrade is requested until it finishes, that it is impossible to revert to the previous version afterwards, and recommends rehearsing the day before. Choose a low-usage window away from month-end closing and keep a backup.
Deliverable: production running on the new version, with a written contingency plan.
5. Training and hypercare
Train users on changed screens and procedures, and follow up closely during the first weeks.
Common mistakes
- Starting without an inventory of custom modules.
- Testing isolated screens instead of a full business flow.
- Scheduling the production upgrade near month-end or a tax filing date.
- Leaving third-party integrations until go-live day.
FAQ
Will Odoo 17 stop working?
The documentation does not say an on-premise system stops, but security updates end, and support is only available through paid extended support where offered.
Can we go straight from 17 to 20?
The documentation allows upgrading to any major version still under standard support. The test upgrade and the state of your customizations decide the right path.
How long does an upgrade take?
It depends on data volume, customizations and integrations, and cannot be estimated before the inventory and test upgrade.
Next step
Maham Pro, an official Odoo partner at Ready Partner level, helps with the customization inventory, test upgrade, testing and go-live as part of our Odoo service. Packages are on the pricing page, and you can book a free 30-minute introductory session to discuss your system.
Sources: Standard and extended support, Upgrade documentation. Reviewed November 2026.