Module porting
Your custom modules, ported to Odoo 19 or 20
Odoo's upgrade service migrates your data and the standard apps. Custom code is left out, and the database cannot move to the new version until someone ports it. That is the part we do.
What is included
From inventory to go-live
A porting project covers the code, not the data: Odoo's upgrade handles the data, and we make sure your modules are ready when it runs.
- Inventory. Every custom and third-party module, what it does and who uses it.
- Pruning. What the new version already covers is dropped, not ported. It is usually a good part of the list.
- Port. Python, views, reports, security rules and JavaScript (OWL), following the new version's conventions.
- Tests on your data. We validate on a copy of your real database, with the flows your users run every day.
- Go-live support. Two to four weeks after the switch to fix what shows up in real use.
How we work
A paid diagnosis first, then a fixed price per module
Diagnosis
A short, paid study of your code and database. You keep the report even if you port with someone else.
Quote
A closed price for each module, a date and the list of what is out of scope.
Port and test
We deliver the ported modules in your repository, with the test results on your copy.
Go-live
We support the switch together with your team or your partner.
Odoo 20
The version that breaks the most custom code
Odoo 20 replaced the access rules model, moved the web client to OWL 3 and made field tracking an optional module. Modules that inherit security, views with JavaScript or tracking need real rewriting, not a search-and-replace.
We already ported our own apps to Odoo 20, so we know where it breaks.
Questions
Before you ask
Do you replace our Odoo partner?
No. The upgrade of the database is requested by whoever holds the Enterprise contract. We deliver the ported code and work alongside your partner or your internal team.
Community or Enterprise?
Both, hosted on Odoo.sh or on your own servers.
Which versions?
We port towards Odoo 19 and 20. The diagnosis tells you whether it is better to go one version at a time or jump directly.
What if a module is not ours or has no source code?
The diagnosis says so: sometimes there is a newer version from its author, sometimes it has to be rewritten, and sometimes it can be dropped.