Data extraction
We export the data from your current ERP to files you can review. If the system has no usable export, we build the extractor.
They are two different jobs with the same method: rehearse first, with every load reconciled against the source, and reach switchover day with the rollback ready.
The old system holds years of shortcuts: duplicate customers, or payment terms typed into a free-text field. None of it shows until you try to load it somewhere else.
Something similar happens with version upgrades. Standard Odoo upgrades without a problem. What breaks are the custom developments and the scheduled jobs nobody remembers setting up.
What comes across and what gets archived is decided with you at the start and put in writing.
We export the data from your current ERP to files you can review. If the system has no usable export, we build the extractor.
Duplicates and codes that clash with each other. We give you the list of what needs deciding and write down what each old record maps to in Odoo.
Customers, suppliers, products, price lists and what is still to be collected and paid. It is the minimum you need to work in Odoo from day one.
Bringing across years of documents has a cost and doesn't always pay off. You can migrate all of it, bring only the balances or keep it archived for reference.
It is tested on a copy: we adapt your developments and check that the scheduled jobs still run. A copy of the database goes to production, and the original is left untouched.
What is in the current system and what is really used. What nobody looks at doesn't need to travel to Odoo.
We decide with you what gets migrated, what stays archived for reference and from what date the history is brought across.
Full loads in a test environment, reconciled against the source: same records, same balances. They are repeated until there are no differences.
Whoever runs each area checks their data in the test environment, working as they would on a normal day.
In a short, pre-announced window. If something doesn't go as it did in the trial runs, we go back to the old system and try again another day.
Each company handled its IT its own way. Now the group has a single point of contact for the ERP, Microsoft 365 and the monitoring of its computers
Production applications on a monitored server with backups. Project planning inside Odoo. And a single support team.
The group's consolidated accounts came from a spreadsheet built by hand. We are moving them into Odoo, with every figure traceable to its source.
Functional design process by process, written acceptance criteria, a fixed price and support through go-live.
Odoo Private SaaS: your Odoo on a dedicated server in the European Union, with backups, updates and monitoring.
A help desk for your Odoo: questions, bugs and small changes, with measured response times.
It depends on how your system stores the data and whether it is worth it. The usual approach is to bring across the master data and open balances and keep the history available for reference outside Odoo. Earlier years, if you need them inside, are quoted separately.
No. The trial runs are done in a separate environment, on a copy. Your current system keeps working until switchover day.
They need adapting, and that is where almost all the work lies. We review each module against the new version and test it before touching your database. If Odoo now does out of the box what a development used to do, we suggest retiring it.
Yes. In Odoo Enterprise, the database is migrated by the vendor's upgrade service and we adapt your developments. In Community you upgrade version by version with OpenUpgrade, the community tool, even though you only see the final jump.
Tell us which ERP or which version of Odoo you have today. In an hour we'll tell you what we would migrate and where we see the risk.