Odoo 20: Six Things Worth Knowing

The new Odoo version ships this September. We've picked the six things with a real operational impact — two of them have a hard deadline, and they apply even to businesses with no upgrade planned.
Confirmed by OdooOn the roadmapPrediction only

Each section is marked with how certain it is. "Confirmed" means official Odoo documentation or Odoo's own pages. "On the roadmap" means the April 2026 partner presentation. "Prediction" is not a promise — do not build a budget on it. Sources are listed at the end.

01

Confirmed by Odoo

Odoo 20 ships at the conference itself, 24–26 September 2026

Odoo ships one major version a year and always unveils it at Odoo Experience in Brussels. This year it runs 24–26 September, and the official event page confirms attendees will see "the latest version of Odoo, which will be released during the event".

That means two things. Nobody knows the final feature list until then — everything we know about version 20 today comes from the April partner presentation. And the date is close enough that preparing now is worth it.

Odoo Experience 2026

24–26 / 09 / 2026

Brussels Expo, Belgium

The new version is released during the event itself. Until then, nobody has the final feature list.

Source1 Odoo — event page

02

On the roadmap

Release day is not upgrade day

This is the most common misconception about new versions. After the conference release it takes roughly two to four weeks before the version is generally available. The first stabilising patches arrive another four to eight weeks after that. And the upgrade scripts for more complex databases only settle after three to four months.

The .0 of any ERP is not where you want your invoicing and your warehouse to live. The sensible window for a production cutover is Q1–Q2 2027.

September 2026

Release

Unveiled at Odoo Experience in Brussels.

October–November

Availability

Downloadable and on Odoo.sh. Fine for a test database.

Q4 2026

First patches

The earliest sensible date — and only for simple installations.

Q1–Q2 2027

Recommended window

Scripts have settled, third-party modules have caught up.

The conference dates are confirmed. The availability estimates are based on how the Odoo 17, 18 and 19 releases actually played out.

Source6 WAO Group8 VTI

03

Confirmed by Odoo

Your integrations will break

The reason is simple: Odoo is retiring the old XML-RPC and JSON-RPC interfaces. They are marked deprecated in Odoo 19, they already disappeared from Odoo Online in 19.1, and in Odoo 20 they go on Odoo.sh and on-premise too. The replacement is the new JSON-2 API — different address, different format, different authentication.

In practice, anything that talks to Odoo from the outside stops working. This is not an optional upgrade you can defer along with the rest — the integrations need rewriting before you even start on the migration itself.

Going away

/xmlrpc/2 · /jsonrpc

Replaced by

POST /json/2/<model>/<method>

Authentication via an API key in the Authorization header — no more username and password over HTTP. Regular users' keys expire after 90 days.

What you have connectedWhat happensWhat to do
E-shop or ordering portalOrder and stock sync stopsCheck JSON-2 support with your connector vendor
Warehouse scanning appReceipts and deliveries stop postingRewrite the calls, test against a production clone
Power BI or Excel feedReports come back emptyMove to JSON-2, or read from the database directly
Banking integrationStatements stop downloadingTreat as priority — it hits your close
Automations in n8n, Zapier or MakeScenarios start failing silentlyReview every scenario, add error alerting

Source2 Odoo — JSON-2 docs4 Odoo — JSON-2 talk

04

Confirmed by Odoo

Odoo 17 reaches end of life that same day

Odoo supports the three most recent major versions. The moment version 20 ships, the window shifts to 18 / 19 / 20 — and Odoo 17 falls out of it. From then on there are no security patches and no bug fixes.

If you are on 17, September 2026 is your deadline for a decision: either move quickly to 19 now, or plan a single jump straight to 20 in 2027. The second option is calmer, but it means a few months without support.

20232024202520262027202820292030todayOdoo 17supportedends when Odoo 20 shipsOdoo 18supportedOdoo 19supportedOdoo 20supported
Odoo 17Decide before September 2026
Odoo 18No pressure, move during 2027
Odoo 19The most comfortable position
Odoo 20For new implementations from late 2026

