Odoo 19 → Odoo 20

Upgrading from Odoo 19 to Odoo 20

A single version is a short hop, but not a no-op. Here's what actually changes, how long v19 stays supported, and what a realistic estimate for your specific setup looks like.

Get your instant estimate

v19

v20

1 version Supported The whole jump is handled in a single cutover.

From our projects

Our six current Enterprise projects take Odoo 16 and 17 to Odoo 19 — exactly where this upgrade starts. Track record ›

The case for upgrading now

v19 is supported — the cheapest time to move is while the gap is one release

Odoo officially supports its three most recent major versions. With v20 as the current release, that window covers v18, v19, and v20, and v19 stays inside it until Odoo 22 ships. There's no deadline forcing this one — but a single-release jump is the smallest an upgrade ever gets, and every release you skip adds to the next one.

It also keeps you on the release where Odoo's own development and the wider community's attention are now focused.

What actually changes between v19 and v20

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

One major release means one year 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 current, a single version of feature development — including v20's continued push into AI-assisted features — becomes available the moment you land on v20, 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 that one version 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 v19 → v20 jump

The three that come up on every v19 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. ›

Yes — it's a single major version, so there's nothing in between to pass through. On the managed upgrade path (typically Enterprise), Odoo's own upgrade service handles the jump in one pass. On Community-to-Community upgrades, the migration scripts still have to account for that release's schema and API changes, which is why even a one-version jump is scoped work rather than a button press.

Yes. Odoo supports its three most recent major versions, which currently means v18, v19, and v20. v19 stays inside that window until Odoo 22 ships, so the 25% legacy-version surcharge on Enterprise contracts doesn't apply to it — moving to v20 now simply keeps your gap at a single release.

It depends far more on how customized your instance is than on the size of the version gap. A single version 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 19 → Odoo 20

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.