The spreadsheet still works. That is what makes it hard to replace.

What it costs to leave it alone

A spreadsheet operation rarely fails dramatically. It charges a weekly tax instead: the hour spent rebuilding the Monday report, the exception nobody caught because it lived inside a filter view, the customer who found the mistake first, and the fact that one person can explain the file and nobody else can. None of it appears on a line item, and all of it is paid every week.

Signals to look for

None of these is decisive on its own. Three or more together usually is.

• One row is doing several jobs

  A single line holds the customer, the order, the shipment and the invoice, because splitting them would break the formulas. Any question that crosses those objects now needs a person to answer it.

• Formula chains carry production logic

  A pricing rule, an eligibility check or an approval threshold lives inside a nested formula or a cross-file link. Google's own guidance names heavy calculation and cross-file references as the usual causes of slow, unstable sheets — and when those chains are also your business rules, a recalculation problem becomes an operations problem.

• People copy tabs to freeze something

  Month-end, a big customer, an audit: the way to protect a number is to duplicate the sheet. Now several versions of the truth exist, with no rule for which one wins.

• The real approval happened somewhere else

  The sheet records the outcome, but the decision was made in a chat thread. Six months later you can see that the value changed, and not who agreed to it.

• Access is managed by hiding things

  Columns get hidden, tabs get protected, and a second client-facing copy of the file gets maintained by hand. Every one of those is a permission rule that a human has to remember to apply.

How to evaluate it

Five steps, in order. Each one produces something you can put in front of other people rather than an opinion you have to defend.

1. 01

   Name the objects hiding behind the tabs

   Write down the real things your business tracks: customer, job, shipment, invoice, technician. Any tab holding more than one of them is a table that has not been split yet. That list is the actual scope of the work.

2. 02

   Separate workflow state from reporting

   Reporting can stay in a spreadsheet indefinitely, and usually should. What has to move is the state: where a job is, who owns it, what happens next. Confusing the two is what makes a migration feel enormous.

3. 03

   Write your access rules as sentences

   "A project manager sees their own clients. Finance sees every invoice and no salary column. The client sees their own jobs and nothing else." If a sentence cannot be expressed by hiding a column, you need a system that understands records.

4. 04

   Follow one exception end to end

   Take a genuinely awkward case — the rush order, the partial delivery, the client who pays differently — and trace every message, copy and manual fix it caused. Exceptions, not the happy path, are what a spreadsheet cannot hold.

5. 05

   Move one flow, not the file

   Choose the single flow with the most manual handoffs and move only that, keeping the spreadsheet alongside until the new one is trusted. A big-bang rewrite of a file this central is the version that fails.

Common questions