Odoo 17 → Odoo 19

Upgrading from Odoo 17 to Odoo 19

Two major versions is a short hop, but not a no-op. Here's what actually changes, why staying on v17 is quietly getting more expensive, and what a realistic estimate for your specific setup looks like.

Get your instant estimate

The case for upgrading now

v17 is supported today — that changes when Odoo 20 ships

Odoo officially supports its three most recent major versions. With v19 as the current release, that window covers v17, v18, and v19. When Odoo 20 arrives the window moves to v18–v20, and v17 drops out of it — along with the security patches and fixes that come with being inside it.

It's also a chance to reconnect with a much larger, more active developer community — today's codebase draws far more attention than v17's does at this point.

What actually changes between v17 and v19

Frontend framework

Odoo's web client has continued moving further onto the OWL (Odoo Web Library) framework, replacing the older legacy JS widget system. Custom modules with frontend code written against the old system typically need real rework, not just a compatibility shim.

Python & PostgreSQL requirements

Minimum supported Python and PostgreSQL versions have moved forward across this range. If you're self-hosted, the infrastructure upgrade is a separate, parallel project from the Odoo upgrade itself — worth scoping before the migration, not discovered during it.

Module and API changes

Two major releases means two years of deprecated fields, renamed models, and shifted ORM conventions to account for. This is the bulk of the actual migration-script work for any custom module — not a single breaking change, but an accumulation of smaller ones.

New capabilities you'd gain

Beyond staying supported, two versions of feature development — deeper automation, expanded AI-assisted tooling in v19, and refinements across manufacturing, inventory, and the website builder — become available the moment you land on v19, not something you have to opt into separately.

Community or Enterprise changes the path

Same version gap, two very different projects. Which edition you land on decides whether Odoo's own upgrade service carries the jump, or your migration scripts do.

CE→CE

No managed path to lean on

Staying on Community means there is no managed upgrade service to lean on — every schema and API change across those two versions gets handled by custom migration scripts written specifically for your database. That is real, scoped engineering work, and it is the main reason a large Community-to-Community gap costs more than the same version gap on a managed Enterprise path.

Cost scales with the gap

CE→EE

The managed path absorbs the gap

If you're moving to Enterprise as part of this upgrade, Odoo's own managed upgrade path absorbs most of that version-by-version cost — which is often what makes a CE to EE move at this stage worth evaluating on its own merits, independent of the version jump itself.

Mostly flat, whatever the gap

Already on Enterprise? Then neither penalty applies — an EE to EE jump is the cleanest route there is, and your estimate reflects that.

Before you ask us

Questions about the v17 → v19 jump

The three that come up on every v17 call. Answered here so you don't have to book one to get them.

Something specific to your instance?Ask a human — no form gate. ›

You don't need to manually pass through each version one at a time. On the managed upgrade path (typically Enterprise), Odoo's own upgrade service handles the full jump in one pass. On Community-to-Community upgrades, the migration scripts still have to account for every version's schema and API changes along the way, which is why the effort scales with the size of the gap even though the end result is a single cutover.

Yes, for now. Odoo supports its three most recent major versions, which currently means v17, v18, and v19. Once Odoo 20 ships that window becomes v18–v20, and v17 falls outside it — at which point the 25% legacy-version surcharge on Enterprise contracts becomes relevant too.

It depends far more on how customized your instance is than on the size of the version gap. Two major versions of schema drift is predictable work; thirty bespoke modules is not. The instant estimate gives you a range in under two minutes, and the free technical review confirms it.

Odoo 17 → Odoo 19

See what yours actually costs

No code or database upload. A real range in under two minutes.

Get your estimate Our full process ›

2 minto your range Zerouploads No callto see a number

What happens after you click

Answer four short steps

Version, edition, complexity, apps. Under two minutes.

Get a range immediately

Generated from your answers, on screen, no waiting.

Free review confirms it

We look at the real thing within 24 to 72 hours, then lock the price.