
Buying Odoo
- Author
- Clovis de Bontin
- Published
- 14 November 2026
- Reading time
- 7 min read
What to clean before an Odoo data migration
A data migration is mostly decisions, not files. Customer records, product units and the chart of accounts are settled before anyone opens a spreadsheet. Settle them late and the import runs cleanly into a database nobody can use.
The export is the easy part
Every implementation ends with a file going in, and the file is mechanical: map the columns, test, then import (Odoo 20 documentation, Export and import data, 14 November 2026). What decides whether go-live is calm is whether two people agree what a customer, a product and a sales unit are before that file is taken. That is master data, small in volume and large in consequence.
Give every record an ID you control
Odoo can use your old system's identifier as the record's external ID. The documentation recommends keeping that column: it lets you re-import the same file without duplicates, and it is how linked records find each other (Odoo 20 documentation, Export and import data, 14 November 2026).
Two records with the same external ID cause a conflict. That sounds technical. It is a question about the old system: does it hold one row per real customer, or three for the same company because three people typed it in? Sort that before the import, and write down the rule you used.
Customers and suppliers: merge before you import
Odoo can search for duplicates by email, name, company status, VAT number and parent company. Select more than one field and only records sharing all of them are suggested (Odoo 20 documentation, Merge contacts, 14 November 2026).
That is a matching tool, not a decision. It will not tell you that Acme Ltd, Acme Limited and ACME are one account, or that a contact is both customer and supplier. Merging is irreversible (same page), so the decision wants someone who knows the accounts, a list of suspicious records, and a rule: which record survives, which address invoices, which contact stays.
Softhealer, the technical partner for the United Kingdom, says the same on its migration page: duplicate data is cleaned up first (checked 14 November 2026).
Products: one unit, one meaning
A product record is a price, a cost, a unit and a stock behaviour. The unit is where small companies get caught, because Odoo requires a purchase unit of measure to sit in the same category as the product's default unit (Odoo 20 documentation, Units of measure, 14 November 2026).
The question to settle is what a box means. If a box holds twelve units from one supplier and ten from another, it is a packaging. The stock record belongs in the thing that does not change.
List the units the business uses: each, box, pallet, metre, kilogram, hour. Name the stock unit for each product family. Anything sold in decimals needs a precision decision, not a rounding habit that four people apply differently.
The chart of accounts is the one-way door
Odoo installs a chart of accounts from the country set when the database is created, and the fiscal localization behind it cannot be changed once a journal entry has been posted (Odoo 20 documentation, Chart of accounts, 14 November 2026).
That makes country and accounting structure the first decision, not the last. If the company trades from two countries, or the accountant relies on a chart the old system customised, settle it before the first opening entry. After that the only route is a new database.
The account type matters more than the code. It sets the rules that close a fiscal year and generate opening entries (same page). A wrong type can leave a balance sheet that reconciles and a report that does not.
Opening balances: one date, one trial balance
Pick a cutover date and take one trial balance as at that date from the old system. That trial balance is the only source for opening balances, not a year-end report or a spreadsheet someone has been updating since.
The opening balance should reconcile to the old system's closing position before it goes in. If the two disagree, the difference is a question for the accountant, not a rounding entry. Imports are permanent and cannot be undone, so a correction is a second import layered on the first (Odoo 20 documentation, Export and import data, 14 November 2026).
Small fields that stop an import
Dates are the usual culprit. A date written 01-03-2016 is ambiguous, and Odoo recommends ISO 8601, as in YYYY-MM-DD, when a file's format is not certain (Odoo 20 documentation, Export and import data, 14 November 2026).
A currency symbol Odoo does not recognise can crash an import. Brackets mean a negative, with the symbol inside them. A tab-separated file is the quiet one: Odoo expects commas, and the formatting options will not repair a tab.
Large files time out, so imports run in batches (same page). A mistake in two hundred records is a repair. The same mistake in twenty thousand is a project.
A cleaning order that holds
| Order | What to settle | Why it blocks |
|---|---|---|
| 1 | Customers and suppliers: one record per real organisation, VAT checked, merge list agreed | Every order, invoice and price list points at these |
| 2 | Products: stock unit per family, packagings, decimal precision | Stock and cost start from here |
| 3 | Chart of accounts: country, localization, account types | Locked after the first journal entry |
| 4 | Opening balances: one trial balance at the cutover date | Every report is measured against it |
| 5 | Open transactions: open orders, purchase orders, part deliveries | Work in progress the team must finish |
| 6 | History: what to migrate and what to archive | Volume without a reader slows every import |
The chart of accounts sits third only because the country decision comes first. In practice the two are settled together.
What not to bring across
Old transactional history is the usual over-import. A sales order from five years ago is a record, not a working document. If the business needs it for a tax enquiry or a warranty claim, a read-only archive does that job without slowing every list view for a decade.
The data decisions belong to the business. The partner runs them.
The implementation is where this work is planned and run: Odoo implementation covers configuration, data migration, training and go live. We implement Odoo with our technical partners, and the agreement is with the partner for your country.
For the version route rather than a first implementation, read what an Odoo version upgrade settles first.
Sources
- Odoo, Export and import data, Odoo 20 documentation, checked 14 November 2026: https://www.odoo.com/documentation/20.0/applications/essentials/export_import_data.html
- Odoo, Merge contacts, Odoo 20 documentation, checked 14 November 2026: https://www.odoo.com/documentation/20.0/applications/essentials/contacts/merge.html
- Odoo, Units of measure, Odoo 20 documentation, checked 14 November 2026: https://www.odoo.com/documentation/20.0/applications/inventory_and_mrp/inventory/product_management/configure/uom.html
- Odoo, Chart of accounts, Odoo 20 documentation, checked 14 November 2026: https://www.odoo.com/documentation/20.0/applications/finance/accounting/get_started/chart_of_accounts.html
- Softhealer, Odoo migration services, checked 14 November 2026: https://softhealer.com/odoo-migration
I sincerely hope this was helpful, and if you have any remark, suggestion or question, you can email me at louis@cdb.solutions or DM me on LinkedIn.
Thank you,
Clovis
Next step
See this in practice
Book a free demo. The technical partner for your country shows the apps that fit, at no charge.
Canonical URL: https://www.cdb.solutions/articles/what-to-clean-before-an-odoo-data-migration
FAQ
Answers to the questions this article raises
The questions buyers ask most, answered here. If yours is not covered, ask us directly.
01How long does an Odoo data migration take?
02Can we clean the data after the import?
03Do we have to migrate every historical record?
04Who decides what a product's unit is?
Next step
Book a free demo
Tell us the country and the operation. The technical partner for your country shows Odoo against your process, at no charge.
+33 7 69 45 83 27UK with SofthealerEverywhere else with AppNvent
Free demo
Put this against your own operation
Country, industry and company size. The technical partner scopes the work and holds the agreement.
Country chooses the partner. The UK is implemented with Softhealer. Everywhere else, with AppNvent.
The demo is specific. Industry and company size tell the technical partner which apps to show you.
No charge, no obligation. Scoping and any agreement come later, and only if you want them.
