When to replace a spreadsheet with real software
The moment a spreadsheet stops being a document and becomes a system: several people depend on it at once, it holds data not everyone should see, and the business would notice if it broke.
Here's how to tell which side of that line you're on, what a safe migration looks like step by step, what it costs, and when Excel is still exactly the right tool.
By Lucas Reddington, full-stack developer and AI engineer, Northbytes. Last updated .
Eight signs the workbook has become a system
None of these on its own means you need software. Three or more and you're maintaining an application without any of the things applications have: permissions, history, validation or backups you've tested.
Nobody is allowed to touch column K
There's a formula somebody wrote years ago that everyone works around and nobody understands. That's not a spreadsheet any more, it's undocumented software with no tests.
There are versions
Master, master_final, master_final_v2, and a copy on someone's desktop. When you can't say which one is true, the data has stopped being reliable and people have quietly noticed.
Everyone can see everything
Salaries, personal details, client records, all readable by anyone with the file. Under UK GDPR that's a data protection problem with the organisation's name on it, not just untidiness.
You can't tell who changed what
A number is wrong and there is no way to find out when it changed or who changed it. Version history in a cloud spreadsheet helps a little; it is not an audit trail.
Two people can't work at once
Or they can, and they overwrite each other. Either way you're paying people to coordinate around a file rather than to do the work.
The monthly report is a ritual
Someone spends a day copying, pivoting and formatting to produce numbers that could be a page anyone can open at any time.
It only works because one person knows how
If that person leaves, or is off for a fortnight, does the process stop? This is the risk nobody prices until it happens.
It broke, and it cost you
A missed order, a double booking, an invoice for the wrong amount. One incident usually costs more than the first phase of a system that would have prevented it.
When Excel is still the right answer
We build the replacements, so treat this as the section with the least incentive to be generous. Spreadsheets are extraordinary tools and there are four situations where nothing beats them.
One person modelling something. Budgets, forecasts, scenarios: anything where you're thinking rather than recording. A system would slow you down and add nothing.
Genuine ad-hoc analysis. A question you'll ask once, an export you want to pivot, a comparison for a board paper. Building software for this is absurd.
A process that's still changing weekly. If you don't yet know what the fields are, a spreadsheet is the cheapest way to find out. Build the system once the shape has settled, and use the workbook as the specification.
And anything small and low-stakes. A list of twelve suppliers, updated twice a year, that nobody depends on. Leave it alone.
A four-question risk check
Score your workbook honestly. Two yeses is worth a conversation; three or four means the spreadsheet is already a risk on your register, whether or not anyone has written it down.
- Do several people need it at the same time? Concurrency is the thing spreadsheets are worst at, and the workarounds cost real hours every week.
- Does it hold data that not everyone should see? Personal data, salaries, client records, anything special category. A file everyone can open is a breach waiting for someone to forward it to the wrong address, and the ICO's guidance on the security principle is unambiguous about access controls.
- Would you ever need to prove who changed what, and when? For anything touching money, compliance, safeguarding or a contract, the answer is yes and cloud version history is not enough.
- Does the business stop if it breaks or one person is away? If yes, you have a single point of failure with no support contract and no backup plan.
How a safe migration actually runs
Six steps, in this order. Skipping step four is the single most common reason a migration goes badly, and it's the one that costs nothing but patience.
1. Map what it really holds
Every column, what it means, who fills it in and what it feeds. This nearly always surfaces two or three columns nobody has used for years, and one that turns out to be load-bearing.
2. Map the decisions, not just the data
What happens when a value goes over a threshold? Who gets told? What are the exceptions? The rules living in someone's head are the real specification.
3. Clean as you move, not after
Dates in four formats, names with trailing spaces, three spellings of the same supplier. Cleaning happens once, during migration, with the rules written down so you can check them.
4. Run both in parallel
Two to four weeks with the spreadsheet still updated alongside the new system, and a weekly comparison. This is the step people want to skip and the one that catches everything.
5. Reconcile before you switch
Totals, counts and a sample of individual records checked against the old data by someone who knows what right looks like. Sign it off explicitly.
6. Freeze the old file, don't delete it
Read-only, kept for a defined period, then disposed of according to your retention policy. It's your fallback and, briefly, your evidence.
What you get that a spreadsheet can't give you
Permissions that mean something. People see the records their role needs and not the rest. Not a hidden column or a protected sheet, which anyone can get past, but access decided on the server before the data is ever sent.
An audit trail. Every change recorded with who, what and when, kept for as long as your retention policy says. When somebody asks why a figure changed in March, there's an answer rather than a conversation.
Validation at the point of entry. Dates that must be dates, required fields that are required, and references that have to point at something real. Most spreadsheet errors are typing errors that nothing prevented.
Reporting that doesn't need a person. The monthly ritual becomes a page anyone can open, current at all times, with the same numbers for everybody.
Backups you've actually tested. Automated, off-site, with a restore that somebody has proved works. A file in OneDrive is a copy, not a recovery plan.
Cost, and the sum to do before you commit
Replacing one departmental spreadsheet typically costs £5,000 to £12,000 with us: records, forms, permissions, exports, a reporting dashboard, an audit log and migration of your existing data, on a fixed quote agreed before anything starts. Hosting afterwards is £90 a month for a system with a database, including monitoring, backups, updates and fixes.
The payback sum is simple, and worth doing on paper. Count the hours a week your team spends on the spreadsheet that the system would remove: the coordinating, the copying, the monthly report, the chasing. Multiply by a realistic hourly cost and by 46 working weeks. Six hours a week at £20 an hour is about £5,500 a year, so a £7,000 system pays for itself inside eighteen months on time alone.
Then add the thing that doesn't appear in the arithmetic: the cost of one bad day. A double booking, an invoice for the wrong amount, a personal data breach that has to be reported. The European Spreadsheet Risks Interest Group keeps a public catalogue of organisations that found out the expensive way, and it makes for uncomfortable reading if your own workbook resembles any of them.
The full price bands are in the custom software cost guide, and if you're weighing this against buying a product instead, the bespoke versus off-the-shelf guide works through that decision, including the cases where we'd tell you to buy.
Common questions
When should we replace a spreadsheet with custom software?
When it has become a system rather than a document. The practical test is four questions: do multiple people need it at once, does it hold personal or sensitive data that not everyone should see, would you need to prove who changed what, and does the business stop if the file breaks or one person is away? Two yeses is worth a conversation. Three or four means the spreadsheet is already a business risk and the only question is timing.
Is Excel ever still the right answer?
Often, and we'd tell you so before quoting. Excel is excellent for one person modelling something, for genuine ad-hoc analysis, for a process still changing every week, and for anything you'll do a handful of times. It is unbeatable at flexibility. What it isn't is a multi-user system of record, and the trouble starts when a document quietly becomes one without anybody deciding that it should.
How much does it cost to replace a spreadsheet with a system?
A focused replacement of one departmental spreadsheet typically runs £5,000 to £12,000: records, forms, permissions, exports, a reporting dashboard, an audit log and migration of the existing data. That's our starting band and it assumes no integrations with other systems and one or two kinds of user. Add integrations, external users or several connected processes and you move into the £12,000 to £35,000 range. Every project is a fixed quote agreed first.
Will we lose data in the migration?
Not if it's done properly, and the safeguards are simple. The original file stays untouched and read-only as a fallback. The new system runs alongside it for two to four weeks with both being updated. Before you switch, totals, counts and a sample of records are reconciled against the old data by someone who knows what correct looks like, and you sign that off. If those steps aren't in a supplier's plan, ask why not.
How long does it take?
For a single spreadsheet replacement, six to eight weeks from first conversation to people using it, including the parallel-running period. Bigger jobs that consolidate several spreadsheets take longer and are better done one at a time, because a phased replacement gets value in front of people early and a big-bang cutover concentrates all the risk on a single day.
Sources
Figures quoted from outside Northbytes come from these sources, checked on 26 July 2026. Our own prices are our published rates.
Read next
Bespoke or off-the-shelf software?
Cost, fit, ownership, security and speed compared side by side, a ten-minute decision tree, and the four cases where we tell people not to build.
How much does custom software cost in the UK?
Price bands by system type, two worked examples with the assumptions stated, the day-rate arithmetic behind every quote, and a checklist for reading one.
What is actually worth automating with AI?
The workflows that pay back, the ones that don't, what it costs, how to handle your data properly, and a 30-day pilot plan you can run yourself.
Show us the spreadsheet
Walk us through the workbook everyone depends on. We'll tell you honestly whether it needs replacing, what would replace it, and what that would cost, with a fixed quote.
Get a free quote