Moving off Excel and spreadsheets
The spreadsheet is the system, and everyone knows it
Every company has them: the file that decides pricing, the tracker that is the real project plan, the sheet that reconciles what two systems disagree about. They work, until the day they do not.
The short answer
Replace a spreadsheet when more than one person needs it at once, when a mistake in it is expensive, or when nobody can say who changed a number and when. Spreadsheets fail on concurrency, auditability and rules — not on capability. If it is one analyst modelling something once, leave it alone.
Signals
How you know it is time.
If more than two of these describe your week, the spreadsheets have already become the system.
- The file has a version number in its name, and there is more than one current version.
- Someone has to be asked before a change is made, because only they know what a column feeds.
- A wrong cell would cost real money and nothing would stop it.
- You email or WhatsApp it, and the copy people act on is not the copy you sent.
- The macro that makes it work was written by someone who has left.
Cost of staying
What it costs to change nothing.
The price of the migration is quoted. This is the price of the alternative, which never is.
No two people can work at once
This is the constraint that never gets designed around. Every workflow built on a shared file becomes a queue, and the queue is invisible in any report — it shows up as things being slow for reasons nobody can name.
There is no answer to “who changed this”
Version history in a cloud sheet is not an audit trail. For anything touching money, compliance or a customer commitment, the inability to reconstruct a decision is the actual exposure — and it surfaces during a dispute, not before.
Rules live in formulas nobody can read
A pricing policy or an approval threshold buried in nested formulas is a business rule that cannot be reviewed, tested or changed with confidence. It gets copied forward into the next file, errors included.
Method
How the migration runs.
- 01
Find the one that matters
There are always dozens and usually two that carry the business. We start from what breaks if the file is wrong for a day, not from what looks most complex.
- 02
Extract the rules before the data
The formulas are the specification, and they contain decisions nobody remembers making. Reading them out is often the first time the business sees its own policy stated plainly — and the first time it gets corrected.
- 03
Model the workflow, not the grid
A spreadsheet rebuilt as a web-based spreadsheet solves nothing. The value is in roles, states, validation and approvals — the things a grid cannot express.
- 04
Run alongside until trust transfers
The old file stays authoritative until the platform matches it for a full cycle. Trust in a number is earned by agreement over time, not by a go-live announcement.
How to decide
What makes staying on Excel and spreadsheets the right call.
Migrations are expensive to reverse. These are the conditions under which the switching cost outweighs what you would gain.
- One person uses it, occasionally, to model something that changes every time.
- It is genuinely ad hoc analysis — that is what a spreadsheet is for, and software is worse at it.
- The process is still changing weekly. Encoding an unstable process just makes it expensive to change.
- A packaged tool already does exactly this. Buy it.
Questions
What people ask before starting.
Next step
Thinking about moving off Excel and spreadsheets?
Bring the estate as it actually is, spreadsheets included. Forty-five minutes is usually enough to tell you whether it is worth doing and roughly what it would take.
- No sales deck
- An engineer on the call, not an account manager
- NDA before you share anything