Odoo 20 is released at Odoo Experience 2026. This brief explains what changed, which support deadlines matter, the six-month upgrade window many teams miss, and a practical migration checklist for custom modules, integrations, and data.
Odoo 20 brings AI agents, an MCP server to connect external assistants, a new JSON-2 API replacing XML-RPC, and a refreshed mobile UI called Frost—plan integration and custom-module updates accordingly.
A safe migration follows a staged process: analyze and plan, migrate modules to a test (QC) database, migrate data, run scenario testing, and only then switch the live system.
# What this guide covers
Odoo 20 launched at Odoo Experience 2026 (September 24–26). That launch is important, but the deadline that affects your business is usually the end-of-support date for the version you currently run. This brief explains what changed in Odoo 20, the concrete support dates you need to track, why a six-month window matters, and the practical migration steps to reduce downtime and surprises.
# What's new in Odoo 20
Odoo 20 focuses on faster everyday work through built-in AI and platform changes that affect integrations and custom code.
# Support policy and the real deadlines
Odoo standard support lasts three years per major release. Only the three most recent major versions stay in standard support at any time. Extended support exists but is limited and paid.
If you run Odoo 17, September 2026 is your hard planning date. Waiting for Odoo 20 to "settle" can push you past the supported upgrade path.
# The six-month rule many teams miss
# Migration risks that need planning
Data migration is usually straightforward. The risky elements are custom modules, third-party integrations, and custom screens:
# Practical migration process (staged and test-first)
Follow a tested, repeatable process on a copy of your system before switching production:
# Immediate next steps for teams
Odoo 20 brings a wide set of improvements across AI, Sales, CRM, Inventory, Manufacturing, Accounting, Projects, HR, Website, and POS, focused on stronger automation and tighter integration between apps. Odoo 19 (September 2025) laid the groundwork with a redesigned interface and the first real steps into AI. Moreover,
Drupal 10 reaches end of life on 9 December 2026. Drupal 12 is planned for the same week. Our recommendation for Drupal 10 site owners is to start the Drupal 11 upgrade now instead of building the whole plan around a new release. Release week leaves no room for discovery As of 16 September, the official Drupal release
Originally appeared on The Rails Tech Debt Blog . Heroku sent us an email about the database behind ips.fastruby.io , a small app we run for sharing benchmark-ips results. That database runs Postgres 15, and the email gave it an end-of-life date on Heroku of January 20, 2027. If we do nothing before December 20, 2026,
The database under a hosted Drupal or Backdrop estate has to change generations one day, and that is the day most operators find out what their migration tooling was hiding. On a BOA box the move across Percona generations is a rehearsed road: a readiness check names the one account which would block the whole box, the
Managing Magento 2 storefront data and Odoo ERP operations separately can lead to repeated manual data entry and synchronization work. Odoo Magento 2 Connector connects both platforms to synchronize products, orders, customers, inventory, invoices, and shipments. This guide compares Webkul, VentorTech, Emipro, Odoo IN,
Shopify manages the storefront, while Odoo handles products, inventory, orders, and accounting. Odoo Shopify Connector brings these systems together to reduce duplicate work and keep business data in sync. This guide compares five leading options—Webkul, Emipro, VentorTech, Techspawn, and Odoo IN—across Odoo version su
Loading more related stories...
Open the app view to save this story, compare related coverage, and continue from the same source.