Odoo 13 → Odoo 20

Upgrading from Odoo 13 to Odoo 20

Seven major versions is a real gap, not a minor bump. Here's what actually changes, why staying on v13 is quietly getting more expensive, and what a realistic estimate for your specific setup looks like.

Get your instant estimate

v13

v14

v15

v16

v17

v18

v19

v20

7 versions Past end of life Every version in between is handled in a single cutover.

From our projects

We have upgraded multiple Odoo 13 Enterprise databases to Odoo 15 Enterprise, and are currently taking six Odoo 16 and 17 Enterprise databases to Odoo 19 — the same v16→v19 ground your upgrade crosses, one release short of v20. Track record ›

The case for upgrading now

v13 has a clear reason to upgrade now

Odoo officially supports its three most recent major versions. With v20 released in September 2026 as the current release, that window now covers v18, v19, and v20. Moving v13 into that window takes you out of the 25% legacy-version surcharge Odoo introduced on Enterprise contracts in 2026 — an easy saving on your next renewal, on top of current security patches and everything new in the platform since.

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

What actually changes between v13 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

Seven major releases means seven 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, seven versions of feature development — deeper automation, AI-assisted tooling that v20 pushes further, and refinements across manufacturing, inventory, and the website builder — become 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 those seven 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 v13 → v20 jump

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

Odoo officially supports only its 3 most recent major versions. As of the current release cycle, that window no longer includes v13, and Odoo's 2026 policy update introduced a 25% legacy-version surcharge on Enterprise contracts for versions outside that window — v13 falls into that surcharge zone.

It depends far more on how customized your instance is than on the size of the version gap. Seven 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 13 → 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.