Should You Upgrade to Odoo 20 on Release Day? The Timeline That Actually Works

Every September the same question lands in ERP inboxes: the new Odoo is out, should we move now? The answer almost never depends on the new version. It depends on the one you are running today, which is where a planned Odoo migration starts.

This Odoo 20 upgrade guide separates the dates Odoo publishes from the excitement around a launch. You will finish it knowing whether your business has a real deadline, a soft preference, or no reason to move at all.

When is Odoo 20 released, and what is confirmed so far?

Odoo 20 is released at Odoo Experience 2026, held at Brussels Expo from September 24 to 26, 2026. Odoo confirms the dates and the venue on its official Odoo Experience 2026 event page.

That is the announcement date, not the date your business can safely run it. A launch keynote tells you a version exists. It does not tell you that your custom code, your apps, or your hosting are ready for it.

One detail is worth more than any feature list. Odoo 20 does not yet appear anywhere on Odoo's own supported versions table, which currently tops out at Odoo 19.0 and the SaaS 19.x releases.

Anything you read about Odoo 20's features before the keynote comes from roadmap previews. Roadmaps signal direction, and items can shift or drop before release, so treat them as intent rather than specification.

Should you upgrade to Odoo 20 on release day?

No, upgrading to Odoo 20 on release day is the wrong call for almost every business already running Odoo. Three practical reasons drive that, and none of them are about the quality of the release.

First, custom modules do not port themselves. Every major version changes framework APIs, and your bespoke code has to be updated and retested before it will run at all.

Second, the wider ecosystem lags a launch. Third-party and community-maintained apps are published by their own maintainers, and a version 20 branch usually appears weeks or months after the release, not on the day.

Third, a production upgrade is a one way door. Odoo's upgrade documentation is blunt about it: "Once the process is completed, it is impossible to revert to the previous version."

There is one honest exception. If you are starting a brand new Odoo implementation with a go live date well after Odoo 20 stabilizes, building directly on 20 avoids an unnecessary second migration later.

Framed as Odoo 19 vs Odoo 20, this looks like a feature contest with a winner. Framed around your own support dates, it becomes a scheduling decision with a much clearer answer.

The better question is not whether Odoo 20 is good. It is whether anything on your calendar actually forces you to move.

What does Odoo's support policy actually give you?

Odoo gives every major version three years of standard support, then a paid extended support window that is narrower than most teams assume. The distinction decides how much time you really have.

Odoo's standard and extended support policy states that standard support "includes helpdesk support, bug fixing, and security updates." That is the only stage where security patches arrive at no extra cost.

Beyond those three years, the same policy states extended support "is subject to a mandatory additional fee and includes helpdesk support and bug fixes (depending on feasibility)." Security updates are not in that list.

Read that carefully, because it is the sentence that should set your deadline. Paying for extended support keeps a version serviceable, not patched.

Odoo marks the 17, 18, and 19 dates as planned, so confirm them before you schedule a cutover. Our Odoo version support timeline tracks every version and what each date means in practice.

If you are on Odoo 17, that September 2026 row is your actual news story this month, not the Brussels keynote.

What is the six month upgrade target rule?

Odoo only lets you upgrade to supported versions, and gives an expired version a six month grace period as an upgrade target. This is the least discussed date in the entire lifecycle, and it catches teams out.

The support policy puts it plainly: "You can upgrade from any version to supported versions only. The last unsupported version can still be used as an upgrade target for up to six months following its end-of-life date."

In practice that means your upgrade destination has a shelf life, not just your current version. Plan a move to a target that is about to expire and the path can close while you are still testing.

It also quietly rewards deciding early. A version chosen and started now is a version still supported when you go live, which is the whole point of the exercise.

Ready to know which target your database can still reach? Request a callback and we will map it against your current version.

Does Odoo 20 remove XML-RPC?

No, Odoo 20 does not remove the XML-RPC and JSON-RPC external APIs, despite a widely repeated claim that it does. If you have integrations built on those endpoints, this is worth getting right before it drives a decision.

Odoo's external RPC API documentation states that the XML-RPC and JSON-RPC APIs at the /xmlrpc, /xmlrpc/2 and /jsonrpc endpoints "are scheduled for removal in Odoo 22 (fall 2028) and Online 21.1 (winter 2027)."

They are deprecated as of Odoo 19, and the replacement is the External JSON-2 API, which authenticates with a bearer token instead of a session. Deprecated means plan the move, not drop everything.

The same documentation adds a carve out that saves a lot of unnecessary work: "The other controllers @route(type='jsonrpc') (known until Odoo 18 as type='json') are not subject to this deprecation notice."

