How companies end up with four ERPs
Nobody plans it. A company grows, acquires a competitor, buys a supplier, opens a new division — and each one arrives with its own system. Soon month-end means exporting from four places, reconciling in Excel, and hoping the consolidation adds up.
Moving everything onto one NetSuite account fixes that — if it's done in the right order. These lessons come from an engagement where four ERPs were replaced in a matter of months.
Lesson 1: Design the company structure first
Before a single record is migrated, decide how the business is modelled: which legal entities become subsidiaries, how locations are set up, and what departments and classes you'll report on. In NetSuite OneWorld these choices drive intercompany, consolidation, security and reporting — and they're painful to change later.
Lesson 2: One chart of accounts, agreed before migration
Four systems means four charts of accounts, each with its own logic. Map them to one harmonized chart before migrating balances. Push detail that doesn't belong in the GL — like customer type or product line — into segments such as class and department, rather than creating hundreds of accounts.
Lesson 3: Clean the item master once
The same part often exists under different numbers, descriptions and units of measure in each system. Agree a naming convention, de-duplicate, and standardize units of measure up front. A clean item master is the foundation for costing, purchasing and every inventory report you'll ever run.
Lesson 4: Migrate in waves
| Approach | Works well when | Watch out for |
|---|---|---|
| Big bang (all at once) | Entities are small and processes are similar | High risk; one problem affects everyone |
| Waves (entity by entity) | Entities differ, or teams are stretched | Temporary intercompany between old and new systems |
Waves usually win: the first entity proves the design, and every later wave goes faster because the templates, data loads and training already exist.
Lesson 5: Learn the business, not just the system
The fastest consolidations aren't led by whoever knows the most NetSuite features. They're led by people who sit with the warehouse, purchasing and accounting teams, understand why each process exists, and then design the system to fit — spotting improvements along the way instead of copying four sets of old habits.
Lesson 6: Train the people who will own it
Every wave should leave behind a few internal experts who can answer everyday questions. Load the data with them, train users with them, and hand over documentation they helped write. That's what keeps the system healthy after the consultants leave.
Want a second opinion on your system?
Book a free 30-minute ERP health check. A senior consultant will look at your setup and give you three practical next steps.
Book a consultation