Upgrade your Odoo 15 module to 19

Moving a custom module from Odoo 15 to Odoo 19 means 4 versions of breaking changes — views that no longer validate, renamed methods, JavaScript the newer web client rejects. It's tedious, and it's exactly what we do for you.

Send us the one module. We install it on Odoo 19, fix everything the jump broke, and run tests until it's green. You try the result live before paying a cent — then it's $50 to download, with a full changelog of what we changed.

What actually breaks between Odoo 15 and 19

• Odoo 16: The web client moves to Owl 2 — legacy odoo.define modules need converting to ES modules with /** @odoo-module **/ How we fix it →
• Odoo 17: attrs= and states= are removed from view XML — every conditional modifier becomes an inline Python expression How we fix it →
• Odoo 17: name_get() is replaced by _compute_display_name on models that customize record display names How we fix it →
• Odoo 18: The <tree> view tag is renamed to <list> — view XML, view_mode in actions, and xpath expressions all need updating How we fix it →
• Odoo 19: SQL constraint declarations move away from the classic _sql_constraints tuple format, and view validation keeps getting stricter How we fix it →

Those are just the headline changes — most modules also hit renamed core fields, stale __manifest__.py dependencies, and xpath targets that no longer exist. We find all of it by installing the module on Odoo 19 and fixing until tests pass.