The ERP the whole company runs on — and nobody dares touch.
The system still runs, and that is exactly the problem: it runs on one aging server, a set of workarounds, and the memory of whoever set it up. Every change request gets the same answer — too risky. What you are looking for is not just new software, but a way off a system that has become untouchable, without breaking the business on the way.
—— Sound familiar?
You know this problem by these symptoms.
Every improvement request ends with the same sentence: too risky, better not to touch it.
The reports management actually uses are built in Excel, because nobody can get a new report out of the ERP any more.
The vendor stopped shipping updates years ago, so every Windows patch or new laptop feels like a gamble.
The working knowledge of the whole system sits in one employee's head, and everyone knows what their resignation would mean.
New staff spend their first months memorising codes and workarounds instead of doing the job they were hired for.
None of this is a management failure; it is what happens to any system that outlives its own architecture. The ERP was built for the company you were a decade or more ago, and every gap since has been bridged with a customisation, a spreadsheet or a manual step. Each bridge made the core harder to change, until caution hardened into policy. Once the vendor stopped developing the product — or disappeared — an ordinary maintenance question became a dead end.
—— The way out
How Odoo closes this gap.
One database instead of a patchwork
Odoo runs Sales, Purchase, Inventory, Accounting and Manufacturing on one database with one data model. The bridges you built between the old ERP and its satellite spreadsheets stop being necessary, because every module already shares the same customer, product and stock records.
Upgrades become routine, not rescue projects
Odoo ships a new version every year with a documented upgrade path, and Enterprise includes Odoo's own upgrade service. Staying current becomes a scheduled task rather than a project nobody will approve. Community remains open source, so the code can never be orphaned the way a closed vendor's product can.
Changes that never touch the core
Odoo customisations live in separate modules that inherit from standard code instead of overwriting it. That is the structural difference from your current system: changes can be added, tested and removed without anyone fearing for the core. For everyday field and form changes, Odoo Studio needs no code at all.
Reports come out of the system, not around it
Every list view in Odoo pivots, filters and exports without a developer, and dashboards plus the built-in spreadsheet engine read live data. The reporting that currently lives in Excel moves back inside the system, so the numbers quoted in meetings are the numbers the system holds.
—— How we run it
The transition, managed properly.
Map the old system before moving it
Before anything moves, we document what the legacy system really does — including the workarounds and the fields used for things they were never named for. The consultant who does this mapping is the same person who stays with you through go-live.
Data moves in validated batches
Customers, products, open orders and balances move in batches your team checks and signs off, with a rollback point at each one. Nothing is written to or deleted from the old system; it stays intact as the reference copy throughout.
Parallel run until you call it
The legacy system runs alongside Odoo through at least one month-end close, so results are compared line by line. Training happens on your live migrated data, and the old system is switched off only when your team says so.
—— FAQ
Questions teams ask about this problem.
How long does a legacy ERP migration take?
Most single-company moves take eight to sixteen weeks from mapping to switch-off, driven mainly by how much history comes across and how much cleaning it needs. We give the phased timeline after seeing your actual data, never before. The old system keeps running throughout, so no deadline forces a rushed cutover.
Can the old system keep running during the migration?
Yes — it has to. We only read from it, never write to it, and it stays the system of record until go-live. Most clients then keep it in read-only mode for a year or more, for audits and old lookups.
Our data is a mess after all these years. Will that break the migration?
Messy is normal at this age: duplicate customers, dead SKUs, fields recycled for other purposes. The mapping phase exists to surface all of it before migration, and you decide what gets cleaned, archived or left behind. Bringing over master data and open transactions while archiving deep history separately is often the right call.
What does a migration like this cost, and how is it billed?
Fixed fee per phase, quoted in writing after we have seen the system and the data — no open-ended hourly meter. Odoo Community licensing is $0; if Enterprise fits your case, Odoo bills you directly and we never mark it up. The main cost drivers are how many modules replace the old system and the state of the data, both pinned down during scoping.
Let's find out whether Odoo actually fits your business.
A short call, an honest answer. If it isn't the right system for you, we'll say so.