The spreadsheet is not the problem. The fourth copy is.

Spreadsheets are one of the best pieces of software ever made. They are flexible, everyone knows how to use them, and they let a business try a process before committing to it. Blaming them for operational chaos is like blaming paper for bad handwriting.

What actually goes wrong is duplication. The first copy of a spreadsheet is a tool. The fourth copy is a disagreement waiting to happen.

How it happens

It usually follows the same pattern. A team creates a sheet to track something the main system does not handle. Another team needs the same data with a slightly different view, so they copy it. Someone downloads it to add a column for their own purposes. Now there are several versions, each updated at different times, each with slightly different definitions.

Soon the meeting that should be about decisions is spent arguing about whose numbers are right.

The question to ask

For every important piece of data (an order, a SKU, a customer, a batch), ask: where is the one place this is true? If the answer is “it depends” or a list of places, that is the problem to solve. Whether the true place is a spreadsheet, a database or an app is a secondary decision.

When a spreadsheet is still the right answer

• —A small team, one copy, clear ownership
• —The process is still changing and you are learning what you need
• —Nobody downstream depends on it being correct in real time

When to move to a tool

• —More than one person edits it and edits collide
• —You need permissions: some people should see or change only part of it
• —Other systems need to read from it or write to it automatically
• —It is used on a phone, tablet or the shop floor
• —Rows have lifecycles (draft, approved, shipped) with rules about who can move them
• —The sheet has become slow, or is held together with complex formulas one person understands

A migration that does not disrupt the team

1. 01Agree the definitions first. What exactly is a batch, an order, an active customer?
2. 02Pick the one canonical home for the data
3. 03Build the tool around how people already work, including the columns they rely on
4. 04Run the old sheet and new tool side by side for a short, fixed period
5. 05Make the sheet read-only, then retire it

If your team has outgrown the sheet, that is the moment for an internal tool built around the work, not an idealised version of it.