Find out what the spreadsheet actually does
Picture a small business that has run its customer jobs from one shared spreadsheet for years. It has a tab for every year, color codes only two people understand, a hidden column of notes, and formulas nobody wants to touch. The business finally moves that work into a proper system. The new system looks clean on day one. A month later, someone needs to know what was promised to a customer three years ago, and the answer is in a cell comment on a tab that did not get imported. Worse, a few people kept updating the old spreadsheet, so now there are two versions of the truth.
That scene is an original illustration, not a TwoQM client and not a measured result. Spreadsheets rarely fail all at once; they get retired badly. The goal of a cutover is not just to start using the new system. It is to stop using the old one on purpose, while keeping its history findable.
This piece is about that retirement step for any business, whether the spreadsheet tracks jobs, customers, inventory, or orders. It is not a guide to picking new software.
A legacy spreadsheet usually does more than anyone wrote down. Before moving anything, walk through it with the people who use it and list:
Every tab and what it is for, including old or hidden ones.
Columns that carry meaning, including colors, bold text, and blank cells that mean something.
Formulas that calculate totals, due dates, or statuses.
Notes and comments stored in cells.
Who opens it, how often, and for what decision.
What depends on it: reports, exports, other files, or a weekly email.
Anything on this list either moves to the new system, becomes part of the archive, or is retired on purpose. Nothing gets dropped by accident.
Decide what moves and what gets archived
Not every row needs to be imported. A common split:
Move open and recent records that people still work on.
Archive older, closed records in a read-only copy that stays searchable.
Map each column that moves to a field in the new system, with a short note for anything that changes meaning, like a color code becoming a status.
Write the mapping down and have the spreadsheet's owner approve it. That page becomes the key for anyone who later compares the old file with the new system.
Pick a freeze point and one system of record
Choose a freeze point: the moment after which nobody edits the old spreadsheet. Before it, the spreadsheet is the system of record. After it, the new system is. Write that rule down and tell everyone who uses the file.
If your team wants a short overlap where both are updated, keep it short and name who checks that they match. The payroll parallel test before a software switch shows a stricter version of this idea for payroll.
Check the move before you call it done
After the import, compare the two:
Counts. Number of records moved per year or status, against the spreadsheet.
Totals. Sums of any money or quantity columns that moved.
Spot checks. A handful of records, old and new, opened side by side.
Exceptions list. Rows that did not import cleanly, each with an owner and a decision.
The owner signs off only when the counts match or every difference is explained.
Archive the old file so history stays findable
Retiring a spreadsheet does not mean deleting it. At the freeze point:
Save a dated, read-only copy with a clear name that says it is archived.
Remove edit access for everyone except the owner.
Link the archive from the new system where people would look for old history, such as the customer or job record when that is possible.
Replace old links and bookmarks so people land in the new system, not the old file.
Keep the mapping page next to the archive.
Ask your accountant or advisor how long your business needs to keep certain records; the archive should follow that, not a guess.
Where TwoQM fits
Custom software can replace a spreadsheet with an app built around how your team actually works, including import tools that follow your mapping and an exceptions list for rows that need a decision. A CRM can hold customer history so older notes sit next to current records. Connected systems work can link the archived copy to records in the new system where your tools allow, and business automation can run the count and total checks and remind the owner about open exceptions. What fits your setup is confirmed during scoping.
Where AI helps, and where it stops
AI can read a spreadsheet's structure and draft a list of tabs, columns, and formulas for the owner to confirm, suggest field mappings, summarize cell comments, and explain differences in plain English or Spanish.
AI does not approve the mapping, decide which records are kept or dropped, sign off on the cutover, or delete anything. A person on your team makes those decisions.
Where to start this week
Open the spreadsheet with the person who knows it best and write the inventory list above. Mark which tabs would move and which would be archived. Pick a tentative freeze point. That single page is enough to start a real conversation about the new system.
TwoQM builds custom software, CRM workflows, and connected systems for small businesses across industries. If one spreadsheet has become the place your business keeps its memory, TwoQM can scope a retirement plan around it. Pricing explains how business apps, systems, and custom software are scoped.
Describe Your Spreadsheet Cutover · Explore TwoQM custom software