Odoo Data Migration for Trading Businesses: What We Plan Before Go-Live

Odoo ERP data migration roadmap for trading businesses showing messy data to clean structured system

Key takeaways

  • Decide what to migrate per data type: move it, clean it first, keep it for reference, or leave it behind.
  • For a commodity trader, product master data needs the most design work: grade, packaging type, weight per unit, HS code, shelf life and temperature range.
  • The same product in a different package should be a separate item, or stock and pricing will not reconcile.
  • Load data in a fixed order, starting with the chart of accounts and ending with a validation report.
  • Odoo 19 imports Excel and CSV files. Imports cannot be undone, so test first and use External IDs so you can re-import to correct records [1].

Overview

This article explains how we plan data migration on our projects, using the requirements we wrote for TAM Trading as the example. Migration is one stream in how we plan an implementation.

TAM’s finance work relied on Excel trackers, physical approval forms and email confirmations. The requirements assume TAM provides clean master data for customers, suppliers, products, warehouses and ports, and include migration of historical invoices with duplicates removed.

Migration is often treated as a technical task near the end of a project. In practice, it is mostly a business task: someone who knows the data has to decide what is correct.

Step 1: decide what to migrate

Data migration decision matrix: migrate, archive, clean or discard
DataTypical decisionNotes
Customers and suppliersMigrateRemove duplicates; capture KYC and compliance documents
ProductsMigrateDesign the product master first (see Step 2)
Opening stockMigratePer warehouse, location and company
Open invoices and billsMigrateNeeded for credit control and payments
Historical invoicesMigrate if needed for reportingTAM’s finance scope includes it, with de-duplication
Chart of accountsFinish before migrationTAM’s was about 80% complete when the requirements were written
Older transactionsUsually keep for referenceExpensive to migrate in full
Obsolete products and inactive contactsLeave behindArchive them in the old system

A useful rule: migrate what the business needs to operate on day one and to report on the current year. Keep the rest where it is, read-only, for reference.

Step 2: design the product master before importing anything

For a commodity trader, the product list looks simple but is not. In TAM’s Supply Chain specification, each product carries:

  • Name and grade
  • Packaging type: bulk, jumbo bag or 25 kg bag
  • Standard weight per unit
  • HS code
  • Shelf life
  • Temperature range

Two further rules affect migration directly:

  • Packaging makes a separate item. A 1.25 MT bag and a 1 MT bag of the same product are different items for stock, pricing and reporting, even with the same name and HS code.
  • Units must convert consistently. Kilograms per drum, tonnes per jumbo bag, and bag-to-bulk conversions must be defined once and used the same way on proformas, purchase orders, receipts and invoices.

An illustrative product template for a trader:

Internal referenceNamePackagingUnitWeight per unitHS codeCosting
SA-DL-JB125Soda ash dense, light gradeJumbo bagBag1.25 t2836.20AVCO
SA-DL-JB100Soda ash dense, light gradeJumbo bagBag1.00 t2836.20AVCO
SA-DL-BLKSoda ash dense, light gradeBulkTonne1.00 t2836.20AVCO

If these are not settled before import, the opening stock will not match the physical count, and the first invoices will show the wrong quantities. Product and warehouse design across countries is covered in stock across UAE and KSA.

Step 2b: clean each data type before it moves

Data typeWhat to check before import
CustomersDuplicates under different spellings, VAT or tax numbers, billing and delivery addresses, payment terms, credit limits
SuppliersDuplicates, bank details confirmed in writing, currencies, payment terms
ProductsOne name per item, unit of measure, weight per unit, HS code, product category and costing method
Opening stockCounted quantity per location, lot or batch numbers, expiry dates where relevant
Open invoices and billsMatches the aged report, currency, due date, partial payments already received

Cleaning is faster in a spreadsheet before import than in Odoo afterwards. Once transactions start, a duplicate customer has invoices on both records, and merging them becomes a cleanup project of its own.

Who does what

TaskClientImplementation partner
Decide what to migrateDecidesAdvises
Provide import templatesProvides
Extract data from the old systemDoesSupports
Clean and correct dataDoesFlags issues
Run trial importsReviewsDoes
Count stock and confirm balancesDoesSupports
Sign off the migration reportSignsPrepares

Step 3: load data in the right order

Each data type depends on the ones before it. Products need units and categories. Opening stock needs products and locations. Open invoices need customers, products and accounts.

Data migration load sequence: chart of accounts, companies and warehouses, units and packaging, products, customers and suppliers, opening stock, open invoices, validation report
The order we load data in.

We run at least one trial migration into a test database before the final one. The trial shows which files fail, which mappings are wrong and how long the real load will take.

Phased data migration roadmap from assessment to final cutover and support

Step 4: plan for data held by partners

TAM uses third-party warehouses. The requirements assume each 3PL either has access to an Odoo portal or sends periodic imports of receipts and dispatches. Decide early which applies to each partner, because it changes how opening stock and daily movements are loaded.

The same applies to freight forwarders and clearing agents if their data feeds landed cost or shipment status. Ask what format they can send, and how often, before the migration plan is fixed.

