Migration planning
Decide what moves (master data, open documents, opening balances, stock) and what stays archived in the old system.
Odoo migration and version upgrades
There are two different jobs under this heading. A data migration moves your records from spreadsheets or another system into a new Odoo database. A version upgrade moves an existing Odoo database to a newer release. Both succeed or fail on preparation and testing, which is where I spend most of the effort.
Problems this solves
- Product, customer and vendor data is spread across spreadsheets and an old system, with duplicates and gaps.
- Your Odoo version is approaching or past the end of its support period.
- Custom modules or integrations make you nervous about upgrading at all.
- A previous import went wrong and left the database untrustworthy.
A good fit if
- You’re moving onto Odoo and need your products, contacts, open orders and stock carried across cleanly.
- You run an older Odoo version and want a planned, tested upgrade.
- You can provide access to source data and a person who knows it.
Probably not the right fit if
- You want to switch edition or hosting as part of an upgrade without planning it separately; Odoo treats those as separate changes.
- You expect years of historical transactions to be moved line by line; that is rarely worth the cost, and we’d discuss alternatives.
Scope
Data cleaning and mapping
Templates, duplicate checks and field-by-field mapping from your source files to Odoo's structure.
Trial loads
Load into a test database first, reconcile totals and counts, fix issues, then repeat.
Upgrade assessment
List installed apps, custom modules and integrations, and identify what must be adapted for the target version.
Test upgrade
Request an upgraded test database, have users test key processes, and record every difference.
Cut-over
Plan the production upgrade or final data load, the downtime window and the checks to run afterwards.
What you receive
- A migration or upgrade plan with scope, sequence and downtime window.
- Cleaned data templates and a reconciliation of what was loaded against the source.
- A list of custom modules and integrations with what each needs for the new version.
- Test results from the upgraded test database, with issues and their resolution.
How the work runs
- Assess. Review the source system or current database, apps, customisations and data quality.
- Plan. Agree what moves, in what order, who checks it and when the cut-over happens.
- Prepare. Clean and map data, or adapt custom modules for the target version with the developers involved.
- Test. Trial loads or an upgraded test database, checked by your users against real scenarios.
- Cut over and verify. Run the final load or production upgrade, then reconcile stock, open orders and balances.
What I need from you
- Access to the source data or current Odoo database, and someone who understands it.
- Decisions on what history to bring across and what to archive.
- For upgrades: the source code of any custom modules, and contact with whoever maintains your integrations.
- Users available to test the trial load or upgraded test database.
Experience behind this service
- Project manager at Master Software Solutions since November 2022, responsible for planning, testing and cut-over on client projects.
- ERP consultant (Odoo) since October 2024, with an Odoo 19 Functional Certification (2026).
- Guides on importing data into Odoo and the mistakes to avoid when importing.
- Migrations I worked on at MSS, including accounting from QuickBooks into Odoo and paper records and an old CRM into multi-company Odoo.
You work with me directly: I'm Sajjal Bajaj, an Odoo ERP consultant and project manager at Master Software Solutions in Mohali, India. Read about my background or see my CV.
? Frequently asked questions
What is the difference between an Odoo migration and an upgrade?
A migration moves data from another system or from spreadsheets into Odoo. An upgrade moves an existing Odoo database to a newer Odoo version. Odoo's own upgrade process covers version upgrades only; it does not cover migrating from another ERP, switching between Community and Enterprise, or changing hosting type.
Can a database with custom modules be upgraded?
Yes, but the custom modules must first be adapted to the target version; Odoo's documentation states that a database with custom modules cannot be upgraded until those modules are available for the new version. That work is planned alongside the request for an upgraded test database.
How is an upgrade tested?
Odoo provides an upgraded copy of your database for testing. Users run their key processes on it, differences are recorded and resolved, and only then is the production upgrade scheduled.
How long is an Odoo version supported?
According to Odoo's upgrade documentation, each major version is supported for three years. Odoo Online databases on a major version must be upgraded every two years, so it pays to plan rather than wait for the deadline.
Do we have to bring all our history into Odoo?
Usually not. Most businesses bring master data, open documents, current stock and opening balances, and keep older history available in the previous system or as an archive. We decide this together during planning.
Moving onto Odoo or upgrading?
Tell me your current system or Odoo version, roughly how much data is involved and whether you have custom modules or integrations. I'll outline the steps and the questions we'd need to answer first.
Discuss your project