Odoo version end-of-life calendar

Support status by version

“Planned” end dates move when Odoo ships the next major; always re-check the official matrix before a hard deadline decision.

Does this even apply to Community?

Strictly speaking, no — "end of support" is a policy for Odoo's paid channels (Online, Odoo.sh, Enterprise on-premise). Self-hosted Community never had a support contract, so there's nothing to expire.

In practice, use these dates anyway. They're the best available proxy for when a Community version stops being maintained:

• When a version leaves the three-version window, Odoo stops committing security fixes to that branch on GitHub — the patches self-hosters pull for free stop arriving.
• OCA and vendors track the same window: module branches freeze shortly after.
• The surrounding stack (Python, PostgreSQL, distro packages) ages out on roughly the same rhythm.

So for Community the calendar isn't a contract deadline — it's the date your version starts accumulating risk, and the sensible trigger to plan the jump to a newer version.

What EOL means in practice

• Nothing switches off on that date. Your database keeps running.
• Security fixes stop for that major. New CVEs stay open on the system that holds invoices and customer data.
• Python and PostgreSQL age out on their own schedules — routine server updates start breaking old stacks.
• OCA / community modules freeze on old branches. Bugfixes stop arriving.
• The eventual upgrade grows — every skipped version is another sequential hop later.

Upgrade from your version

Each page has EOL detail, what typically breaks, and a fixed-price band for that hop.