There is a spreadsheet. It has been going for years. It holds the jobs, or the stock, or the bookings, and everyone knows the one where you have to be careful with column H.
It works. That is the awkward part of this conversation, and it is why the honest answer is not simply to replace it.
Why it got this far
Spreadsheets win because they ask nothing of you. No project, no specification, no budget approval. Someone needed to track something on a Tuesday and by Friday it existed.
They also shape themselves to how you actually work rather than how software imagines you work. Most business software is worse at that than a spreadsheet, which is a genuine criticism of the software rather than a compliment to the spreadsheet.
So it is not stupidity that got you here. It is a series of reasonable choices, and it is worth saying so before listing the problems.
Where it actually goes wrong
Not the things people list in sales pitches. These four.
- Two people, one file. The moment a second person needs it at the same time you get copies, and the moment you have copies you have two versions of the truth and no way to tell which is right.
- Nothing stops a bad entry. A date in a quantity column, a supplier name spelled three ways, a formula overwritten by someone pasting. No warning, and the error surfaces weeks later inside a total nobody questions.
- No history. When a number is wrong you cannot see who changed it or when. Not for blame, but because you cannot fix what you cannot trace.
- It knows things only one person knows. The colour coding means something. Rows below 400 are archived. That knowledge lives in a head, and it walks out on their last day.
The fourth is the real risk. Everything else is friction; that one is a single point of failure with a notice period.
The signals it has outgrown itself
Not the size of the file. These.
- Someone spends real time each week tidying it rather than using it.
- There is a second spreadsheet that reconciles the first.
- People message each other to ask whether it is safe to open.
- A customer has been given wrong information from it more than once.
- Only one person is trusted to make changes.
One of these is normal. Three is a business running on something that will eventually let it down at the worst possible moment.
The honest fix, in order
The instinct is to commission a system. Resist it for a moment, because there are cheaper steps that solve most of it.
Move it somewhere shared and versioned. If it is emailed around or sitting on one machine, putting it in SharePoint or OneDrive removes the copies problem and gives you history, for nothing.
Add validation. Dropdowns instead of free text, restricted formats, protected formula cells. An hour of work that prevents most bad data.
Separate entry from storage. The single biggest improvement available without building anything much. A simple form writing into a list means people add records without ever touching the structure.
Then, if it still hurts, build. By this point you know exactly what it needs to do, because you have been running it for years. That makes the build cheaper and far more likely to fit.
Most businesses stop after step three and are fine. For those that go further, a SharePoint list is often the right destination rather than a database, and it avoids the licensing questions that come with reaching outside Microsoft 365.
The one thing not to do
Do not rebuild it exactly as it is.
Spreadsheets accumulate workarounds for problems that stopped existing years ago. A faithful reproduction preserves every one of them in something now much harder to change. The point of moving is to lose the workarounds, and that requires asking what each column is actually for, which is uncomfortable and always worth it.
The honest summary
A spreadsheet doing a job well is not a problem to be solved. A spreadsheet that only one person understands, that two people cannot use at once, and that has already given a customer wrong information, is a risk with a timeline.
Try the cheap steps first. They fix more than people expect, and if they are not enough you will know precisely what to build.
If there is one holding your business together and you are not sure whether it is fine or a problem waiting, describe what it does and who touches it. That is usually enough to tell.
Where this leads
Almost every internal system starts as a spreadsheet, so almost everything else on this site starts here. These are the next steps in roughly the order they come up, including two accounts of what breaks once you have built something and started depending on it.
Common questions
When has a spreadsheet actually outgrown itself?
Not when it gets big. When someone spends real time each week tidying it, when a second spreadsheet exists to reconcile the first, or when a customer has been given wrong information from it more than once.
What is the cheapest fix?
Move it somewhere shared and versioned, add validation, and separate entry from storage with a simple form. Most businesses stop there and are fine, having built nothing.
Should we rebuild it exactly as it is?
No. Spreadsheets accumulate workarounds for problems that stopped existing years ago, and a faithful reproduction preserves every one of them in something now harder to change.