Staying costs more than the licence invoice
The “annual maintenance” line is the visible part. The rest: reports rebuilt by hand every month, double entry between the system and the files, the consultant called back for every change, the person whose departure would stop everything, and the decision put off because the number exists nowhere.
We don't ask you to take our word for it: that is exactly what the diagnostic puts numbers on, with you, before any commitment is made.
What we guarantee
That the business keeps running.
ERP migrations fail on people, processes, cutover and training — not on data transfer. We run the project as a change project: a named team on your side, milestones with written acceptance criteria, and a cutover rehearsed on a copy before it's done for real.
That the history comes along.
Orders, invoices, payments, inventory, journal entries: years of history, not an opening balance — with migration tools built to be rerun (below).
That you stay in control.
Everything we build is yours: open code, exportable data, documentation, hosting wherever you decide. Dependence, if there is any, is a choice you renew — not a lock.
Do you really need to change?
Not always. A system change is justified by one of three reasons, and each can be costed:
A risk you already carry
- Your vendor is forcing a migration, raising its prices or has just been acquired.
- Aging technology, or only one person who knows how to keep it running.
- No tested restore: an outage would stop orders.
Friction that costs you every week
- Hours spent extracting data and building reports by hand.
- Too many clicks for everyday work, too little automation.
- Sales reps checking prices and re-entering data instead of selling.
- You can't see clearly where your operations lose time and money.
An opportunity your current system blocks
- Sell online to your customers.
- Largely automated accounting, and reports always ready for the bank or for financing.
- Know the actual margin by customer, project or product, to decide faster with less risk.
- Processes specific to your core business, too particular for generic software.
If you recognize yourself here, the diagnostic puts a number on each situation and ranks your options. Sometimes it's a migration with full history — the project we deliver best. Sometimes it's a single missing tool, or protecting yourself first. Sometimes it's “don't change anything for now.”
How the diagnostic worksMigration tools built to be rerun
We don't migrate once, by hand, on cutover night. Our migrations are programs that we rerun as many times as needed.
Repeatable
Several test migrations, sometimes dozens: each team tests, trains and validates its own data, in turn, before the real cutover. Cutover day is just one more rehearsal.
A common core
Each engagement builds on the same framework and on what the previous ones taught us. So each migration is faster, more reliable and more complete than the last.
Open code
Our SAP Business One, xTuple and QuickBooks Online migrators are published under an open-source licence (LGPL). Your team, another partner or any Odoo user can read, adapt and improve them.
The same goes for all the code we write, except what would protect a trade secret that belongs to you. See the migrators on GitHub →
What it asks of you
- An owner on your side with the authority to decide.
- Your people's time at the right moments: validating migrated data, trying things out, getting trained.
- The will to shut down the old system, not keep it running in parallel indefinitely.
If any of the three is missing, we'll tell you in the first conversation — and we usually know someone better placed.
And if the data is messy?
Rules? Into the migration.
If you can explain them, we build them into the transfer.
Painful clean-up? Afterwards, in Odoo.
Its clean-up tools are good; the old system doesn't need to be touched.
AI, if you want it.
Once the data is in Odoo — and with your agreement to connect it — AI does a good share of it.
It's not a prerequisite, it's our job.