Upgrade Odoo 13 to 17

Is Odoo 13 still supported?

Odoo patches its three most recent major versions. Fall off that list and security fixes stop — your live system still runs, but newly found holes stay open. Full calendar: Odoo version end-of-life calendar.

What breaks between Odoo 13 and 17?

For most companies, the database move is not the hard part. The quote moves mainly on custom JavaScript, website/POS/warehouse changes, accounting overrides, and third-party apps that do not yet support the target version.

Community upgrades run one major version at a time under the hood (OpenUpgrade). A 13 → 17 project is 4 sequential hops. Custom modules, JS/web client code, and third-party connectors are where most of the effort sits — not the raw database size.

Odoo 13 → 14

• Python 3.6 → 3.8 floor; some older OS images no longer work without a stack bump.
• web_enterprise / community web client diverged further — custom JS assets often need rework.
• Mail / discuss refactors and chatter field moves that break custom views.

Odoo 14 → 15

• Assets bundling (assets_backend / web.assets_*) replaces many old JS/CSS includes.
• Early OWL adoption in core — custom client actions and widgets start breaking.
• Accounting localization and tax report structure changes in several countries.

Odoo 15 → 16

• OWL 2 and a much larger share of the web client rewritten — custom JS/POS/website widgets are the usual pain point.
• View architecture and many XML attrs deprecated or renamed.
• Studio / custom fields and report QWeb templates frequently need porting.

Odoo 16 → 17

• Website builder rewrite — custom website snippets and themes often need a rebuild.
• POS and inventory flows change enough that heavily customized warehouse/POS modules break.
• New default UI density and form layout — inherited views need cleanup.

Every hop also means OCA and third-party modules need a matching 17.0 branch (or a replacement). Abandoned apps are often the real schedule risk.

Odoo 13 to 17 upgrade cost

Partner market rates for a 4-version Community jump with custom code commonly land in the tens of thousands (sometimes much more once workshops and retainers are bundled). Our fixed price for the same whole-instance job — database and every custom addon — usually sits in the $6,000 – $18,000 band for a typical SME setup.

• Small & clean (few custom modules, tidy data): often toward the low end, sometimes under $6,000.
• Typical (handful of custom/OCA modules, a few years of data): the band above.
• Heavy (deep custom JS, warehouse/POS/accounting overrides, large messy DB): can move into the $15,000–$40,000 tier.

It's one fixed price for the whole jump — not a fresh bill for each intermediate version. See also how much an Odoo upgrade costs and the free upgrade cost estimator.

How the upgrade works

1. You send your current version, target version, approximate custom-module count, and work email. We return a quick estimate; no files are needed for this first step.
2. For the committed fixed price, you upload a database copy and your addons. We inspect both and return one fixed price within 24 hours.
3. Once you approve the fixed price and written scope, we migrate the database and every in-scope module to Odoo 17 on a copy. Your live 13 system stays untouched.
4. You test a working copy. You pay only after the agreed checks pass.