Your data moves. Your business keeps running.
An old Odoo version with no security updates, a system nobody can get out of, or the move into hosting with Odoo: the switch is manageable when it's prepared and rehearsed beforehand. That's exactly the work we do.
How you know it's time to switch
Nobody switches for fun. There's usually a specific reason. If one of these sounds familiar, it's worth a closer look.
Your version isn't getting updates anymore
Odoo supports every major version for three years. Standard support for version 15 ended in October 2024, for version 16 in September 2025. Versions 17, 18 and 19 are currently supported, with version 17 leaving standard support in September 2026. After that there are no more security updates, and every change becomes a risk.
Systems that don't talk to each other
Sales in one tool, stock in the next, accounting bolted on somewhere else. Someone's retyping the same order for the third time.
Reports that are always a day late
When getting solid numbers means exporting three spreadsheets and reconciling them by hand, the system is working against you.
Customizations nobody dares touch
Years of change on top of change, and the one person who understood it all left the company long ago.
What a migration actually means
A migration doesn't just move a database, it moves the business: data, users, settings, workflows, reports, custom modules, integrations and history. The goal is a current Odoo environment that works Monday morning exactly the way your team is used to.
This has little to do with "just copying data over." It includes an honest assessment of data quality, mapping every field on purpose rather than by guesswork, the question of which custom modules and integrations are actually still needed, testing against real cases, and a migration plan everyone knows in advance.
What Odoo covers itself, and what you need us for
Odoo offers Enterprise customers its own upgrade service, and it's included in the subscription. We'd rather tell you that here than later.
What Odoo does
Odoo converts the database to the new version, including the standard apps. The process is always the same: first a test database is converted, then the production database. For Enterprise customers, this service is included in the subscription.
What Odoo doesn't do
Not included: cleaning up your historical data, custom modules and extensions without a maintenance contract, and training on new features. Testing the converted database is your responsibility. Custom modules have to be adapted in source code before the upgrade.
That's exactly where we come in: we look at your data quality, bring your own modules up to the new version, reconnect the integrations, test against real cases and support the migration. You don't pay us for the database conversion itself.
For a migration from another system to Odoo, this service doesn't exist. There, every mapping is built by us.
Six areas that make up a migration
Most projects combine two or three of these.
Odoo Version Migration
From an older or unsupported Odoo version to current, without the business coming to a stop.
- Conversion planning
- Review of changed features
- Adapting your own code
- Testing against the new version
Legacy ERP to Odoo
A structured path off your current software, without the standstill a single-weekend cutover would bring.
- SAP Business One, Microsoft Dynamics, Sage
- QuickBooks and comparable accounting software
- Custom-built legacy systems
Data Migration
Your data is the actual point. It's about accuracy and quality, not just pushing rows from one place to another.
- Customers and vendors
- Products and inventory
- Financial records and history
Custom Module Migration
Code that ran on the old version rarely survives a version change unchanged. We assess it before it fails in production.
- Check dependencies
- Adapt code
- Test behavior on the new version
Integration Migration
Every connected system has to keep working after the switch, not just the Odoo screens your team sees daily.
- Payment providers
- Shipping and carriers
- Accounting, such as our BMD export
Cloud & Odoo.sh Migration
From your own server to Odoo Online or Odoo.sh, with a clean cutover date.
- Current-state assessment
- Backups and rollback path
- Choosing the right hosting model
BMD is a registered trademark of BMD Systemhaus GesmbH. E&P Solutions IT GmbH is not affiliated with BMD Systemhaus GesmbH. The name is used to describe compatibility.
Four paths, and one of them is yours
Every starting point is different. These are the four shapes a migration project usually takes.
Odoo-to-Odoo
From an older version to the current one, with data, workflows and customizations intact.
ERP-to-Odoo
The previous software is replaced, through structured data mapping, review and a staged rollout.
Community-to-Enterprise
The switch to Odoo Enterprise, once feature scope, support and hosting on Odoo.sh are needed. We work exclusively with Enterprise.
On-Premise-to-Cloud
An existing installation moves to Odoo Online or Odoo.sh.
An eight-step process, run the same way every time
Consistency is what makes migration safe. Every project moves through the same eight stages, so you always know exactly where things stand.
Migration Assessment
Goal, stakeholders, target environment and scope, with verifiable criteria for when it's succeeded.
Technical Analysis
Environment, databases, integrations, custom modules and reports are checked for risk before anything moves.
Migration Planning
A written plan: milestones, ownership, testing approach, backups, rollback path and the migration date.
Data Preparation
The old data is cleaned, checked, transformed and mapped. Then you sign it off before it touches the new system.
Migration Execution
The approved data, settings, modules, workflows and integrations are carried into the target environment.
Testing & Validation
Functional testing, integration testing, side-effect checks and data reconciliation, plus sign-off from your team.
Go-Live Management
Final backup, catching up on activity since testing, switch to production and monitoring while your team starts working.
Post-Migration Support
The weeks after are when the questions come. We stay close during that time.
Not sure yet which path is yours?
Tell us which system you're on today and which Odoo version it's running. We'll tell you what's involved.
Systems we migrate data from
The approach is the same for every source system: first we look at what data can actually be extracted, then we set the plan. Which systems we've already replaced, we're happy to discuss openly in conversation, including the cases that turned out more involved than expected.
What actually comes across
A realistic picture of what transfers cleanly, and what needs a closer look first.
| Business area | Typical records | Migration support |
|---|---|---|
| CRM | Leads, opportunities, activities, notes | Standard |
| Sales | Quotations, orders, customer history | Standard |
| Purchase | Vendors, purchase orders, receipts | Standard |
| Inventory | Products, warehouses, stock, serials | Standard |
| Accounting | Journals, invoices, payments, balances | Needs reconciliation |
| Manufacturing | BOMs, work orders, routings | Standard |
| HR | Employees, attendance, leave records | Standard |
| Projects | Tasks, timesheets, milestones | Standard |
| Documents | Attachments and supporting files | Depends on source access |
"Standard" means: there's a proven way to do it. It doesn't mean it happens without review. Every mapping is approved by you before it counts.
Accounting is the only row where we don't say standard. Balances, tax codes and open items have to match as of the cutoff date, and we check that together with your tax advisor.
You can't just switch off the old system
Under § 132 of the Austrian Federal Fiscal Code (BAO), books, records and receipts must be kept for seven years. Where they're kept electronically, complete, ordered, content-identical and true-to-original reproduction has to be possible at any time during that whole period. A data export into a spreadsheet doesn't meet that requirement. So before the migration, we clarify with you and your tax advisor which years move into the new system and how the rest are archived so they stay readable in the event of an audit.
What we check before a single record moves
This is the checklist our team runs before development, testing or production migration begins.
Odoo Ready Partner and active OCA member
Especially with a migration, it matters that someone works to the same standards as the platform itself.
Odoo Ready Partner
Verified in Odoo's official partner directory, so you are working with a vetted team.
OCA Member
We use and support Odoo Community Association modules. When it comes to version upgrades, that pays off because these modules are maintained and we don't have to update them ourselves.
What a migration with us actually looks like
Every migration is rehearsed first against a copy of your real data. You see the result before go-live and sign it off. The rollback path is set in writing before the switch, not only once something goes wrong.
Migration questions we hear on almost every call
Plan Your Migration While You Still Can
Tell us which system you're on today, which Odoo version it's running, how much data there is and what depends on it. You'll get a path that fits you, not a sales brochure.