How to move a critical process from spreadsheets to custom software, in phases and with the spreadsheet running in parallel
A spreadsheet that runs operations holds rules nobody wrote down. We bring them out, put them in order and move them into a system, and the spreadsheet stays until the system produces the same results.
How we do it
The spreadsheet stays until the system gives the same results.
- Inventory of the spreadsheet: formulas, macros, who uses it and which unwritten rules it holds.
- Data cleanup and a model for the system.
- System running in parallel with the spreadsheet, with a small group of users.
- Reconciliation between the spreadsheet and the system until they match.
- Cutover approved by the owners, and training.
- Retirement of the spreadsheet.
Frequently asked questions
- What happens to the macros and formulas we already have?
- Each one is documented and reproduced in the system. The ones no longer used, or that give inconsistent results, are reviewed with you before deciding.
- When do we stop using the spreadsheet?
- When the system produces the same results during the parallel run and the process owners approve the cutover.
- Is custom software or a low-code tool the better choice?
- If the process is standard and the tool covers the rules, a low-code option may be enough, and we'll tell you so. Custom software makes sense when the rules, integrations or volume go beyond what the tool allows.
Request a quote
Tell us which process you want to fix and what you use for it today. We reply within 24 business hours.
Request a quote