Odoo Version Support in Australia: How Long Each Version Lasts and When to Plan Your Upgrade

Odoo supports its three most recent major versions, and a new major version arrives roughly once a year. That simple policy has a hard edge to it. When Odoo 20 is unveiled at Odoo Experience this September, Odoo 17 drops out of the supported window. If you’re running v17 or anything older, the next few months are your chance to plan the move on your own schedule instead of someone else’s.

This post explains how Odoo version support works, which versions are supported right now, and how Australian businesses should time an upgrade around it.

How Odoo version support works

Odoo’s policy is published in its supported versions documentation: the three most recent major versions receive support, bug fixing and security updates. Because a new major version ships each year, that works out to roughly three years of coverage per version.

A few details matter in practice:

• The policy applies across hosting types. Whether you run Odoo Online, Odoo.sh or on-premise, the same three-version window applies to major releases.
• Odoo Online also gets intermediary releases. Databases on Odoo’s own cloud receive smaller updates between major versions. Odoo.sh and on-premise installations only move between major versions.
• Support means more than bug fixes. A supported version gets security patches and access to Odoo’s helpdesk. An unsupported one gets neither.

You can always upgrade from any version, however old. Support ending doesn’t strand you; it just means the clock is running.

Which Odoo versions are supported in 2026

As of August 2026, the supported versions are Odoo 17 (released late 2023), Odoo 18 (released October 2024) and Odoo 19 (released September 2025).

The next change is already on the calendar. Odoo Experience 2026 runs from 24 to 26 September in Brussels, and Odoo 20 will be unveiled there. On Odoo’s usual pattern, once v20 ships, v17 leaves the supported window.

That gives v17 users a clear deadline. It also gives v18 users a preview of their own: v18 becomes the oldest supported version from October, which puts it next in line when v21 arrives in 2027. We covered what’s expected in the new release in our Odoo v20 roadmap post.

What happens when your version leaves support

Nothing breaks on day one. Your database keeps running exactly as it did. What changes is what sits behind it:

• No more bug fixes. Issues you hit stay unfixed unless you pay someone to patch them locally.
• No more security updates. For a system holding your customer data, invoices and payroll records, this is the risk that matters most. It compounds quietly the longer you wait.
• No helpdesk. Odoo’s support team works on supported versions.

Odoo does offer a paid extended support option for businesses that need more time on an older version. It’s a bridge, not a destination, and it costs money that could otherwise fund the upgrade itself.

The better news is that the upgrade itself is free for Enterprise subscribers. Odoo’s upgrade service converts your database to the new version at no charge, and you can request test upgrades before committing to anything.

The businesses that struggle are never the ones that upgrade a year late. They’re the ones still on v14 with no test upgrade, no budget line and a server nobody wants to touch. Book the test upgrade early and the rest is routine.

Bill Alvarez, Practice Manager, Auboros

When Australian businesses should schedule the move

Upgrade appetite is high across the market. MYOB’s Mid-Market Survey 2025 found 36% of Australian mid-sized businesses looking to upgrade their ERP. The harder question is timing, and Capterra’s Australian research is a useful caution: fewer than 1 in 3 Australian businesses successfully adopt new software. Rushed cutovers are a big part of why.

Our advice for timing an Odoo upgrade in Australia:

• Cut over just after a BAS quarter closes. A fresh quarter on the new version keeps GST reporting clean and gives your bookkeeper one system per BAS, not two.
• Avoid the EOFY crunch. June and July are the worst months to change systems. Finance teams are closing the year and finalising STP; they don’t need a new interface as well.
• Start test upgrades 2 to 3 months out. Standard databases upgrade quickly. Customisations, integrations and third-party modules are where the work hides, and each needs testing against the new version before production moves.
• Budget partner time for customisations, not for the upgrade itself. The database conversion is free. Adapting custom code and retesting integrations is where a partner earns their keep.

The process itself, including what the free upgrade service covers step by step, is in our guide to how Odoo version upgrades work. If you’d rather have it handled end to end, that’s what our Odoo upgrade service exists for, alongside our broader Odoo consulting work for Australian businesses.

Running an Odoo version that’s about to leave support?

We’re a Brisbane-based Odoo Silver Partner, and version upgrades are routine work for us: test upgrade first, customisations adapted, production moved when the timing suits your BAS cycle. If you want to know exactly what an upgrade from your version involves, book a free consultation. Twenty minutes will tell you whether it’s a quick job or a project.