Odoo Gold Partner for Nigeria · Offices in Lagos and AbujaClient supportadvisors@growthstack.gs+234 913 842 1230

Moving from Spreadsheets to Odoo: Data Migration Without Losing Your History

Finance team comparing spreadsheet figures with a new ERP system on screen

"We'll lose five years of history."

It is one of the most common reasons we hear for putting off an ERP project. The finance team has years of invoices, payments and stock movements in spreadsheets, QuickBooks, Sage or an older local system. Moving to Odoo feels like starting from zero.

It doesn't have to be. A well-planned migration keeps what you need, archives what you don't, and gives you opening balances that match your old system to the naira. This article explains how.

What usually moves, and what doesn't

Not everything in your old system needs to come into Odoo. It helps to think of your data in three groups.

Master data

These are the records everything else depends on:

  • customers and suppliers, with contacts, addresses and TINs
  • products and services, with codes, units of measure and prices
  • your chart of accounts
  • employees, if HR or payroll is part of the project

Master data always moves. It is also where most of the clean-up work happens.

Opening balances

These are the figures that let you carry on trading from day one:

  • the trial balance at the cut-over date
  • open customer invoices and supplier bills, so you can still collect and pay them
  • stock on hand by warehouse, and by batch or serial number where you track them
  • fixed assets, with their cost and accumulated depreciation

Opening balances always move, and they must reconcile with the old system before anyone signs off.

History

History is a choice, not a requirement. Most businesses bring summarised monthly balances into Odoo, so year-on-year reports still work, and keep the full transaction detail in the old system or an archive for reference and audit.

Bringing years of individual transactions into a new system is possible, but it is slow, expensive and rarely worth it. Old transactions were recorded under old codes, old processes and sometimes old mistakes. Summaries give you the comparisons you need without importing those problems.

A step-by-step approach

1. Clean the data before you move it

Migration is the best chance you will get to tidy up. Typical clean-up work includes:

  • merging duplicate customers and suppliers
  • retiring products and accounts that haven't been used in years
  • fixing inconsistent units of measure and product codes
  • filling in missing details such as TINs, phone numbers and email addresses

Data that is moved dirty stays dirty. It is much harder to fix once it is live.

2. Map old codes to new ones

Your Odoo chart of accounts, product categories and warehouses may not match the old system exactly, and often shouldn't. Each old code is mapped to its new home in a simple spreadsheet that the finance team reviews and agrees. The chart of accounts deserves the most care, because every report you run afterwards depends on it.

3. Use templates and test imports

Data goes into Odoo through import templates, one for each type of record. Each import is run first in a test database, never straight into the live system. Errors are fixed in the source file and the import is run again until it loads cleanly.

4. Reconcile to the naira

Before go-live, the figures in Odoo must match the old system at the cut-over date:

  • the trial balance, account by account
  • debtors and creditors, in total and by customer and supplier
  • stock value, in total and by warehouse

If a figure doesn't match, the difference is found and explained before anyone moves on. This is the step that gives the finance team confidence in the new system.

5. Plan the cut-over

The final move is usually done over a weekend or at month-end, so day-to-day work isn't disrupted. Closing balances are taken from the old system, imported into Odoo, reconciled and signed off.

The old system is then kept read-only for a period, so people can look things up but can't post new transactions. That way there is only ever one live set of books.

Moving from specific systems

Excel and other spreadsheets. The data is usually all there, but spread across many files with different layouts. Most of the work is gathering, cleaning and standardising it into the import templates.

QuickBooks and Sage. Customers, suppliers, products, the chart of accounts and balances can be exported from both, usually as CSV or Excel reports. These exports are then cleaned and mapped like any other source. The details depend on your version and how it has been used. If you are still deciding whether to switch, see QuickBooks, Sage or Odoo?.

Older local or custom software. Here the first question is how to get the data out. Most systems can produce reports or exports. Where they can't, the data may need to be extracted from the database, or the balances rebuilt from reports. We look at this early, because it affects the timeline.

In every case, migration is a process of exporting, cleaning, mapping, test importing and reconciling, not a single button.

A checklist for your migration

  • Agree which history comes across as summaries and where the full detail will be kept.
  • Name a data owner in finance, and one for stock, for clean-up and sign-off.
  • Clean customers, suppliers and products before the first test import.
  • Agree the chart of accounts mapping in writing.
  • Run at least one full test migration in a test database.
  • Reconcile the trial balance, debtors, creditors and stock value.
  • Fix the cut-over date and plan the weekend.
  • Make the old system read-only after go-live, and decide how long to keep it.

The sign-off your finance team should insist on

Before go-live, the finance lead should sign a short statement confirming that the opening trial balance, debtors, creditors and stock value in Odoo match the old system at the cut-over date, with any differences explained. If the figures can't be signed off, the system isn't ready.

Data migration is one of the main things that sets an implementation timeline, which we cover in How Long Does an Odoo Implementation Take?.

Talk to us

If worries about your data are holding back a move to Odoo, book a free consultation. We'll look at where your data lives today and show you how it would come across, what to archive, and how long it would take.

Thinking about Odoo for your business?

Talk to a Growth Stack consultant about your processes, timeline and budget. The first consultation is free.

Book a free consultation

Keep reading