From Spreadsheets to ERP: When to Switch and How to Prepare

Excel is a great tool. The problem is not Excel itself, but what you are asking it to do. Here are five situations we see at companies before they make the switch.

1. Data is retyped between spreadsheets manually

An order arrives by email. Someone retypes it into Excel. From Excel it gets retyped into accounting. Shipment information from the warehouse gets copied back into Excel. Every retype is a chance for error. At one client we counted four separate systems with data moving manually between all of them: spreadsheets, Google Docs, an internal app and transport software.

2. Nobody knows which version of the file is current

Pricelist_v3_FINAL_really_final.xlsx. Stock levels someone updated yesterday but saved in a different folder than the one the sales team is working from. At manufacturing companies we have seen recipes in Excel where changing one number affected production - and nobody knew who changed it or when.

3. Reporting takes days instead of seconds

The CEO wants to know margins for the last quarter. The accountant spends two days pulling data from different spreadsheets, copying and assembling. The result is a PDF that is outdated the moment it is sent. In an ERP this takes 30 seconds.

4. Errors are discovered too late

The accountant calls because the numbers do not add up. The warehouse reports that items expected to be in stock are missing. An invoice went out with the wrong price because someone edited the price list and forgot to save the right version. Excel has no audit trail - you do not know who changed what and when.

5. New hires cannot get up to speed

Processes live in people's heads, not in the system. When a key employee leaves, their knowledge of how the order process works, where each spreadsheet lives and which formula must not be overwritten leaves with them. An ERP enforces standard procedures - a new person gets up to speed in weeks, not months.

The most common mistake: a company starts by selecting an ERP. They sit through three demos, pick a system based on how it looks and then discover it does not cover what they need. The right approach is the opposite.

Write down what everyone does

Who receives orders? Where do they come from (email, phone, e-shop, EDI)? Who enters them into the system? Who checks inventory? Who issues invoices? Who handles complaints? You do not need formal documentation - a list of steps and who is responsible for what is enough.

Find out where data flows

Draw a simple diagram: order → stock check → dispatch → invoice → payment. At each step write down where the data currently lives (Excel, email, paper, someone's head).

Measure how much time you spend retyping

For one week, track how many minutes per day you spend copying data from one place to another. At the companies we work with, this typically runs 2-4 hours per day per person - 40 to 80 hours a month that an ERP eliminates entirely.

Identify where Excel is enough

Not everything needs to be in an ERP. Ad-hoc analyses, project budgets, internal planning - Excel works fine for these. The goal is not to get rid of Excel, but to move operationally critical data into the ERP: warehouse, orders, invoicing, production.

10 questions before your first meeting with a vendor

1. How many people will use the system daily?
2. Where do orders come from? (email, e-shop, EDI, phone)
3. How many invoices do you issue per month?
4. Do you have a warehouse? How many items, how many locations?
5. Do you need manufacturing or production planning?
6. Do you deal with batches, expiry dates, FEFO?
7. Do you export to the EU? (VAT, Intrastat, OSS)
8. Do you have an e-shop or B2B portal that needs to connect?
9. Who handles accounting today? (in-house, outsourced)
10. What is the biggest pain point you want to solve first?

This list is not an academic exercise. We use it as the foundation for process analysis on our projects. It helps both us and the client understand what matters and where to start. The better you map the current state up front, the fewer surprises arise during implementation.

ERP implementation is not a flip-the-switch project. It is a gradual change done in phases.

Phase 1: Must have

Core functions to keep the business running. Goal: replace spreadsheets where it hurts most. Typically: order intake, warehouse management, invoicing, bank integration. This can be up and running in 3-6 months.

On one project we started this way with a B2B portal for a distribution company (name withheld). Phase 1 covered customer registration, order entry with validation (the system blocks prohibited product combinations), proforma invoices and basic warehouse management. The company could operate without spreadsheets and manual retyping.

Phase 2: Nice to have

Automation and convenience. Online payments, automatic invoice matching, mobile warehouse scanning, EDI communication with suppliers, AI document processing. These increase efficiency but are not required for basic operations.

Why phase it

• Lower risk - you are not changing everything at once, the team learns as you go
• Faster payback - you see the first savings in months, not a year
• Better decisions - after phase 1 you know what you actually need in phase 2
• Less burden on the team - people do not have to learn everything at once

From our projects, we know where the transition to ERP gets complicated most often.

1. System chosen based on a demo, not processes

Demos always look convincing - a prepared scenario, everything works with one click. But your company has specific processes that were not in the demo. It pays to map what you need first (see section above) and only then look for a system that covers it.

2. Migrating all data at once

Naturally you want to transfer the full history. But 10 years of data from Excel means months of cleaning and import debugging. More practical: migrate only what you need for operations - active customers, current price list, open orders. Keep history as an archive.

3. No one is making decisions

Every process needs one person on the company side who says "this is how it will work." Without clear ownership, the implementation team waits for answers and the project stalls.

4. Too much scope on day one

ERP, B2B portal, mobile app, EDI and e-shop integration - all of it makes sense, but not on day one. Starting with a smaller scope, getting it running and expanding based on real experience has worked well for us.