September 2026 support deadline
Odoo’s current support table lists September 2026 as the planned end of standard support for Odoo 17.0. Standard support includes helpdesk assistance, bug fixes and security updates. Organisations using Odoo 17 should decide whether to upgrade before the planned deadline or arrange extended support. (Odoo 19.0 Docs: Administration Standard Extended Support)
The published information identifies the planned end month but does not provide an exact cutoff day. Administrators should confirm the operative date with Odoo rather than assume that coverage will change on the first or last day of September. (Odoo 19.0 Docs: Administration Standard Extended Support) The internal schedule should leave time to obtain that confirmation before an upgrade or support decision is approved.
Coverage after standard support
Odoo lists different coverage for standard and extended support. Standard support covers helpdesk assistance, bug fixes and security updates. Extended support costs an additional fee and covers helpdesk assistance and bug fixes where those fixes are feasible. (Odoo 19.0 Docs: Administration Standard Extended Support)
Security updates are explicitly included under standard support but are not listed in the supplied summary of extended support. Extended-support bug fixes are also qualified by feasibility. (Odoo 19.0 Docs: Administration Standard Extended Support) Before relying on extended support, decision-makers should ask Odoo to confirm the terms that apply to their contract, how feasibility is assessed and whether any limits affect existing issues.
Odoo states that each major version receives three years of support and strongly recommends using a supported version. (Odoo 19.0 Docs: Administration Standard Extended Support; Odoo 19.0 Docs: Administration Upgrade) For organisations still running Odoo 17, the planned deadline requires coordination between the people responsible for contracts, system administration, custom development, integrations and operational downtime.
Begin with an upgraded test database
Odoo’s documented process begins with requesting an upgraded test database. The organisation should then test its business workflows and integrations, resolve identified issues and schedule the production upgrade only after that work is complete. (Odoo 19.0 Docs: Administration Upgrade) Following this order prevents the production upgrade from becoming the first full compatibility test.
Testing should cover the workflows and integrations on which the organisation depends, in line with Odoo’s guidance. (Odoo 19.0 Docs: Administration Upgrade) Each workflow should have an owner who can record the outcome, investigate problems and confirm that corrections have been retested. Creating the test database is only the start of the assessment, not evidence that the upgraded environment is ready for production.
Odoo recommends resolving problems found during testing before scheduling the production upgrade. (Odoo 19.0 Docs: Administration Upgrade) If an issue remains unresolved, its operational effect should be documented before a production date is approved. The organisation can then decide whether to move the date, change the upgrade plan or seek further assistance.
The test record should distinguish between successful checks, failed checks and items that have not been tested. Because Odoo’s process places issue resolution before production scheduling, an incomplete test should not be treated as a successful result. (Odoo 19.0 Docs: Administration Upgrade) This distinction helps decision-makers see which parts of the upgrade are ready and which still require work.
Assess custom modules separately
A customised database has an additional prerequisite. Odoo states that custom modules must be compatible with the target version before the database can be upgraded. (Odoo 19.0 Docs: Administration Upgrade) Administrators should identify each custom module, assign responsibility for it and establish whether a compatible version is available for the intended target release.
Odoo’s documented requirement places custom-module compatibility before submission of a customised database for upgrade. (Odoo 19.0 Docs: Administration Upgrade) Testing standard workflows alone does not establish whether custom code is ready. Each module should have a recorded compatibility status and be included in the upgraded test database so that the workflows affected by it can be checked.
Odoo also calls for integrations to be tested as part of the upgraded database process. (Odoo 19.0 Docs: Administration Upgrade) The assessment should therefore cover both custom modules and connected systems. For each item, administrators should record what must be tested, who can investigate a failure and whether a relevant third party needs to participate during testing or the production upgrade.
Plan for production unavailability
The production database is unavailable during the upgrade, and Odoo recommends scheduling the work for a period of minimal use. (Odoo 19.0 Docs: Administration Upgrade) The plan should identify an acceptable window, the activities that must be completed beforehand and the people who need to know that the live database will be unavailable.
Odoo’s guidance places production scheduling after testing and issue resolution. (Odoo 19.0 Docs: Administration Upgrade) Administrators should preserve that sequence when working back from the planned September 2026 support deadline. Committing to production too early may leave insufficient time to address problems found in workflows, integrations or custom modules without changing the window.
The production plan should not assume that completing the database upgrade is the only scheduling consideration. Odoo confirms that the database will be unavailable during the process and advises choosing a period of minimal use. (Odoo 19.0 Docs: Administration Upgrade) Internal approval should therefore account for the interruption and confirm which business activities need to pause or be completed before the window starts.
Checks before choosing a path
Before approving extended support or an upgrade timetable, confirm the exact standard-support cutoff date, the additional fee for extended support and the coverage available for Odoo 17. Odoo’s published distinction is that standard support includes helpdesk assistance, bug fixes and security updates, while extended support provides helpdesk assistance and feasible bug fixes for an additional fee. (Odoo 19.0 Docs: Administration Standard Extended Support)
For an upgrade, verify that an upgraded test database has been requested, business workflows and integrations have been tested, identified issues have been resolved and custom modules are compatible with the target version. These steps are part of Odoo’s documented upgrade guidance. (Odoo 19.0 Docs: Administration Upgrade) The production window should be approved only when the checks have named owners and recorded outcomes.
Odoo 17 standard support is planned to end in September 2026, and Odoo recommends operating a supported version. (Odoo 19.0 Docs: Administration Standard Extended Support; Odoo 19.0 Docs: Administration Upgrade) Organisations still using Odoo 17 need to choose between completing a tested upgrade before the planned change or obtaining confirmed extended-support terms while upgrade work continues. That decision should reflect the applicable contract, the readiness of workflows and customisations, and the acceptable period of production unavailability.