Your old system still runs the business. Let's keep it that way, without the rewrite.
The Access database that quotes every job. The VB6 app the shop floor built its day around. The ColdFusion site still handling half your orders. It works. Your team knows it. Your customers depend on it. And every consultant you've spoken to wants to tear it out and start again for six or seven figures you don't have.
There's a middle path and we've been walking it for over twenty years. We assess what you've actually got, tell you honestly whether to fix it, modernize it, or replace it, then do the work at a pace your business can absorb.
Fix it, modernize it, or replace it.
Most firms have one answer because they only make money one way. Large consultancies always find a rewrite. Cheap shops will maintain anything forever whether or not that makes sense. We've been at this long enough to tell you the truth about your specific system.
Fix it. The system still earns its keep. It needs patching, security work, and a maintenance plan somebody actually follows. Cheapest path, and the right answer more often than people expect.
Modernize it. The bones are good, but the framework is out of date, the login is frightening, and the reporting is stuck in 2008. We upgrade what needs it and leave alone what still works.
Replace it. It has genuinely reached the end. We build the replacement to match how you work, move the data, and retire the old one on a schedule you control. No big-bang cutover.
Whichever it is, you get real cost and effort numbers before committing to anything.
The stacks we've kept alive.
Mostly the systems other shops decline to touch.
- Microsoft Access applications, front-end forms, back-end databases, or the whole thing
- Visual Basic 6 business apps still running on somebody's desktop
- Classic ASP and older .NET web applications
- ColdFusion sites and internal tools
- Older PHP, including WordPress, Joomla, Drupal, ZenCart, OsCommerce, and custom code
- On-premise custom apps with no vendor, no documentation, and no original developer
- ERP, inventory, order management, or accounting systems whose upgrade path is a full rewrite
If your business runs on something other consultants won't support, that's the conversation we're set up for.
An assessment, then a roadmap you control.
Assessment. We go through the code and the workflow, then hand you a written report: what you have, what's at risk, what each path forward looks like, and what it would cost. Fixed price, and the fee credits back if you engage us for the work.
Roadmap. A prioritized plan with real numbers against it. You decide what to act on and when. Nothing gets scoped in a vacuum.
Execution. The work happens at a pace your business can absorb. No surprise invoices, no multi-year megaproject. You get documentation and code you own along the way, so you're never trapped with us.
If the right answer for you is to leave it alone for another year, we'll say that, and it will be in writing.
When we're not the right call.
We'd rather lose the work than take it badly. Some honest cases where you should hire someone else, or nobody:
- You want the cheapest possible bid. We are not the cheapest, and on a system nobody documented, cheapest tends to get expensive later.
- You want a wholesale rewrite of something that does not need one. We will push back on that, which is not what you want if the decision is already made.
- It is a licensed product from an active vendor with a reasonable upgrade path. That is a conversation with them, not with us.
- You want someone who disappears after go-live. We stay to keep things running.
Before you call.
My Access database is decades old. Is it too far gone?
That is usually the sweet spot rather than a problem. The older and more abandoned a system feels, the more value there tends to be in sorting it out, because the alternative quotes people have received are so much worse. Access is one of the most common places we start.
Do we have to pick one path up front?
No, and that is what the assessment is for. Often the answer is a mix: stabilize now, modernize a piece at a time over a year, replace one component two years out when it actually needs it.
How much does modernization cost?
Less than a rewrite, almost always. Small stabilization work runs a few thousand. Incremental modernization runs into the tens of thousands and occasionally low six figures across months. Full replacements land higher, though rarely close to what the rip-and-replace crowd quotes. The assessment gives you real numbers for your system.
What if the original developer is gone and nothing is documented?
That is the common case, not the exception. Working out what the code actually does, and writing that down, is a large part of what the assessment produces. You end up with documentation you did not have even if you never hire us for the work.
Will we be locked in to you?
No. Every engagement leaves you with documentation and code you own. If you want another team to take over, they will have what they need. We would rather keep clients because the work is good.
Do you work remotely?
Yes. We are based in Hopedale, Massachusetts, and clients are across New England and the rest of the country. Most of the work is remote, with on-site visits when the engagement genuinely calls for it.
The deeper playbook lives at LSM.
Legacy System Modernization is a big enough practice that we gave it its own home, with the full assessment methodology, per-stack detail, and the complete fix-versus-modernize-versus-replace framework.
A replacement is usually a custom application, and whatever you keep still needs to talk to the rest of your stack, which is integration work. See everything we do.
Running on something nobody wants to touch?
Tell us what it is and what it does for you. We'll tell you honestly whether it needs fixing, modernizing, replacing, or leaving alone.
Get an assessment