Follow one transaction from start to finish
Choose a common task such as a service request, purchase order or monthly reconciliation. With authorized, redacted examples, record where data enters, who changes it, what is copied between files and which output is trusted. Include email approvals and paper notes.
The first deliverable is a process map and exception list, not a new screen. Keep working analysis workbooks when they remain useful.
Find the authoritative record
Identify who owns customer IDs, product codes, rates and statuses. Compare duplicate files and write down how conflicts are resolved today. For each record, decide where updates are allowed. A web app cannot repair unclear ownership by itself.
Extract hidden logic
In Excel, inspect formulas, named ranges, lookup sheets, macros, external connections and manual adjustments. In Access, inspect queries, form events, reports, VBA and linked tables. Ask why an override exists before removing it.
For example, an illustrative discount spreadsheet might round each line while an invoice report rounds only the total. Save both outputs and get an agreed rule before implementing either.
Choose the smallest useful change
Compare cleanup and documentation, controlled sharing, a backend change and a web rebuild. Access can retain its front end with linked server tables, as Microsoft describes. A workflow that needs customer browser access may warrant different screens; a reliable internal report may not.
Prepare evidence for the next decision
Bring an object inventory, user roles, sample calculations, report definitions and acceptance owners to the review. Keep real personal records and credentials out of public forms. Use secure transfer only after agreeing access and handling.
Then follow the migration and recovery plan, or compare Access and Excel uses. Preserve the existing workflow until the replacement has passed agreed checks.




Comments
Leave a comment
Comments are reviewed before publishing.