Loading experience…
Loading experience…
Legacy Application Modernization for UK Boiler Manufacturers
UK boiler and pressure vessel manufacturers often run quoting, calculation, and production logic on VB6 software built 15-20 years ago - a language Microsoft stopped supporting in 2008. UK shops carry an added layer: PSSR, PED, and a post-Brexit CE-to-UKCA marking transition that legacy control systems were never built to track. This page covers what that risk looks like for UK manufacturers and how a phased migration works without stopping production.
Why This Matters Now
VB6 lost official Microsoft support in 2008. Any vulnerability found since then has no fix coming, which is an increasingly hard thing to explain during a customer or insurer's IT due diligence review.
Windows 10 reached end of life in October 2025. VB6 applications running on UK plant floors via compatibility shims often break as those shims tighten under modern Windows security hardening.
VB6 expertise is a shrinking pool in the UK market specifically - when the engineer who understands the quoting logic's edge cases retires, the business rules embedded in that code often leave with them.
Calculation and labelling logic built when CE marking was the only requirement often hasn't been touched since - it wasn't designed with a UKCA parallel-marking period in mind, and that gap tends to be invisible until an audit finds it.
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
Redesigned and rebuilt on a modern web stack, with PED-aligned calculation logic re-implemented from a documented spec. Cleanest long-term architecture, highest risk of missing undocumented UK-specific compliance rules.
Best when: The current system is small, or CE/UKCA labelling logic needs a proper rethink rather than a patch anyway.
Watch out for: Skipping a proper audit means marking and category-classification rules tend to resurface late, usually during a Notified Body or HSE review.
Tool-assisted code translation
Automated tools translate VB6 into C# or VB.NET, preserving the existing PED category logic and calculation rules as-is. Faster than a rewrite, but roughly a third to half of converted code on complex systems needs manual tuning.
Best when: The codebase is large, the PED classification logic has been reliable for years, and preserving exact behaviour matters more than redesigning it.
Watch out for: Automated tools struggle with proprietary classification and category logic - manual review against current PED/PSSR requirements isn't optional.
Modernize the edges, keep the core running
Existing VB6 logic stays in place, wrapped in a modern API so new dashboards, ERP integrations, and UKCA/CE dual-marking tracking tools can connect without touching the legacy code directly.
Best when: Production can't tolerate downtime and the priority is getting modern visibility into a system that's still calculating correctly.
Watch out for: Buys time and reduces risk, but the underlying VB6 code still needs a real plan - especially once transitional marking arrangements change.
UK Boiler & Pressure Vessel Compliance
The Pressure Equipment (Safety) Regulations 2016 and the retained PED framework set category and conformity requirements by pressure, volume, and fluid group. Calculation and classification logic can be built to reflect the categories that actually apply to your equipment, instead of relying on manual lookups.
The UK's CE-to-UKCA transition timeline has shifted more than once - a modernized system can be built to track which marking regime applies to which product line and update as guidance changes, rather than hardcoding a single answer.
Written scheme of examination intervals, inspection records, and conformity documentation are common places manual VB6 systems fall behind - not because inspections were skipped, but because the paperwork trail wasn't kept current.
A Note on PED, PSSR, and UKCA
PED (as retained UK law) sets design and conformity categories; PSSR governs safe operation, written schemes of examination, and in-service inspection. They're enforced differently and a VB6 system built years ago was very likely only encoding one of them, if either.
The CE-to-UKCA marking transition has been extended more than once since it was first announced - if your quoting or labelling logic hardcodes one marking regime, that's worth flagging in the audit before assuming it's still correct. Confirm current deadlines with HSE or BEIS guidance rather than relying on what the software currently assumes.
Marking Transition
The UK's marking transition timeline has changed more than once. Software written under the original CE-only assumption tends to carry that assumption forward silently - worth checking before it becomes an audit finding.
Pre-2021
Most legacy VB6 quoting and labelling logic was written when CE marking, under the EU PED framework, was the only requirement in play.
2021 onward
UKCA marking was introduced for the GB market, with CE marking still accepted during a transitional period - a period that has been extended more than once.
Ongoing
Because the transitional deadline has moved before, any new or modernized marking logic should be built to be updated easily, and current requirements should be confirmed with HSE or BEIS guidance rather than assumed from a past deadline.
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 workflow, mapping business logic against PED/PSSR categories and checking what marking regime the software currently assumes.
Varies by scope
Based on the audit, we recommend rewrite, automated conversion, or hybrid API wrap, and build against a written scope that accounts for UK-specific classification and marking requirements.
Final phase
The new system runs alongside the existing one and is verified against real production data before cutover. Your team keeps working on the current system throughout.
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.