Odoo Updates · Odoo 20

What we know about Odoo 20, and how to prepare your instance now

What we expected from Odoo 20 in June, how that compared with what shipped in September, and a preparation checklist for custom modules, integrations and data that still applies.

By Octagotech Team7 min readUpdated

Key takeaways

  • Odoo 20 was unveiled at Odoo Experience on September 24 to 26, 2026, ahead of the October window we expected in June.
  • Review custom modules before a move to 20: access rules merged into one ir.access model, and Model._table_query was removed.
  • Build new integrations on the JSON-2 API that arrived in Odoo 19; XML-RPC and JSON-RPC are deprecated.
  • AI now has a running cost: Odoo's release notes say every AI feature needs IAP credits.

Update, September 2026: Odoo 20 has now been released. This post reflects what was expected in June 2026; Odoo's release notes have the final list of changes, and Odoo 17 has now left standard support. For what actually shipped, read Odoo 20 is here: what's new and what it means for your business.

Odoo moves fast. When we wrote this post in June 2026, Odoo 19 was current and the community was watching the roadmap for what came next. This post keeps that June view, a practical preparation checklist, and notes on where Odoo's release notes differ from what we expected.

We wrote this before Odoo published a formal Odoo 20 feature list, so it drew on public roadmap items and patterns from prior release cycles. Several of our guesses did not match what shipped, and we say so below. The preparation steps hold regardless.

Release window: what we expected, what happened

In June we expected Odoo to follow its usual pattern: an announcement at Odoo Experience in October 2026, stable releases in late October or November, and a migration window for on-premise teams in the first quarter of 2027. That is not how it went.

Odoo unveiled version 20 at Odoo Experience, held at Brussels Expo from September 24 to 26, 2026, and its release notes list the version as released that month. Both editions shipped: Odoo's download page offers Community and Enterprise builds of 20.

What happened · September 2026 onward

  1. September 24 to 26, 2026Odoo 20 unveiled at Odoo Experience

    Release notes list the version as released in September 2026, in Community and Enterprise.

  2. September 28, 2026OpenUpgrade opens its 20.0 branch

    The OCA's route for Community upgrades starts to build module coverage for 20.

  3. 2027Our advice: plan the move to 20

    Land on 19 first and move to 20 once the first rounds of fixes are in.

For Odoo Online customers, part of the schedule is Odoo's. A database on an online version such as 19.4 has to upgrade a few weeks after the next version is released, so test early. Our Odoo 20 release overview explains the details.

AI and automation: what we expected

In June we expected Odoo 20 to extend AI-assisted features to more touchpoints in core modules. That held. Per Odoo's release notes, as summarized in our release overview, Odoo 20's AI agents can create and update records and be called from automated and scheduled actions, Odoo now acts as an MCP server for outside AI tools, and every AI feature needs IAP credits. Our June list of specific modules that would gain AI features was a guess, and we have removed it.

The practical implication: AI now has a running cost, so decide which AI features you actually want before you budget for 20.

Accounting and manufacturing changes

These two areas tend to get the most substantive changes in each release, because they are where ERP implementations live or die operationally. In June we guessed at tighter multi-jurisdiction tax tooling in accounting and a reworked work center capacity model in manufacturing. Neither is what Odoo's release notes lead with.

What the notes describe instead, as covered in our release overview: in accounting, bill line prediction and a rule that every journal entry touching a bank account must now come from a bank transaction; in manufacturing, continuous production, Kanban and Gantt views for work orders, and side-by-side comparison of bills of materials. If you have custom development in these areas, plan a compatibility review against the 20.0 documentation.

Key takeaway: Odoo's developer changelog is where the breaking changes show up. Between 19.0 and 20, access control lists and record rules merge into one ir.access model, binary fields change type, and Model._table_query is removed. Flag custom modules that touch any of these for compatibility testing.

A meaningful shift in API access

In June we expected a more mature external API layer and guessed it would be REST. That guess was wrong. Odoo's existing XML-RPC and JSON-RPC APIs work, but they expose the ORM layer directly, which means integrations often break when Odoo changes field names or model structures during a major upgrade. Odoo's answer is the JSON-2 API that arrived in Odoo 19. The old endpoints are deprecated: their db service was removed in Odoo 20, and the common and object services are scheduled for removal in Odoo 22, in fall 2028.

This matters most for businesses that have built integrations with e-commerce platforms, logistics systems, or external analytics tools. If your integration was built against XML-RPC or JSON-RPC, now is a good time to audit it and plan a move to the JSON-2 API. Plan for key rotation too, since Odoo's documentation caps API keys at three months.

If you are evaluating Odoo integration work for a new system connection, we would generally recommend building on the JSON-2 API now rather than on XML-RPC.

What to do in your Odoo 19 instance today

Upgrades go badly for predictable reasons: undocumented customizations, integrations nobody fully understands, data quality issues that were easy to ignore in the old version, and workflows that exist in people's heads rather than in documentation. None of those problems is created by the upgrade, but the upgrade forces you to confront them.

Here is what we recommend starting now, regardless of your planned upgrade timing:

Audit your custom modules

Run a full inventory of every module that is not a standard Odoo module. For each one, record: what it does, which Odoo models it extends, whether it has an active maintainer, and when it was last updated. Custom modules that touch core models like account.move, mrp.production, stock.picking, or sale.order deserve the most attention. These are the most likely to require rework.

Document your workflows

Write down how your team uses Odoo today, which may differ from how it was configured at go-live. Upgrades often reset configuration options or move settings to new locations. Teams that have documented their workflows can verify the upgrade result systematically. Teams that have not end up discovering problems in production.

Review deprecated API calls in any custom code

Odoo publishes deprecation notices in their changelog. Go through the Odoo 17, 18, and 19 changelogs and check whether any deprecated methods appear in your custom code. The Odoo migration guide for each version is your primary reference here.

Clean up your data

Duplicate records, orphaned attachments, and stale leads do not cause upgrade failures, but they slow down migrations and bloat your staging environment. Run a data quality pass now. Archive inactive customers, merge duplicate products, and clear out the document inbox backlog. A leaner database is faster to test and easier to validate.

Test your integrations in isolation

For every external system connected to Odoo (your e-commerce store, your 3PL, your accounting sync, your CRM data exports), document the exact API calls being made and what Odoo models they touch. Then set up a test environment and verify each integration still works on an upgraded test copy. Doing this in staging before production cutover is the difference between a smooth migration and a fire drill.


In our experience, the upgrades that go well share a common characteristic: preparation started before there was a migration date. The technical work of upgrading Odoo is manageable. The organizational work (getting everyone aligned, testing edge cases, retraining on changed workflows) takes longer than people expect.

If you are on Odoo 19 and want a second opinion on your upgrade readiness, or if you are considering Odoo for the first time and want to land on a version with a clear upgrade path, book a discovery call with our team. We will tell you where you stand and what, if anything, needs to happen before you move to Odoo 20.

Ready for Odoo 20?

30 minutes on your custom modules, integrations and upgrade readiness.

Book a discovery call

Is your instance ready for Odoo 20?

The first call takes 30 minutes.

Or email sales@octagotech.com