Step 5: use Odoo’s import tool properly

Odoo 19 can import into most objects (contacts, products, journal entries, orders) from Excel or CSV [1]:

  1. Open the list view, click the Action icon and choose Import records.
  2. Upload the file and check the column-to-field mapping.
  3. Click Test.
  4. Click Import.
Import records option in the Odoo 19 action menu
The Import records option in the action menu [3].

Odoo tries to match each column to a field. Check every match, because a wrong match imports data into the wrong place without an error.

Matching a file column to an Odoo field during import
Matching a column to a field during import [3].

Points that matter on a real project [1]:

  • Imports are permanent. Filter by creation date to find imported records.
  • External IDs let you re-import to update. If the file has an External ID column, Odoo updates existing records instead of creating duplicates.
  • Large files can time out. Split them into batches.
  • Orders with several lines need one row per line, with the order details only on the first row.
  • Start from an export. Exporting a few records with the import-compatible option gives a template with the right columns.

Step 6: opening balances

Opening balances are where migration errors show up in the accounts. We load them in three parts:

  • Stock: counted quantities per product, lot and location, loaded as an inventory count so stock and stock value are created together.
  • Receivables and payables: each open customer invoice and supplier bill as its own record, so payments can be matched and aging reports work from day one.
  • Other balances: bank, fixed assets, loans and equity through an opening journal entry, agreed with the client’s accountant.

The cut-over date matters. Pick a period end, freeze transactions in the old system, take the stock count, and load balances as of that date.

Step 7: multi-company migration

TAM runs three entities in one database. In Odoo 19, products and contacts are shared by default, and values such as product cost are company-specific [2]. Decide which records are shared before importing, and load company-specific values such as opening stock, cost and open invoices separately for each company. Employee records follow the same rules; see one HR setup across three countries.

If your migration plan has more questions than answers, we can review it with you before the build starts.

Step 8: validate and report

Before go-live, we share templates early, validate each file with the client, and close with a data migration report. Checks include:

  • Customer and supplier balances match the old aged reports.
  • Stock quantities match the last physical count for each warehouse and company.
  • Stock value matches the accounting balance after opening entries.
  • A sample of products has the right packaging, unit of measure and costing method.
  • Open orders and their delivered quantities match the old system.
Financial and inventory reconciliation before go-live

The client signs off the report. Going live without that sign-off means discovering data problems in the first month of operations. Skipping validation is one of the mistakes we plan for.

Common migration mistakes

Common data migration mistakes and what to do instead
  • Leaving it to IT. Only the business can decide whether a balance or product is correct.
  • Migrating everything. Old transactions add cost and risk with little benefit.
  • Cleaning data after go-live. Duplicates and wrong units multiply once daily transactions start.
  • No trial run. The first full load should not be the final one.
  • No reconciliation. Stock and balances must be checked against the old system and signed off.

FAQ

Can I undo an import in Odoo?

No. Imports are permanent. Use Test first, and filter by creation date to find imported records [1].

How do I update records I already imported?

Export with the import-compatible option to keep External IDs, edit the file, and import it again [1].

Should the same product in different packaging be one item or several?

For stock and pricing accuracy, several. TAM’s design treats each packaging type as a separate item.

Should we migrate all our historical transactions?

Usually not. Migrate open items and what you need for current-year reporting, and keep the rest in the old system for reference.

How many trial migrations do we need?

At least one full trial into a test database before the final load. More if the trial shows many errors.

Plan migration before you plan go-live

If you are moving from spreadsheets or another system, start by listing your data types and designing your product master. We can review both with you. Read more about our Odoo implementation service.

References

[1] Odoo, Export and import data, Odoo 19.0 documentation. https://www.odoo.com/documentation/19.0/applications/essentials/export_import_data.html

[2] Odoo, Multi-company, Odoo 19.0 documentation. https://www.odoo.com/documentation/19.0/applications/general/companies/multi_company.html

[3] Screenshots: Odoo S.A., Odoo 19.0 documentation, Export and import data, licensed under CC BY-SA 4.0 (https://creativecommons.org/licenses/by-sa/4.0/). https://www.odoo.com/documentation/19.0/applications/essentials/export_import_data.html

  • Kawser Ahmed is the Founder & CEO of Softeko, a global IT consultancy with offices in Dhaka and Dubai. A tech entrepreneur, investor, and AI enthusiast, he has led numerous software and web projects, including the successful ExcelDemy.com. Kawser holds an Odoo 18 Functional Certification and has deep expertise in business process management, finance, SEO, and software development. He's also a Technical Analysis trainer at Dhaka Stock Exchange Ltd., with popular online courses on AmarStock.com and Udemy. A lifelong learner, Kawser explores how business, technology, and global markets work.

    View all posts

Want to write an article for our blog? Read our requirements and guidelines to become a contributor.

Leave a comment

Your email address will not be published. Required fields are marked *

Get Free Consultancy
Odoo Consultant
Get Free Consultancy
Book a meeting with an expert → Shafiuddin Haider, Odoo ERP Consultant
☰
Table of Contents