Upgrade your Odoo 13 module to 17

Moving a custom module from Odoo 13 to Odoo 17 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 17, 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 13 and 17

• Odoo 14: Python and view-level API cleanups accumulate; custom JavaScript widgets written for the old web client start drifting from what core expects
• Odoo 15: Frontend assets move out of XML template inheritance and the manifest qweb key into the assets dict in __manifest__.py How we fix it →
• 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 →

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 17 and fixing until tests pass.