Have stock, orders and production lived in Excel for years? A step-by-step plan for moving to an ERP without stopping the business or losing the team.
Every business has a “big Excel file”. It’s usually called something like stock_final_FINAL_v2.xlsx, only two people know how it works, and when those two take the same day off, things slow down. That’s usually the day the idea of an ERP is born.
The good news: you don’t have to stop everything to switch. The bad news: if you try to change everything in one weekend, things really might stop.
1. Draw the map first, not the software
The first job isn’t designing screens. It’s writing down how the work actually flows today. Where do orders come from, who approves them, where does stock drop, when is the invoice issued? Drawing this usually reveals two things:
- The same information is kept in three places, in three slightly different forms.
- One step only works because “Ahmet knows how”.
Those two are the first problems an ERP will solve.
2. Start with the module that wastes the most time
An ERP isn’t one package, it’s a series of modules. Instead of switching them all on, start where it hurts most. For most small businesses that’s stock; for service companies it’s often orders and invoicing.
| Symptom | Module to open first |
|---|---|
| Sales and warehouse quote different stock numbers | Stock and warehouse |
| Orders get lost in email and phone calls | Order management |
| Production order is re-argued every morning | Production orders |
| Month-end closing takes days | Accounts and invoicing |
3. Clean the data before you move it
Pouring old data into a new system as-is is like moving a messy house in boxes: new house, same mess. Before importing:
- Merge duplicate product and customer records.
- Tie product codes to a single rule.
- Let go of the columns kept “just in case” that nobody ever opens.
4. Run both systems side by side, briefly
When the first module goes live, keeping Excel open read-only for a few weeks reassures the team. When the numbers match, trust arrives; when trust arrives, Excel closes itself. The rule is simple: new data goes into the new system only.
5. Bring the team in early
Test screens with the people who will use them every day. A warehouse colleague asking “why is this button here?” is worth more than ten decisions made in a meeting room.
An ERP is worth exactly as much as the manual work it removes. If it adds a new form to fill in, something has gone wrong.
Quick checklist
- Is the workflow drawn?
- Is the first module chosen?
- Is the data cleaned?
- Are the switch week and the people responsible set?
- Is it written down what will be measured after the first month (counting time, error count, closing time)?
If you have a lot of “no” answers, that’s fine; that’s exactly why we plan. Describe how your business runs today in the quote form and we can pick the first space together.