Start a spreadsheet migration by identifying decisions, exceptions and ownership. Copying every tab into a web application often preserves the confusion that prompted the project.
Follow one real record
Ask an operations manager to demonstrate a completed job using a redacted workbook. Follow the handoffs between a branch, headquarters and an external contractor. Hidden columns and cell colours may encode approvals that nobody has documented. Compare the explanation with what the person actually does; interviews and observation answer different questions.
Build a mapping before an interface
| Workbook convention | Product decision | Acceptance check |
|---|---|---|
| One row per job | Stable job identifier | Identical customer names do not merge |
| Red background | Explicit status and reason | Meaning survives a monochrome export |
| Copied formula | Versioned calculation rule | Historic totals remain explainable |
| One tab per branch | Organisation membership | Branch data stays isolated |
Rehearse the cutover
Consider a fictional field-service company expanding across time zones. Two branches name the same asset differently. An import that merely accepts every row doubles the inventory. Produce a reconciliation queue, preserve original values and assign someone who understands the equipment to resolve ambiguity. Run the import against a copy and compare both aggregate totals and individual job histories.
Decide which system owns edits during the transition. A parallel run is useful for comparison only when staff know where to enter changes. Define the freeze window, the reconciliation owner and the conditions for returning to the workbook. Avoid an irreversible switch during the busiest operating period.
Must every historical row move?
Usually the decision can be separated from the first release. Active jobs may need full migration while closed jobs remain in a controlled archive. Record what users can search, export and correct in each location. A useful migration brief ends with a signed-off mapping and rehearsal report, not a promise that the upload button works.
A cross-region import case
For a distributed team, rehearse a file containing US-style dates, UK-style dates and identifiers with leading zeros. Reject ambiguous dates for review instead of guessing. This creates a concrete acceptance case for an English-language product serving more than one market.
Sources and further reading
From this guide to your project
Strategy ↗
An idea becomes an opportunity when it solves a real problem for people willing to change how they work.
Tell us about your ideaExamples are educational and do not describe client results. Content prepared with AI assistance; see our editorial policy. Our method ↗