Odoo just shipped its newest major version in front of a packed audience in Brussels — and for the tens of thousands of US businesses still running Odoo 17, that keynote quietly started a countdown clock. If your ERP is still on 17, the question is no longer "should we upgrade eventually," it's "how fast can we get to a supported version before the security patches stop."

What Actually Happened at Odoo Experience 2026

Odoo Experience 2026 ran September 24–26 at Brussels Expo, bringing 400+ talks and the Odoo 20 launch. The event drew 45,000+ attendees from 150+ countries, cementing its status as the largest annual gathering in the ERP world. Odoo 20 was unveiled during the opening keynote on September 24 at 8:30, given by Odoo founder and CEO Fabien Pinckaers.

The headline theme this year is autonomy. According to session previews and Odoo's own teasers, Odoo 20 brings a native Model Context Protocol (MCP) server letting external AI assistants connect directly to Odoo, alongside natural-language database actions and automated document parsing, plus a redesigned interface. Odoo's release engineers are also framing the agentic layer as a shift from reactive to proactive: users will be able to add Skills to their AI Agents in Odoo 20. Beyond AI, expect meaningful updates to accounting, manufacturing, and inventory — MRP and Inventory modules typically receive their most significant improvements on even-numbered releases, which is good news for operations-heavy mid-market firms.

None of that matters, though, if your current version drops out of support before you've planned your move.

The Real Deadline: Odoo 17 Support Is Ending

Here's the mechanic that actually drives urgency, and it has nothing to do with feature envy. Odoo follows a deliberately simple support policy: the three most recent major versions always receive helpdesk support, bug fixes, and security updates — roughly three years of lifecycle per major version, because a new major version appears about once a year and the oldest then drops out of the window.

With Odoo 20 now released, the supported window shifts to 18, 19, and 20. Odoo 17 standard support ends September 2026, and versions 16 and 15 are already on paid extended support. Multiple industry trackers had flagged this well in advance: Odoo 17 was supported, but was expected to drop off the list when Odoo 20 shipped. That prediction has now become reality.

What does losing standard support actually mean day to day? Once a version reaches end of life, there are no more security patches, no bug fixes, and no official support — a clear signal to plan an upgrade. Odoo does offer a grace period, but it's narrow: the last unsupported version can still be used as an upgrade target for up to six months following its end-of-life date. Extended support exists as a paid fallback, but after that it moves to paid extended support, which covers helpdesk and bug fixes but not new security updates. In plain terms: you can keep limping along on Odoo 17, but you'll be paying more for less protection against the next CVE.

Given the US accounts for a huge share of Odoo's global footprint — approximately 60,679 live websites, or 26.45% of all Odoo deployments worldwide — a large slice of that installed base is now facing this exact decision.

Should You Upgrade to 19, or Wait for Odoo 20 to Stabilize?

This is the part where most upgrade advice online gets muddled, so let's separate the two decisions CFOs and IT directors actually need to make.

Decision 1: Get off Odoo 17 (and definitely off 16 or older). This isn't optional anymore. As one industry analysis put it bluntly: if you are on Odoo 17, your standard support window closes this month; if you are on Odoo 16 or older, you are already outside it. In both cases the question is not Odoo 19 versus Odoo 20, it is how fast you can reach a supported version.

Decision 2: Which version should you land on? Here the consensus among Odoo partners is more nuanced, and reasonably consistent:

  • If you're several versions behind, don't leapfrog straight to a brand-new major release. Waiting for Odoo 20 means running unsupported software through a release cycle where third-party modules are unstable, and it stacks two risky changes into one project — Odoo 19 has had a full year of fixes and a mature app ecosystem behind it.
  • Multi-version jumps are technically supported. Multi-version jumps are supported, and Odoo lets you upgrade to supported versions only — a larger jump means more framework changes for your custom modules to cross, so the testing effort grows with the distance.
  • Skipping is often cheaper than upgrading annually. Odoo's official upgrade service handles multi-version jumps in a single migration pass, so a 16-to-19 project is one project, not three, and skipping versions is almost always cheaper than upgrading annually, which is why a 2–3 version jump is the most common migration delivered.

For teams building new automations or data-heavy AI workflows, one architectural note matters: removal of the XML-RPC and JSON-RPC endpoints is scheduled for Odoo 22 in fall 2028, and they are deprecated from Odoo 19, with the JSON-2 API as the replacement. That's a planning detail for your integrations team, not a reason to rush or stall.

What a Migration Actually Costs — and Why "Wait and See" Costs More

Budget is usually the real blocker, so let's be concrete. Most Odoo upgrades cost between $1,500 and $15,000, rising to $30,000 or more for large or heavily customized systems; the database upgrade itself is free on Enterprise, so you pay for the project around your custom code, data, and version jump. The variable that actually moves the number isn't the version name — it's your codebase: Odoo upgrade cost is influenced not only by the target version but also by the technical distance between the existing and target environments, and custom development is often one of the largest variables in an Odoo migration services cost estimate.

Timeline-wise, a clean project is faster than most CFOs expect: a straightforward upgrade with few or no custom modules typically takes 3–6 weeks from kickoff to go-live. Heavily customized, multi-integration environments take longer and cost more — which is exactly why a readiness assessment before you commit to a target version pays for itself. As one upgrade guide summarized the trade-off: waiting has a continuous cost — every month spent working around gaps already fixed in a newer release is avoidable manual work, and upgrading now means a second migration later, but that's a single, plannable project, usually a smaller cost than months of delay.

Don't Let the Countdown Catch You Off Guard

Odoo 20's launch is exciting on paper, but for anyone still running Odoo 17, 16, or earlier, the real story is the support clock that just started ticking. Waiting for "the perfect version" is how businesses end up two releases behind, unpatched, and paying premium rates for an emergency migration instead of a planned one.

Grey Space Computing is an Odoo Ready Partner built for exactly this moment. We run a structured readiness assessment on your current instance — auditing custom modules, integrations, and data health — then map a staged migration path to a supported version, whether that's a direct jump to Odoo 19 or a phased move that lands you safely on Odoo 20 once it matures. Talk to our team about an Odoo ERP implementation or migration plan before your support window closes, not after.