So the honest advice is neither panic nor complacency. Start migrating external integrations to JSON-2 on your own schedule, and do not let a mistaken 2026 deadline dictate your upgrade timing.

Which Odoo 20 upgrade path applies to your hosting?

Your hosting decides how much control you have over upgrade timing, so check it before you check your version. The same Odoo release behaves very differently across the three deployment types.

Odoo Online users have the least to decide. Odoo notifies you ahead of a mandatory upgrade and, in its own words, "an automatic upgrade to the next version will be triggered if no action is taken before the specified due date."

Odoo.sh and on-premise teams own the calendar, which is a benefit and a trap. Nobody forces the date, so the date slips, and the version gap widens until the upgrade becomes a project instead of a task.

Knowing your path tells you how urgent this is. What you check next tells you how big it will be.

What should you check before you upgrade to Odoo 20?

A short pre-upgrade audit tells you whether Odoo 20 is a routine step or a rebuild, and it takes days rather than weeks. Run these checks before you commit to any date.

• Confirm your PostgreSQL version. Odoo 19's requirements state supported versions are "13.0 or above", and the minimum moved up from 12 to 13 at version 19.

• Confirm your Python version. The same documentation states "Odoo requires Python 3.10 or later to run."

• Check the database extension for AI features. Odoo notes the pg-vector extension "is available only for PostgreSQL version 15 and up", so AI capability can raise your database floor.

• Inventory every module you run, split into standard, third-party, and custom, with version numbers against each.

• Check each third-party module for a target version branch, and identify who maintains it. An abandoned app is a rebuild, not an upgrade.

• Document every integration: payments, shipping, marketplaces, banking, and any external API client your team wrote.

• Clean your data before you move it. Duplicates and orphaned records cost time in every test cycle you run.

Most upgrade budgets are decided by items four and five, not by the version number. That is also where an honest estimate comes from, and it is why Odoo customization history matters more than release notes.

What does a realistic Odoo 20 upgrade timeline look like?

A safe upgrade follows Odoo's documented sequence, and the testing loop is what stretches the calendar. Odoo publishes the process, so there is no need to invent one.

The documented flow starts with requesting an upgraded test database, then upgrading your custom module source code, then testing the result before anything touches production. Our complete Odoo migration guide covers each stage in depth.

Odoo recommends repeating that loop rather than testing once. Its guidance is to "frequently request another upgraded test database to ensure that the upgrade process is still successful", and to fully rehearse the process the day before you upgrade production.

Only then do you request the production upgrade, which makes the database unavailable while it runs. Because there is no revert, that rehearsal is the safety net, so treat it as mandatory rather than thorough.

Put those pieces together and a sensible answer emerges. Decide your target version now, audit now, and schedule the production cutover for a window well past the launch, once your modules and apps have caught up.

How iVentureTeam helps with your Odoo 20 upgrade

We tell you which version to target and when to move, then run the upgrade against that plan rather than against the release calendar. Sometimes our answer is to wait, and we say so.

We start with the audit above: version, hosting, database and Python versions, module inventory, and integration map. That produces a written scope and a downtime window before anyone touches your system.

From there our senior Odoo developers team refactors custom modules for the target framework, checks third-party apps for a compatible branch, and rebuilds what has been abandoned upstream.

After go live, our Odoo maintenance services keep you inside the supported window, so the next upgrade is a scheduled task rather than an emergency. That is the pattern that keeps the six month rule from ever becoming your problem.

Odoo upgrade in practice: custom modules moved without losing a record

Custom code, not the core database, is what usually decides an upgrade timeline. A version migration we ran for an IT consultancy shows what that looks like when it is planned properly.

Codequarters, a consultancy specializing in ERP, CRM, and MRP applications, needed its custom Odoo modules moved to the latest Odoo version. We ran the work as two parallel migration tracks, refactoring module code and migrating the database schema.

The outcome was one unified codebase on the latest version, 100% of custom module functionality preserved after the upgrade, and zero records lost during the schema migration. The system runs current and supported, with nothing rebuilt from scratch.

The bottom line on upgrading to Odoo 20

Odoo 20 arriving in Brussels on September 24 is news, not a deadline. The dates that should move you are your own version's end of standard support, the six month window on upgrade targets, and the point at which your third-party apps are ready.

If you run Odoo 17, act on the September 2026 support date now and target a version that will still be supported when you finish. If you run Odoo 18 or 19 on a stable system, you can plan calmly and move once. Either way, decide from your database, not from a keynote.

Ready to plan your Odoo 20 upgrade window?

Get a written target version, scope, and downtime window based on your actual modules and hosting. Book a free Odoo upgrade assessment, call +91-93270-18076, or email business@iventureteam.com.