Loading experience…
Loading experience…
Legacy Application Modernization for Manufacturers
Boiler and pressure vessel manufacturers often run their quoting, calculation, and production logic on software built 15-20 years ago - frequently in Visual Basic 6, a language Microsoft stopped supporting in 2008. This page explains what that risk actually looks like, the real options for modernizing it, and how a phased migration works without stopping production.
Why This Matters Now
VB6 lost official Microsoft support in 2008. Any vulnerability discovered since then has no fix coming - the application inherits every security gap that's accumulated for over a decade and a half.
Windows 10 reached end of life in October 2025. VB6 applications that relied on compatibility shims to run on newer Windows versions often break as those shims get tightened under modern security hardening.
VB6 expertise is a shrinking pool. When the one person who understands the quoting engine's edge cases retires or leaves, the business rules embedded in that code often leave with them.
It's common for VB6 systems built up over many years to have logic - discount rules, material substitutions, tolerance calculations - that exists only in the code itself, with no other record of why it works that way.
Many VB6 systems run on one aging on-prem machine with no supported upgrade path. If that hardware fails, the business can lose quoting or production capability entirely until it's rebuilt from scratch.
Three Real Options
A full rewrite, an automated conversion, and a hybrid API wrap each solve a different problem. The right one depends on how much of your business logic is documented, how much downtime you can tolerate, and how much of the current system genuinely needs to change.
Rebuild from scratch on a modern stack
The application is redesigned and rebuilt from the ground up, usually on a modern web stack. This gives the cleanest long-term architecture but carries the highest risk of missing undocumented business rules that only exist in the old code.
Best when: The current system is small, well-documented, or badly needs a UX rethink anyway.
Watch out for: Rewrite projects that skip a proper audit of the existing logic tend to rediscover missing business rules late, in production.
Tool-assisted code translation
Automated tools translate VB6 code into a modern language, typically C# or VB.NET, preserving the original logic structure. Faster than a full rewrite, but the output usually needs meaningful manual cleanup - industry data suggests roughly a third to half of auto-converted code needs hand tuning on complex, highly customized systems.
Best when: The codebase is large, the logic is well-tested, and you want to preserve exact behavior rather than redesign it.
Watch out for: Automated tools handle routine code well but struggle with proprietary algorithms and deep architectural decisions - human review of the converted output isn't optional.
Modernize the edges, keep the core running
The existing VB6 logic stays in place, but gets wrapped in a modern API layer so new interfaces - web dashboards, mobile access, ERP integrations - can talk to it without touching the legacy code directly. Functions get replaced behind that API over time, not all at once.
Best when: Production can't tolerate downtime, and the highest-value fix is giving the team modern access to a system that otherwise still works.
Watch out for: This buys time and reduces risk, but it's a bridge, not a destination - the underlying VB6 code still needs a real plan eventually.
Boiler & Pressure Vessel Specifics
The ASME Boiler and Pressure Vessel Code is a set of active sections covering different equipment classes - Section I for fired and unfired steam boilers above 15 psig, Section IV for heating boilers at or below 15 psig steam or 160 psi/250°F hot water, among others. Calculation logic can be built to reflect the sections that actually apply to your equipment, instead of relying on manual table lookups.
When thickness, material spec, and performance calculations are built into the system instead of done by hand, generating a bill of materials from a quote request takes a fraction of the manual time - without changing the underlying engineering rules your team already trusts.
Certificate expirations, inspection records, and Manufacturer's Data Report tracking (Form U-1/P-1) are common places manual systems fail during audits - not because inspections were skipped, but because the paperwork trail wasn't kept current. A modernized system can track this automatically.
A Note on ASME BPVC
The ASME Boiler and Pressure Vessel Code isn't one document - it's a set of active sections, each covering a specific class of equipment. Section I applies to fired and unfired steam boilers above 15 psig; Section IV covers heating boilers at or below 15 psig steam, or 160 psi and 250°F hot water.
Getting the applicable section wrong isn't a paperwork slip - it's a compliance and liability issue. Calculation logic built into your quoting system should reflect the sections that actually govern your equipment, not a generic ruleset.
How the Migration Works
Timelines vary depending on codebase size and which modernization approach fits best - the audit is what determines that, not a fixed promise made before anyone's looked at the code.
Weeks 1-2
We review the existing VB6 code and current workflow to map out the business logic, identify undocumented rules, and flag which parts of the system carry the most operational risk.
Varies by scope
Based on the audit, we recommend the right approach - full rewrite, automated conversion, or a hybrid API wrap - and build against a written scope, so the timeline and cost are known before development starts, not discovered during it.
Final phase
The new system runs alongside the existing one until it's been verified against real production data. Your team keeps working on the current system throughout - the switch happens only once the new one is confirmed accurate.
FAQs
Next Step
A short review of the existing code and workflow is enough to tell whether a rewrite, an automated conversion, or a hybrid API wrap makes the most sense - before any commitment to a build.
Book a Legacy System ReviewNo obligation. NDA available on request.