Odoo IntegratorDevelopment and integration

Blog

Planning an Odoo data migration

What to bring into Odoo on day one, how to rehearse the load, and how to reconcile the figures before anyone depends on them.

By Alfatih Ridho NT2 min read

  • migration
  • data

A migration is a design problem before it is an import problem. Ask which records your team needs in order to sell, buy, stock, and account on the first Monday. The archive of every past transaction is a different question, and it usually has a different answer.

Bring what the first week will post against

Plan to load active partners, products, the chart of accounts, taxes, price lists, open sales and purchase orders, stock on hand, and opening balances for customers, vendors, and the bank. Load history when a report or a legal duty requires that history to live inside Odoo. Otherwise leave it in the old system, in a read-only export, where it can still be looked up.

This choice keeps the new database small enough to understand. It also keeps the project from spending its testing time on invoices that will never be paid again.

Clean the master data before the first trial

Duplicates, competing units of measure, products with no category, and partners with three spellings of the same tax number will all survive a careless import. Fix them in a working sheet before they become records. Agree the units, the product categories, and the rule for a customer who is also a vendor. Those decisions are cheap in a spreadsheet and expensive inside a live database.

Map the accounts, taxes, and locations

A chart of accounts is rarely copied line for line. The old structure and the structure you want in Odoo are allowed to differ, and the mapping between them is a document with an owner. Do the same for taxes and for warehouses. A receipt that lands in the wrong location will make the stock figure and the balance sheet disagree, and the import file will not be the place you notice it.

Rehearse on a copy

Run at least one full trial load against a copy of the Odoo database. Then reconcile. Stock quantities and stock value. Open receivables and payables. Bank and cash. The trial is finished when a person from the business, not only the person who built the file, can explain the differences.

Keep the import files. The cutover load should be the same files with a dated delta, not a new invention produced over a weekend.

Freeze, then cut over

Write the freeze. Name the hour when the old system stops accepting new orders, who may still correct a master record, and how the transactions that slip through are loaded. A migration without a freeze window is two systems telling two stories about the same afternoon.

After the load, post a small set of real transactions with the people who will do that work on Monday: a sale, a receipt, a vendor bill, a payment. The reconciliation from the trial, plus those transactions, is the evidence that the data is ready.

Leave the structure alone during the load

A migration does not repair a chart of accounts the business has outgrown. If the structure needs to change, that change is a design decision made before the templates are built. Changing it between the trial and the cutover throws away the reconciliation you just earned.