Article
The risk in switching ERPs is almost never the new software. It's in go-live week and in the quality of the data you bring over.
Moving to a new ERP is less like installing a program and more like moving house: the expensive part isn't the truck, it's deciding what to take and what to throw out.
| Data | Usual decision | Why |
|---|---|---|
| Customers and vendors | Migrate, cleaning out duplicates | They are the foundation of all commercial operations. |
| Products and catalog | Migrate, standardizing units of measure | A dirty catalog ruins inventory, costing and reports. |
| Chart of accounts | Redesign, don't copy | It's the chance to fix a structure that grew by accumulation. |
| Opening balances | Migrate as of the cutover date | It's the bare minimum for the books to close. |
| Accounts receivable and payable | Migrate document by document | Without the detail you can't manage collections or reconcile payments. |
| Inventory | Migrate from a physical count, not the system balance | Starting with wrong inventory contaminates the whole year. |
| Transaction history | Usually don't migrate | The old system is kept in read-only mode. Migrating history costs a lot and gets little use. |
The rule that prevents the most headaches: data gets cleaned before migrating, not after. And your team does the cleanup, because they're the ones who know which of the three "Distribuidora del Valle" records is the right one.
Pick the start of an accounting period, preferably the start of the fiscal year. Two weeks before, freeze changes to master data in the old system; in the final week, do the physical inventory count; the weekend before, load the final balances. On Monday you invoice in the new system, and the old one stays available for reference only.
No amount of prior testing replaces the first month-end close and the first inventory in the new system. That's where the odd cases show up: the credit note against a document from the old system, the inventory adjustment nobody anticipated, the tax report that asks for data that wasn't migrated. That's why support has to cover the first close, not end on go-live day.
The rest of the method is in how we implement Odoo, and if you're still evaluating platforms, in Odoo vs. SAP Business One.
The start of an accounting period, ideally the fiscal year, because it simplifies opening balances and avoids splitting the year across two systems. The second-best option is the start of a month with a light operational load. Going live in peak season is the decision that has derailed more projects than any other.
A full parallel run is usually a bad idea: it doubles your team's workload in the most demanding week and creates two versions of the truth. What does make sense is keeping the old system available in read-only mode for several months.
A 30-minute conversation is enough to know whether Odoo, automation or an integration will solve your problem — and what it would cost to do it right.