Odoo module upgrades, done for you

Upgrade your Odoo 13 module to 16

Moving a custom module from Odoo 13 to Odoo 16 means 3 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 16, 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 16

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 →

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

Send this module — $50 How it works

Try the working result before you pay a cent. No signup to get started.

Common questions

How much does it cost to upgrade an Odoo 13 module to 16?

This is a 3-version jump, which prices at the complex tier: a flat $250. Every version boundary adds its own breaking changes, and crossing 3 of them is real work even for a simple module. The site scans your module and confirms the price before you send it.

Do I have to pay before I see it working?

No. You get a live instance to try your ported module first. Payment only unlocks the download.

How long does an Odoo 13 to 16 module upgrade take?

Standard modules come back within 24 hours. The complex ones (heavy JavaScript, deep customization) come back within 3 days.