Can I upgrade Odoo 15 directly to Odoo 20?

Yes, as a single project. Technically the database passes through 15 → 16 → 17 → 18 → 19 → 20, but TechUltra Upgrades runs and checks every hop for you and you only test the final Odoo 20 result.

How long does an Odoo 15 to 20 upgrade take?

Expect a longer project than for recent versions because of the engineer-assisted early hops. The free assessment gives a module-by-module plan and timeline for your database.

Is Odoo 15 still supported?

No. Odoo maintains only the three most recent major versions (18, 19, 20). Odoo 15 is 5 years old and is out of support.

What does it cost to upgrade Odoo 15 to 20?

Every upgrade is quoted on its complexity after the free assessment. Cost depends on database size, the 5 hops involved and the number of custom or third-party modules to port.

Upgrade Odoo 15 to Odoo 20: Steps, Changes & Cost

The upgrade path: 15 → 16 → 17 → 18 → 19 → 20

Odoo can't jump straight across major versions; each one carries its own data migration scripts. Moving from Odoo 15 to Odoo 20 therefore means 5 consecutive hops. TechUltra Upgrades runs them back to back on a copy of your database, saves a checkpoint after each one, and resumes from the last good hop if something fails, instead of starting over.

What changes between Odoo 15 and Odoo 20

These are the framework changes your custom modules cross on the way. Each one is handled by our porting rules and reviewed by an engineer.

Arriving at Odoo 16 (2022)

Web client moves to OWL 2; legacy widgets and field widgets must be rewritten.
fields_view_get replaced by get_views; view-manipulation overrides break.

Arriving at Odoo 17 (2023)

attrs and states removed from views: visibility rules become plain Python expressions on invisible/readonly/required.
name_get deprecated in favour of _compute_display_name.
Python 3.10 becomes the minimum runtime, so servers and dependencies need upgrading too.

Arriving at Odoo 18 (2024)

views renamed to across XML views and actions.
Many JS patches and client actions need updating for the reworked OWL services.

Arriving at Odoo 19 (2025)

SQL constraints move from _sql_constraints to declarative models.Constraint objects.
ORM internals reorganised under odoo.orm; imports and private API calls need updating.

Arriving at Odoo 20 (2026)

_sql_constraints and _constraints no longer supported at all, so un-ported modules silently lose their constraints.
Accounting: parent accounts replace account groups, account codes become optional, depreciation models replace asset models.
AI agents that create and update records and connect over MCP; new offline mode for field users.

How TechUltra Upgrades handles this path

Preflight checks for PostgreSQL version, hop images and upgrade scripts before anything runs.
Custom modules detached during hops so the standard data migrates cleanly, then re-attached as ported Odoo 20 code.
Auto-heal for known upgrade failures, such as bad XML-ID renames and orphan views, with automatic hop retry.
Reconciliation of trial balance, stock valuation and receivables/payables against your Odoo 15 source.
Engineer-assisted early hops: versions before 16 cross older framework changes which our team handles hands-on.

Should you upgrade Odoo 15 now?

Yes. Unsupported versions miss security patches, can't install current apps and get harder to upgrade with every release. Waiting one more year adds another hop and another round of breaking changes.

Upgrade Odoo 15 to Odoo 20