no fixes

Side note: extended support

Odoo offers paid extended support for anyone who wants to stay on an older version longer. It is narrower in scope than standard support, and it costs money. It is a postponement, not a solution.

Source3 Odoo — supported versions

05

Prediction only

Large deployments may get a read-replica database

Today your Odoo has one PostgreSQL database doing everything. Every barcode scan and every "export the whole year" report hits the same server. Most of the time that is fine — it stops being fine when month-end close collides with a warehouse shift and one heavy report slows everybody down.

Read replicas split that work up. The primary database keeps all the writes; alongside it run copies into which PostgreSQL continuously streams the changes, and those serve the reads: dashboards, reports, analytics. The heavy report then runs off to the side and holds nobody up.

How it works

Todayone database for everythingOperationsorders, stock, POSReportingdashboards, analytics, BIOdoo application serversPostgreSQLwrites + reads + reportsWRITE + READOne heavy report slows everybody downWith read replicaswrites separated from readsOperationsorders, stock, POSReportingdashboards, analytics, BIOdoo application serversPostgreSQLprimary — writes onlyWRITEReplica 1read-onlyReplica 2read-onlycontinuous replicationlag: a fraction of a secondThe report runs aside — operations never feel it

On the left, today — one database serving both writes and heavy reads. On the right, the split: a primary for writes, replicas for reporting, with continuous replication between them. A replica is always a fraction of a second behind — irrelevant for a dashboard, not irrelevant for a "has that payment landed?" screen.

10,000+

concurrent users the architecture is meant to handle

today the quoted figure is in the low thousands

Treat that number with caution

The sources disagree. Some partner write-ups list read replicas among Odoo 20's technical changes; others file them explicitly as unconfirmed, and one source says outright that the 10,000 figure is an informed forecast rather than a statement from Odoo. This is something to watch at the conference — not a line in a budget. Worth adding: PostgreSQL streaming replication is standard technology and can be deployed for reporting workloads today, independently of Odoo 20.

Source6 WAO Group7 Much Consulting8 VTI

06

On the roadmap

AI stops advising and starts acting

Odoo 19 gave you an "Ask AI" box that answers and suggests. The version 20 roadmap aims somewhere else: at agents that perform concrete actions inside your data — find every unwon opportunity belonging to a given rep and reassign them, work through bank reconciliation and report anomalies, read a specification PDF and build a project from it with stages and tasks.

AreaOdoo 19 todayOdoo 20 roadmap
CRMYou reassign opportunities by handAn agent finds and reassigns them by your criteria
AccountingA person checks bank reconciliationAn audit agent reviews statements and reports anomalies
ProjectsYou create the project manuallyThe AI reads a spec PDF and builds stages and tasks
TimesheetsYou enter lines by handAn assistant proposes them from real activity

Decide these before you switch it on

An assistant that drafts a paragraph can afford to be wrong occasionally. An agent that reassigns opportunities on its own, or touches accounting, needs three things settled: who may run it, what it may change without approval, and how you would notice it got something wrong. And build training around "how to override it", not just "how to use it". Accountability for a wrong document still sits with a person, not a model.

Source5 Aktiv Software7 Much Consulting

07

On the roadmap

Payroll loses an entire step

Attendance and time off currently reach payroll through an intermediate step called work entries. That step disappears in Odoo 20 — the data flows straight into the payslip. Alongside it comes a dashboard that shows what is blocking a pay run: a missing contract, bank account or ID number.

It is a small thing, but it repeats every month. Instead of hunting for why a payslip would not generate, you get a list of what needs filling in.

Today

Attendance and time off

Work entriesstep removed

Payslip

In Odoo 20

Attendance and time off

Payslip

A dashboard shows what is blocking the pay run, up front

Source5 Aktiv Software6 WAO Group

ProLight & Sound 2024