Spreadsheet alternatives
The spreadsheet is not the problem. Being the only system is.
Replacement paths for the spreadsheets that quietly became infrastructure — the tracker, the pipeline, the reconciliation, the roster. What to keep, what to move, and how to migrate without losing the rules nobody wrote down.
Rules first
The undocumented logic is elicited before anything imports
Parallel
Both systems run until the replacement is trusted
Archived
The original is kept read-only, never deleted
Introduction
Why the spreadsheet won in the first place.
A spreadsheet that has run a process for nine years is not a failure of discipline. It won because it was available on the day the need appeared, it fit exactly, and it changed as fast as the process did. Any replacement has to be honest about giving up two of those three.
What it cannot do is the reason to move: no access control, no audit trail, no concurrency, no retention policy, and no way to recalculate a chain when an underlying rule changes. When the file holds regulated or customer data, those absences stop being inconveniences.
The pages here take one common spreadsheet each and describe the replacement in the terms that actually decide whether it works — what the record is, which rules were implicit, and what to do during the period when both exist.
- The real work
- Eliciting the undocumented rules
- The real risk
- The period when both systems exist
- What survives
- The spreadsheet, archived read-only
Why this exists
What actually goes wrong in a spreadsheet migration.
Almost never the data. Rows import. What does not import is the colour coding, the strikethrough convention, the column whose header is an abbreviation only one person can expand, and the rule that amber means awaiting-customer. That knowledge is the system, and it lives in someone's head.
The second failure is running both without naming one as authoritative. Two systems disagreeing about a date is how a missed deadline becomes nobody's error — and the parallel period is precisely when a team is least sure which to trust.
The third is treating the spreadsheet as wrong. Frequently the migration surfaces that the old calculation was correct and the new one is not, or the reverse — and in a fee, payroll, or commission context that finding is worth more than the automation.
You're likely here because
- One person maintains the file and holidays are a risk
- The file holds customer or regulated data with no access control
- Two copies exist and nobody is sure which is current
- A formula has been wrong for months and nobody noticed
How to choose
Start with the spreadsheet that costs the most when it is wrong.
If
The file is the pipeline or the customer list
If
The file computes money — fees, commission, payroll
Start with
Reconcile the rules against the agreement before migrating anything
If
The file is the schedule or the deadline tracker
Start with
Move the computed dates to a system that can recalculate a chain
If
The file is a report assembled every Monday
How it works
The migration sequence that works.
Order matters more than tooling here. Most failed spreadsheet migrations ran these steps in a different sequence rather than skipping any of them.
Step 01
Sit with the person who maintains it
Two hours, writing down what each colour, column, and convention means. This is the highest-value step and the one most often replaced by an assumption.
Step 02
Make the implicit rules explicit fields
Amber becomes a state. The abbreviation becomes a named field. The rule in someone's head becomes a definition the next person can read.
Step 03
Reconcile against the source of authority
Where the file computes something contractual — a fee, a deadline, a commission — check it against the agreement rather than against itself. Differences found here are findings, not defects to smooth over.
Step 04
Run both, with one named authoritative
For at least one full cycle. Naming which one wins is the control that stops a disagreement becoming an error nobody owns.
Step 05
Archive rather than delete
Read-only, retained. The file is often the only record of how the process worked before, and that matters the first time someone asks why a number changed.
All replacement paths
Every spreadsheet, and what replaces it — 40 in total.
Each page covers one common spreadsheet: what it actually holds, the rules that are usually implicit, and what the replacement has to do that the file could not.
Replace Excel with AI
Replace the business operations spreadsheet with a connected AI workflow.
See the replacement path →Replace Google Sheets with AI
Replace the business operations spreadsheet with a connected AI workflow.
See the replacement path →Spreadsheet alternative for small business
Replace the small-business operations spreadsheet with a connected AI workflow.
See the replacement path →CRM spreadsheet alternative
Replace the CRM spreadsheet with a connected AI workflow.
See the replacement path →Sales pipeline spreadsheet alternative
Replace the sales pipeline spreadsheet with a connected AI workflow.
See the replacement path →Lead tracking spreadsheet alternative
Replace the lead tracking spreadsheet with a connected AI workflow.
See the replacement path →Customer tracking spreadsheet alternative
Replace the customer tracking spreadsheet with a connected AI workflow.
See the replacement path →Deal tracker spreadsheet alternative
Replace the deal tracking spreadsheet with a connected AI workflow.
See the replacement path →Sales forecast spreadsheet alternative
Replace the sales forecasting spreadsheet with a connected AI workflow.
See the replacement path →RevOps spreadsheet alternative
Replace the RevOps spreadsheet with a connected AI workflow.
See the replacement path →Marketing reporting spreadsheet alternative
Replace the marketing reporting spreadsheet with a connected AI workflow.
See the replacement path →Campaign tracking spreadsheet alternative
Replace the campaign tracking spreadsheet with a connected AI workflow.
See the replacement path →Content calendar spreadsheet alternative
Replace the content calendar spreadsheet with a connected AI workflow.
See the replacement path →SEO spreadsheet alternative
Replace the SEO tracking spreadsheet with a connected AI workflow.
See the replacement path →Customer acquisition spreadsheet alternative
Replace the customer acquisition spreadsheet with a connected AI workflow.
See the replacement path →Project management spreadsheet alternative
Replace the project management spreadsheet with a connected AI workflow.
See the replacement path →Task tracking spreadsheet alternative
Replace the task tracking spreadsheet with a connected AI workflow.
See the replacement path →Operations spreadsheet alternative
Replace the operations spreadsheet with a connected AI workflow.
See the replacement path →Workflow tracking spreadsheet alternative
Replace the workflow tracking spreadsheet with a connected AI workflow.
See the replacement path →Approval tracking spreadsheet alternative
Replace the approval tracking spreadsheet with a connected AI workflow.
See the replacement path →Inventory spreadsheet alternative
Replace the inventory management spreadsheet with a connected AI workflow.
See the replacement path →Order tracking spreadsheet alternative
Replace the order tracking spreadsheet with a connected AI workflow.
See the replacement path →Vendor tracking spreadsheet alternative
Replace the vendor management spreadsheet with a connected AI workflow.
See the replacement path →Procurement spreadsheet alternative
Replace the procurement spreadsheet with a connected AI workflow.
See the replacement path →Budget spreadsheet alternative
Replace the budget tracking spreadsheet with a connected AI workflow.
See the replacement path →Cash flow spreadsheet alternative
Replace the cash-flow tracking spreadsheet with a connected AI workflow.
See the replacement path →Client intake spreadsheet alternative
Replace the client intake spreadsheet with a connected AI workflow.
See the replacement path →Client portal spreadsheet alternative
Replace the client delivery spreadsheet with a connected AI workflow.
See the replacement path →Consulting spreadsheet alternative
Replace the consulting delivery spreadsheet with a connected AI workflow.
See the replacement path →Agency spreadsheet alternative
Replace the agency operations spreadsheet with a connected AI workflow.
See the replacement path →Law firm spreadsheet alternative
Replace the legal operations spreadsheet with a connected AI workflow.
See the replacement path →Accounting firm spreadsheet alternative
Replace the accounting-firm operations spreadsheet with a connected AI workflow.
See the replacement path →Real estate spreadsheet alternative
Replace the real-estate lead and deal tracking spreadsheet with a connected AI workflow.
See the replacement path →Property management spreadsheet alternative
Replace the property management spreadsheet with a connected AI workflow.
See the replacement path →Contractor spreadsheet alternative
Replace the contractor operations spreadsheet with a connected AI workflow.
See the replacement path →Home services spreadsheet alternative
Replace the home-services operations spreadsheet with a connected AI workflow.
See the replacement path →Healthcare practice spreadsheet alternative
Replace the non-clinical practice operations spreadsheet with a connected AI workflow.
See the replacement path →Insurance spreadsheet alternative
Replace the insurance operations spreadsheet with a connected AI workflow.
See the replacement path →Nonprofit spreadsheet alternative
Replace the nonprofit operations spreadsheet with a connected AI workflow.
See the replacement path →Replace spreadsheets with AI workflows
Replace the cross-functional workflows spreadsheet with a connected AI workflow.
See the replacement path →Scope
Where the spreadsheet should stay.
- Genuine ad-hoc analysis. A one-off model built to answer one question should stay a spreadsheet and be thrown away.
- Anything with no defined process yet. Automating an undefined process makes the confusion faster; definition comes first.
- Small, single-owner, non-regulated lists where the file is genuinely sufficient. Replacing those is churn.
- The archive itself. The old file stays, read-only — it is the record of how the process used to work.
FAQ
Questions about this collection.
Do we have to move everything at once?
No, and doing so is the usual reason these fail. One spreadsheet, one full cycle of parallel running, then the next.
What if the migration shows the old numbers were wrong?
That is a finding, and in a fee or payroll context it may require correction and disclosure. It is also frequently worth more than the time the automation saves.
Who should own the replacement?
The same person who owned the spreadsheet, unless the reason for moving is that ownership sat with one person. In that case ownership is part of what is being changed and should be decided explicitly.
Can we keep using the spreadsheet for reporting?
You can export to one, and many teams do. What should not persist is the spreadsheet being the place where a value is first entered or first corrected.
How long should parallel running last?
One complete cycle of whatever the process is — a month for billing, a quarter for reviews. Long enough that the exceptions appear, because the exceptions are what the file handled and nobody documented.
Start here
Start with the spreadsheet that costs the most when it is wrong.
Describe what the file actually does, including the rules that only one person knows. ARIA resolves the record model and what the replacement has to handle before anything is migrated.