01. The signals that a spreadsheet has reached its limit
None of these is serious on its own. It is their accumulation that shows the cost of the current tool has overtaken the cost of changing it.
- Two versions of the same file are circulating, and nobody knows which one is authoritative.
- The stock on file differs from the stock on the shelf, and the gap surfaces at the annual count.
- The same order is entered into the quote, the invoice and the accounts.
- One person is indispensable: only they know where the formulas are.
- Monthly reporting takes several days of retyping.
- A file has grown so heavy it takes a minute to open.
02. What waiting actually costs
The cost of a spreadsheet is invisible because it is spread thin: it appears on no invoice. It is measured in hours of typing, in errors corrected after the fact, in decisions taken on stale figures, and in dependence on one person.
The calculation is simple to set up, though. Count the hours spent each month retyping, reconciling and checking; multiply by a loaded hourly cost; add what the last stock or invoicing error cost you. That figure, obtained in an hour, is what an ERP has to repay.
It is also what makes a return on investment demonstrable later. Without a baseline, no improvement will be provable — only asserted.
03. Migrating without stopping the business
The main fear is not the budget, it is the shutdown. A well-run migration never requires switching everything at once: it starts with the scope whose gain can be measured, then extends.
Your current files are not thrown away. They are analysed, cleaned, and the discrepancies found are shown to you before the switch — often the moment you discover two departments were counting differently. That discovery has value in itself.
For a period, old and new coexist. That is normal and healthy: trust in a new system is built by checking it says the same thing as the old one, before the old one is closed.
- Map what runs today, exceptions included.
- Clean and import the data, with gaps shown before switching.
- Start on a measurable scope rather than on everything.
- Let old and new coexist through the verification period.
- Train the teams before, not after.
04. What spreadsheets will still do better
An ERP does not replace spreadsheets, and pretending otherwise sets up a disappointment. A spreadsheet remains the fastest tool for a one-off analysis, a simulation, a table you throw away after use.
What changes is the source: instead of being the company’s memory, the spreadsheet becomes an analysis tool, fed by data that lives elsewhere and that nobody has to retype. That is often the moment teams stop resisting the migration.