Excel is not the enemy

Let us be fair to the spreadsheet.

Excel is flexible, fast and understood by everyone. Most successful businesses ran on it for years. If your company grew on spreadsheets, they were doing something right.

The problem is not that Excel is bad. The problem is what happens when a business gets bigger than one person’s attention.

Two people open the same file. Somebody keeps a copy on their desktop. A formula gets overwritten and nobody notices for a month. The stock sheet and the invoice sheet slowly stop agreeing, and nobody can say which one is correct.

That is the moment to move.

Before you touch any software

Skip this section and your project will take twice as long. Every experienced implementer will tell you the same thing.

Find every spreadsheet

Not the ones you know about. All of them.

Ask each person what they keep on their own machine. You will almost always find files nobody mentioned — a pricing sheet the sales lead maintains privately, a delivery tracker in the warehouse, a commission calculation somebody built years ago.

These matter. They usually contain a business rule that exists nowhere else.

Decide which one is the truth

If three files list your products, one of them is right and two are stale. Decide now, while it is a calm conversation, not later during data import when everyone is under pressure.

Write it down: this file is the master for customers, this one for products, this one for prices.

Write down the rules hiding in formulas

Spreadsheets carry business logic that has never been written in words.

Look at the formulas. That nested IF calculating a discount is a pricing policy. That lookup table is a customer tier structure. That manual adjustment somebody makes every month is a rule nobody documented.

Get these into plain sentences before configuring anything. This document is the single most useful thing you can hand an implementation partner.

Cleaning the data

This is the unglamorous part, and it is where most of the real effort goes.

Fix duplicates. “ABC Trading”, “ABC Trading Ltd” and “abc trading” are three customers in a spreadsheet and will be three customers in Odoo unless you merge them first.

Standardise units. If some products are listed in pieces, some in boxes and some in kilograms, decide the rule now. Unit of measure is one of the hardest things to change later, once you have transaction history.

Complete the required fields. Odoo will need a customer name, and for accounting it will want proper tax details. Blank cells that Excel tolerated will be rejected.

Drop what you do not need. You do not have to import ten years of history. Usually open balances, current stock and active master data are enough. Old history can stay in the spreadsheets, archived and read-only.

What to import, in what order

Order matters. Each step depends on the one before it.

1. Master data first. Customers, suppliers, products, product categories, units of measure, chart of accounts. Nothing else can be imported until these exist.

2. Opening balances. Customer balances, supplier balances, and your opening trial balance. Your accountant should agree these figures before they go in.

3. Opening stock. Current quantities and their values, by location. Do this as close to go-live as possible so it does not drift.

4. Open transactions. Sales orders and purchase orders that are still in progress. Completed ones from before go-live usually do not need to come across.

Odoo imports from CSV or Excel files directly, and it can match records by an external ID. Use those IDs — they let you re-run an import to update records instead of creating duplicates.

Test before you trust

Never import into your live database first.

Import into a test database. Then run real transactions through it: a full sales cycle, a full purchase cycle, a stock adjustment, an invoice, a payment.

Take five real orders from last month and process them in the test system. Compare the result with what actually happened. If the numbers match, your setup is sound. If they do not, you have found a configuration problem while it is still cheap to fix.

Going live

Two approaches. Pick one deliberately.

Clean cut. Pick a date, usually the start of a month. Everything before it stays in the old spreadsheets. Everything after it happens in Odoo.

This is simpler, and it is what most small businesses should do. There is no ambiguity about where a transaction lives.

Parallel run. Run both systems for a period and compare.

This sounds safer and is often worse. It doubles the work for your team at exactly the moment they are learning something new, and people quietly fall back to the spreadsheet because it is familiar. If you do run parallel, keep it short and set a firm end date.

The mistakes that cost the most

Trying to recreate the spreadsheet. People ask for Odoo screens that look exactly like their old sheet. Resist this. You are not buying a prettier spreadsheet, you are buying a connected system. Some things will work differently, and usually better.

Importing everything. Ten years of history brings ten years of bad data with it. Import what you need to operate.

Skipping training. People who do not understand a system will keep a spreadsheet on the side. Then you have both, and neither is trusted.

Nobody owning it. There must be one person inside your company who owns this project and makes decisions. Not the consultant. Someone who knows how the business really works.

What good looks like

Six months after a successful move, the signs are simple.

Nobody is keeping a private spreadsheet. Questions about stock and margin get answered in a minute. Month-end is a review rather than an investigation. And when somebody asks where a number came from, there is one clear answer.

That is the whole point. Not fancier software — one version of the truth.