Odoo 17 vs Odoo 18: what changed and is it worth migrating

Every Odoo release ships dozens of changes, but the only question that matters for the business is whether the migration justifies your team's time and the system downtime. In this post we share a practical view of Odoo 18 based on 14 projects our team upgraded in the past six months.

What changed under the hood

Odoo 18 is primarily a performance release. The developers rewrote the ORM cache, optimized report rendering and eliminated several bottlenecks in Web Studio. In our load tests the time to open filtered list views dropped by an average of 23%, and quarterly pivot reports got 40% faster.

• A new batch-operation engine in inventory and accounting models
• Reworked Kanban tile UI with bulk actions
• Improved mobile client with an offline mode for warehouse scenarios
• Native support for Python 3.12 and PostgreSQL 16
• Updated Studio with custom-field refactoring that doesn't require migrations

Who benefits the most from migrating

If your Odoo 17 hits a wall on reports, warehouse documents or daily bulk updates — upgrade. If you've been on 17 for only a few months with minimal customization, it's safe to wait for Odoo 18.2 (the LTS-style release planned for autumn 2026).

Scenarios where migration is mandatory

1. 01You're integrating with a bank or marketplace that requires Python 3.12+
2. 02You run more than 100 concurrent users and get performance complaints
3. 03Your team wants the mobile client in warehouses and stores
4. 04You're rolling out AI agents — Odoo 18 has full JSON-RPC batching

A painless-migration checklist

• Audit every custom module and its compatibility with the v18 ORM
• Run a pre-flight migration on staging using a production database copy
• Regression tests for critical flows (sales-to-cash, procure-to-pay)
• Set up a 30-minute rollback fallback plan
• Train key users 1–2 weeks before the release

The biggest migration risk is organizational, not technical. A team that doesn't see the new version before release will resist the change. We always do a demo for key users two weeks ahead of launch.

What it costs

A typical mid-market migration (50–150 users, 10–20 custom modules) takes 4–6 weeks and lands at €18,000–€35,000 on our side. More than 60% of that time goes to customization audit and regression testing — and that's not where you want to cut corners.