ERP: Odoo migration
Upgrade Odoo without risk or surprises
Our Continuous Migration method writes your whole upgrade as code on our migration platform. We replay it on copies of your real data until it behaves like your live system. AI does much of the work, and a person approves every change.
Book a free discovery call See how Continuous Migration works
Why Odoo upgrades feel risky
Your Odoo version is getting old or is out of support. Custom modules, Studio changes and connections to other systems make every upgrade attempt risky.
When each test round is rebuilt by hand, there are few of them, and problems show up after the switch.
What we do about it
We take the proven upgrade steps, such as clean-up, database upgrade, module fixes and tests, and write them as code. Each test round runs on a fresh copy of your live data. We only rework what did not work the last time, so each round behaves more like your live system.
The work comes in two phases. The migration phase keeps your processes as they are, and the improvement phase starts once the new version is stable.
How it works
We prepare a fresh test environment every night by default, or every week. Your team can test as often as it needs.
01
Migration analysis
Before you commit, we review every module and customization, and the data they hold.
You get a decision for each module, a plan and an estimate, with the improvements listed separately.
02
Continuous Migration
We run test rounds on fresh copies of your live data, every night by default. Your key users test, and we only fix what changed.
You get test environments that get closer to your live system each time.
03
Switch to the new version
The switch usually happens over a weekend. The final run replays the test round your team approved.
You get a downtime estimated in advance at 8 hours, then confirmed by the real test runs.
04
Improvement phase (optional)
We make the improvements you choose, on the new version once it is stable.
You get changes once the migration is behind you.
A classic upgrade compared with Continuous Migration
We use the same proven steps as a classic upgrade. The difference is that we write them as code on our migration platform, and AI helps at every step.
| Step | Classic upgrade | Continuous Migration |
|---|---|---|
| Analysis | A list of customizations, reviewed with key users. | The same review, prepared by our AI agents from your database. |
| Clean-up of unused modules and code | Done by hand, and redone at each attempt. | Coded once, then replayed automatically. |
| Upgraded database | Requested by hand, each time. | Requested and installed automatically. |
| Module errors | Commented out and fixed step by step. | Fixed once in code. Only what changed since the last run is new work. |
| Test environments | Rebuilt by hand, so there are few of them. | Every night by default, or every week, and whenever you ask. |
| Go-live | A written checklist, followed by hand. | The same run as the last test your team approved. |
What the method changes for you
The method gives your team more test rounds, a short planned switch and a person in charge of every change.
8 h
downtime estimated in advance, usually over a weekend
A fresh test environment every night by default
Community or Enterprise, whoever implemented it
A named consultant approves every change
What we promise
A switch without risk
The final run replays the test round your team has already approved on real data.
No surprises after the switch
Your processes stay the same on day one. Improvements come in their own phase.
Short, planned downtime
We estimate the downtime in advance at 8 hours, usually over a weekend, and confirm it with the real runs.
Test whenever you need
You get a fresh test environment every night by default, or every week.
Any Odoo
We migrate Community and Enterprise, whoever implemented your Odoo.
AI does the work, a person approves it
Our AI agents find module versions in the open-source (OCA) catalogue and the Odoo App Store, and suggest fixes between test rounds. They only get the read-only access you allow, and a named consultant approves every change.
How we bill
You know the scope and the cost of your upgrade before the work starts.
We bill by the hour, against an estimate you sign. The migration analysis comes first, and the migration estimate comes out of it.
The improvement phase gets its own estimate.
Frequently asked questions
How long will Odoo be unavailable?
Only as long as the final run takes, which depends on the size of your database. It takes hours, even for the largest databases. We estimate 8 hours in advance, usually over a weekend, and confirm it with the real runs.
Can we improve things at the same time?
We split the work into two phases on purpose. There is less change for your team at once, less risk, and a migration you can check against what you already know. The improvements come in the improvement phase.
Do we need support after the switch?
Very little, and it is included anyway. The final run plays out exactly like the previous test round, which your team tested and approved.
Doesn't the Odoo upgrade service do this?
That service converts your database. We take care of your custom and third-party modules, Studio changes, connections to other systems and the testing. On Community, we use the open-source upgrade tools.
What would your upgrade involve?
Book a free discovery call to talk about your Odoo. The migration analysis then gives you a clear picture of the work, the risks and the downtime before you commit.
Related services: Odoo implementation, Odoo support and Odoo hosting.
Prefer to write? Send us a message at [email protected] and we'll reply by email.
Book a free discovery callOdoo is a trademark of Odoo S.A.