Three-version Odoo upgrade, delivered in 3 weeks
An 18 GB database and 84 customized modules moved from Odoo 16 to 19 in three weeks, without a weekend the business had to gamble on.
The situation
The client was three major versions behind, on Odoo 16, with 84 customized modules in production — new modules written for them, POS customizations, and changes to native Odoo flows that no longer matched upstream. The database was 18 GB. Every quarter spent waiting made the eventual jump larger, and the modules least likely to survive it were the ones the business depended on daily.
What we did
We did not attempt the jump in one move. Each major version was rehearsed on a copy first — 16 to 17, then 17 to 18, then 18 to 19 — with the customizations reviewed against what upstream had changed at each step. That is what turns an upgrade from a weekend gamble into a sequence of known outcomes: by the time the production run happened, every failure had already been seen and fixed on a rehearsal.
The outcome
Three major versions in three weeks, with the cutover itself taking a single planned window. All 84 modules came across; those broken by upstream changes were repaired rather than dropped, so no working process was lost to the upgrade. The database is now on a version that still receives updates, which is the part that decides whether this has to be done again next year.
Delivered by our engineers. Client names are withheld under confidentiality; scope and outcomes are stated exactly.