How do you replace the spreadsheet that runs your business?

Carefully, and with respect for the fact that it works. The spreadsheet running a critical part of your business survived because it fits how the work is actually done. Understand why before replacing it, choose something that keeps those strengths, migrate deliberately, and run both briefly before switching the old one to read-only.

Nearly every small business has one: the job tracker, the pricing model, the roster, the stock list, the file everyone opens each morning and nobody is allowed to break. It is usually built by one person, holds logic nobody has written down, and has grown well past what a spreadsheet was designed for. It is also, quietly, one of the most important systems in the business.

The risks are worth naming plainly, because the argument for replacement has to be more honest than a spreadsheets are bad slogan. There are no real permissions, so anyone with the file can see and change everything. There is no audit trail, so when a number is wrong nobody can say when or by whom. There is little validation, so a typo becomes data. Two people editing produces conflicts or lost work. And the knowledge lives with whoever built it, which becomes a business continuity problem the day that person resigns.

Against that, be equally honest about why it has survived, because these are real advantages and any replacement that loses them will be resented. It fits the process exactly, because it grew around the work rather than the work bending to it. It is instantly changeable by the person who uses it. It costs nothing. And everyone already knows how it behaves. A replacement that is more rigid, slower to adjust and requires a support ticket to change a column has lost more than it gained, however professional it looks.

So start by mapping what it actually does, and expect to be surprised. Who uses it and for what, what the calculations really are including the ones buried in cells nobody looks at, what the exceptions are, which decisions depend on it, and what happens today when someone gets it wrong. Have this conversation with the person who built it rather than around them, because their cooperation determines how this goes and their knowledge is the asset you are trying to make institutional.

Then choose between buying and building. Buy when a product exists for your job, since someone else maintains it, handles compliance and keeps it current, and most small-business processes are not as unique as they feel from the inside. Build, using something like Power Apps against data held in Microsoft 365, when the process genuinely is unusual or when the available products are far larger and more expensive than you need. The question that should decide it is who maintains the thing in three years, because a bespoke application dependent on one person has recreated the original risk in a more expensive form.

Migrate in a way that lets people trust the new thing. Run both in parallel briefly, with the spreadsheet as the reference, so anyone can check the new system is producing the same answers. Then switch the old file to read-only rather than deleting it, because a deleted file provokes anxiety and an editable one guarantees somebody keeps using it. Archive it properly once the new system has been through a full cycle, whatever a cycle means for that process.

One risk deserves separating out because it is rarely framed as a technology issue: the critical spreadsheet is usually a single file, and a single file is a single point of failure. Corruption, an accidental overwrite or ransomware takes it, and the version history you are relying on may be shorter than you think. Whatever you decide about replacing it, confirm today that it is backed up somewhere independent and that someone has actually restored a copy.

The honest caveat is that some spreadsheets should stay. A model one person uses to think with, a working calculation, a genuinely temporary list: these are fine and formalising them is bureaucracy. The ones worth replacing are those where multiple people depend on the same file, where the data matters to the business, and where losing it or corrupting it would hurt. If that describes one of yours, call 1800 456 567.