SVC-LGC
Legacy System Modernization
Replace the Access database, the Excel workbook or the aging on-premise system that the business depends on.
The problemOne person understands the system, and the business stops if it breaks.
Many small businesses run on an Access database, a macro-heavy workbook or an old on-premise application built years ago. We document what it does, decide with you what to keep, rebuild or replace, and move to a maintained system in stages while the old one keeps running.
What we build
- 01
System review
An inventory of tables, macros, reports, scheduled tasks and manual steps, and a written description of the behavior nobody wrote down.
- 02
Rebuild or replace decision
A recommendation on whether to rebuild, buy a packaged product, or mix the two, with a cost comparison.
- 03
Phased replacement
Move one function at a time, starting with the one that carries the most risk, and run old and new in parallel until they agree.
- 04
Data migration
Cleaned, mapped and reconciled, with the old data kept read-only for reference.
- 05
Documentation and handover
Data model, screens, business rules and deployment notes, so the next person can maintain it.
A sketch of the kind of screen
Sample layout only. Numbers here are placeholders, not results.
What ships first
- 01Written system review
- 02The highest-risk function rebuilt and running in parallel
- 03Reconciliation against the old system
- 04Runbook for restore and support
Scope is fixed in the proposal at the end of discovery. How a project runs
How we would judge it
- Business rules documented
- Parallel-run differences resolved
- Single-person dependencies removed
- Time to restore from backup, tested
Works with what you already run
- Access and SQL Server databases
- Excel and CSV
- Legacy ERP exports
- Accounting packages
Before we start
- Access to the system and the person who built or maintains it
- A list of the reports and exports people rely on
- Permission to run old and new in parallel
What we do not build, and when to buy instead
We do not promise a like-for-like copy of a large packaged ERP. If your legacy system is a mature package with an upgrade path, upgrading it may cost less than replacing it, and we will tell you.
Questions about Legacy System Modernization
Do we have to stop using the old system?
Not until the new one has matched it for a full period you choose, usually including a month-end close.
What if no one knows how the old system works?
That is common. The system review reads the data, macros and reports to reconstruct the rules, and we confirm them with the people who use it.
Can you support the legacy system while we move?
For a limited time, after review. We would rather stabilize it than let it fail during the move.
Industries that use this
Blueprints (illustrative)
SVC-LGC
Sound familiar? One person understands the system, and the business stops if it breaks.
Send a project brief. Discovery ends in a fixed-price proposal for the first release, and you keep it whether or not you hire us.