Odoo data migration: bring over what matters without holding up go-live

In an ERP project, data migration is a costly, time-consuming and often underestimated phase. Many companies start out thinking they need to bring everything over, just to be safe.

In practice, every migrated line takes time to extract, clean, map, import and, above all, check from a business standpoint. Spending budget to import old data that will almost never be looked at is rarely a good investment.

Migration is about making Odoo operational with the essential information. The goal isn't to recreate the company's entire past in the new ERP. The goal is to start with a clean, consistent, useful database. A well-scoped migration speeds up go-live. A poorly planned one slows down the whole project.

Migration can potentially touch the entire ERP, because everything in Odoo is connected. But a few areas carry most of the stakes:

• Products and items: references, variants, bills of materials, logistics routes, prices.
• Sales and purchasing: customers, suppliers, contacts and orders that are still open.
• Accounting: opening entries, balances, chart of accounts and unpaid invoices.

These are the building blocks that let the company keep selling, buying, storing, delivering and invoicing from day one.

A common belief is that you can simply export the data from the old system and load it into Odoo as is. That is almost never true.

Data coming from Sage, Cegid, Prestashop, Excel or any other tool doesn't have the same structure as in Odoo. Fields, constraints, relationships between objects and formats are all different. An address, a contact, a product or an invoice often has to be restructured before import.

Requests to migrate the full history are very common: old quotes, closed orders, old stock moves, invoices going back several years.

• How often will this history actually be looked at?
• By whom, and for what specific purpose?
• What operational value will it still have a few years from now?

If the need isn't clearly justified, it is often smarter to keep this history in the old system, in read-only mode, or as exported archives. The goal is to keep an oversized data migration effort from blocking the ERP project.

The migration logic is simple: bring over the master data and everything that is still open.

• Active customers, contacts and suppliers.
• Products, variants, bills of materials and useful references.
• Pricelists.
• Opening stock levels on the cutover date.
• Open sales and purchase orders.
• Open invoices and account balances.

So the right question isn't “what can we technically migrate?” but “what do we need to bring over so the business runs properly from day 1?”

An Odoo data migration follows a structured process:

• 1. Define the data to migrate: what needs to exist on go-live day.
• 2. Identify the sources: current ERP, Excel files, accounting, e-commerce, CRM, etc.
• 3. Do the mapping: match the source columns to Odoo fields.
• 4. Prepare the files: structure the data according to the defined templates.
• 5. Clean up: fix duplicates, inconsistencies, formats and blocking empty fields.
• 6. Import into Odoo: through standard import or scripts, depending on complexity.
• 7. Check: make sure the data is actually usable in your business flows.

• Trying to migrate everything: it drives up cost, complexity and lead times.
• Confusing archives with data needed at go-live: information can remain accessible without being migrated into the production database.
• Cleaning up too late: it puts the whole schedule under pressure.
• Treating migration as a simple technical import: it is also a business, organizational and operational issue.
• Delaying go-live in pursuit of pointless perfection: aim for a good level of quality without turning the migration into a bottleneck.

Migration is not a purely technical matter handled by the integrator alone. The client plays a central role. The SPoC and key users need to extract, gather and prepare the data to migrate, confirm what it means for the business and fill in missing information.

That makes sense: we know how to bring the data into Odoo, but you are the only ones who know what your business data really means.

Our role goes beyond running an import. We handle the scope analysis, trade-offs, the target structure in Odoo, import rules, consistency checks and securing the go-live. We guide you on format, priorities and the right method so you don't lose time.

One idea should guide the entire migration: data migration should serve go-live, not delay it unnecessarily.

If not all the data is perfectly clean in time, that shouldn't necessarily block go-live. Some corrections can be made after go-live, directly in Odoo, as long as the business can run normally. The goal is to get data as clean as possible without jeopardizing the cutover date.