Skip to Content

Migrating an import company to Odoo in a single phase

We're moving the company to Odoo in one go, without months running two systems side by side. Before switchover day, its people test each area with their own data.
17 November 2026 by
Migrating an import company to Odoo in a single phase
OdooBot
Status
In progress
Sector
Import and distribution
Company size
SME
Business lines
Business solutions
Solutions
Migration to Odoo, Odoo implementation, Custom Odoo development
The challenge

Changing ERP without stopping a company that sells every day

The company buys abroad, in other currencies, and sells from its warehouse with very fast deliveries. It had used the same ERP for years and the time had come to replace it.

Changing area by area would have meant months with two systems at once, with duplicated data and reconciliations between them. The decision was to move the whole company to Odoo in one go.

  • Purchases in other currencies, with an incoterm and arrival date on each line
  • Freight costs built into the product cost
  • Sales commissions with their own rules
  • Years of history that didn't all need to come across
The solution

Everything in Odoo, including what makes an importer different

Standard Odoo where it's enough, and our own development where the company works differently.

Import purchasing

Orders in other currencies, with their incoterm, arrival dates and shipping documents. The freight cost is spread across the goods.

A warehouse with its own rules

Each item's minimum and maximum, brought over from the old system as replenishment rules, plus stock reservations for the sales team.

Sales, credit and commissions

Prices by customer and product reference. If a customer goes over their credit limit, the delivery waits, and commissions are calculated at invoicing.

Quality checks on receipt

A quality protocol for each supplier when goods are received. A bill that doesn't match what was received needs approval before it's posted.

Accounting from day one

The chart of accounts and the balances from the old system are loaded by script, and the load is rehearsed and reconciled account by account before cut-over.

How we're doing it

A single phase doesn't mean testing only once

The switch happens in one go, but the testing happens in parts. The work is split into milestones: purchasing, inventory and manufacturing in one, sales in another and accounting at the end. Each milestone comes with its own test guide, and the company tests it in a separate environment before signing it off.

Testing is done with their own data. We loaded the real stock from the old system into that environment. After a few days working with it, the operations team sent back their list of changes, which was what we needed from that round.

We bring across what's live: master data, stock and open balances. The full history is archived separately.

The opening stock doesn't come from the old system either. It comes from a physical count before cut-over.

This is how we carry out a migration to Odoo when a company can't afford to run two systems side by side.

Where it stands

In testing, on the way to switchover day

The project is under way. Purchasing and the warehouse are in the company's hands, in its test environment, and accounting is now being rehearsed against the balances from the old system.

The switch is planned for December 2026.

On switchover day, purchasing, the warehouse, sales and administration all start working in Odoo at the same time. There is no second system to keep running in parallel.

Been putting off changing your ERP?

Tell us what you work with today and what can't stop. We'll tell you whether you're better off switching in one go or area by area.