Custom Software
Business Strategy
Replace a Business Spreadsheet: A Practical Migration Guide
Preserve business rules, map fields, test permissions and reconcile data before a controlled spreadsheet cutover.
The practical answer
A safe replacement preserves the spreadsheet’s business rules, defines access, rehearses migration and reconciles results. Agree one source of truth and a rollback plan that includes work created after cutover.
Discuss your business technology requirements, users and existing tools so we can define a useful website or web app scope. Discuss your website or app.
Replace a business-critical spreadsheet by preserving its useful rules, then improving the workflow around them. Begin with one workbook and one outcome. Do not assume that a new interface will repair unclear data or responsibilities.
First decide whether replacement is necessary #
A well-managed spreadsheet can remain the right answer for analysis, modelling or a simple shared list. Modern tools offer collaboration and history: see Google Sheets version history and Excel co-authoring. The question is whether those controls meet your actual workflow, access and audit needs.
Check an improved workbook, a product you already own and an industry tool before choosing custom development. Shared editing alone does not prove you need a new system.
Example: turn a job tracker into a controlled workflow #
This fictional example starts with a workbook containing customer names, job status, quote totals and coloured cells that indicate approval. The proposed system keeps the same job information while making ownership and approval explicit.
| Current workbook | Meaning to preserve | Proposed requirement | Acceptance check |
|---|---|---|---|
| Customer typed into each row | The organisation commissioning the job | Stable customer ID with an agreed matching process | Two similarly named customers are not merged automatically |
| Green cell | A particular quote was approved | Status, approved version, approver and time | Changing the scope requires a new approval |
| Formula for remaining value | Agreed calculation and rounding | Documented calculation with sample inputs | Known examples reconcile with the agreed result |
| Hidden overdue tab | Work needing a follow-up | Owner queue with due date and reason | Closed or deferred work is handled according to the rule |
Agree who can see and change each record #
| Role | Can do | Must not do |
|---|---|---|
| Coordinator | Create and update enquiries; assign an owner | Approve a quote outside their agreed authority |
| Job owner | Update assigned work and submit completion evidence | Read another client’s restricted documents |
| Approver | Review and approve the current scope version | Silently overwrite approval history |
| Finance reviewer | Check billing information and record invoice handoff | Treat an unapproved variation as billable |
Define the permissions from real responsibilities, not from convenient screen labels. Test denied actions as well as successful ones, including exports, files and direct requests to the server.
Clean and rehearse the migration #
- Save a controlled copy and identify the business owner of the data.
- List every field, formula, hidden tab, macro, external link and manual convention.
- Resolve duplicates and invalid values through an agreed process; keep decisions traceable.
- Import a representative sample including awkward cases.
- Reconcile record counts, totals, dates, relationships and access with expected results.
- Have the people who use the workbook complete their real tasks in the candidate system.
Cut over with one source of truth #
Agree a cutover window, final export, migration owner and rollback decision. Keep the old workbook read-only after cutover. If a short parallel check is necessary, specify which system is authoritative, who reconciles differences and exactly when the check ends. Avoid asking staff to maintain two competing live systems indefinitely.
A rollback plan should say what happens to records created after cutover. Simply reopening yesterday’s spreadsheet can lose today’s work.
Download the migration and reconciliation checklist (CSV). Open in a spreadsheet or text editor; the example rows are illustrative.
Measure the complete change #
Compare data-entry effort, missing information, rework and reporting time before and after. Include training, support and new review tasks. Keep a named person responsible for data quality after launch. The result should be more dependable work, not merely a tidier table.
Use the cost and quote comparison guide to check migration, testing and ongoing care are included in the proposal.
A useful companion: Spreadsheet Replacement Checklist.
Other articles worth reading
Business Strategy
Outgrowing Spreadsheets: When Your Business Needs a Better System
Spreadsheets are useful until they quietly become the system your business depends on. Here are the signs you have outgrown them, and how to move to a better system without buying the wrong tool.
Business Strategy
The LD Efficiency Stack: A Practical Systems Framework
Use foundation, standardisation, automation and visibility to decide what evidence and improvement a workflow needs.
AI & Automation
AI Strategy vs Technology Strategy for NZ Businesses: Which One Fits?
AI strategy decides how AI should safely fit into the business. Technology strategy decides what systems, workflows, software, portals, and reporting the business should run on.