The upgrade path: 19 → 20
Odoo can't jump straight across major versions; each one carries its own data migration scripts. Moving from Odoo 19 to Odoo 20 therefore means 1 consecutive hop. 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 19 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 20 (2026)
_sql_constraintsand_constraintsno 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 19 source.
Should you upgrade Odoo 19 now?
You're on a supported version, so there's no emergency. But every year you wait adds another hop. Upgrading now keeps it to 1 hop.