Reading 32,000 lines of undocumented VBA, straight from the file
A housing association's Excel and VBA application, 113 modules read in full, then an executive review and a fixed-price plan to replace it with a supported web application.
Spreadsheets into systems
Macros, links between files, copies of copies, and one person who understands it. We read the workbook end to end, rebuild it as a proper system, and move its data across, reconciled.
The workbook
The system
Formulas, macros, hidden sheets and links to other files come straight out of the file, so the review covers what is out of sight as well as what is on screen. That is how we read 113 VBA modules for a housing association. Read the write-up
Some of it is business rules worth keeping exactly. Some is a workaround for something Excel couldn't do. The review says which is which, and what replacing it would cost.
A database with the rules written down and tested, screens for the jobs people actually do, permissions, and a record of each change: who, when and what it was before.
History comes across with the same checks as any migration: counts and totals from the workbook against the new system, and anything not moved listed with its reason. How a migration runs
The workbook runs alongside until the answers match, then becomes read-only. Anyone who still wants a spreadsheet can export one.
.NET and React for the application, SQL Server or Azure SQL underneath, Python where it suits the job, and Power BI for reporting. Sometimes the honest answer is a smaller change: the same spreadsheet, fed from one database instead of a dozen copies. The review says which.
A housing association's Excel and VBA application, 113 modules read in full, then an executive review and a fixed-price plan to replace it with a supported web application.
Tell us what it does, who uses it and what goes wrong with it. No files yet: those come later, under an NDA.