Loading experience…
Loading experience…
Legacy Application Modernization for European Boiler Manufacturers
European boiler and pressure vessel manufacturers - especially those running plants across more than one member state - often run quoting and calculation logic on VB6 software built 15-20 years ago, a language Microsoft stopped supporting in 2008. The added complexity in Europe: PED and CE marking are EU-wide, but national implementation, Notified Body relationships, and inspection regimes still vary by country. This page covers what that risk looks like across a multi-country footprint 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 - a growing liability for manufacturers whose customers increasingly require IT security attestations as part of EU procurement.
Windows 10 reached end of life in October 2025. VB6 applications on European plant floors that relied on compatibility shims often break as those shims tighten under modern Windows security hardening.
VB6 expertise is a shrinking pool across Europe. When the engineer who understands the quoting engine's edge cases retires or moves on, the business rules embedded in that code often leave with them.
Plants operating in more than one EU country often run the same VB6 system across different national implementations of PED and different Notified Body relationships - with no clean way to see which rules apply where.
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 category and CE marking logic re-implemented from a documented spec that can flex per country. Cleanest long-term architecture, highest risk of missing undocumented national variations.
Best when: The current system is small, or the multi-country logic has become too tangled to safely extend further.
Watch out for: Skipping a proper audit means country-specific rules - a different Notified Body requirement, a different national inspection interval - tend to resurface late, usually per-plant, one at a time.
Tool-assisted code translation
Automated tools translate VB6 into C# or VB.NET, preserving the existing PED category logic and whatever national variations are already coded in. 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 multi-country logic has been tested against real inspections for years, and preserving exact behaviour matters more than a redesign.
Watch out for: Automated tools struggle with proprietary, country-specific classification logic - manual review against each jurisdiction's current requirements isn't optional.
Modernize the edges, keep the core running
Existing VB6 logic stays in place per plant, wrapped in a modern API layer so a single dashboard can give visibility across all country operations without touching the legacy code in each location directly.
Best when: Different plants can't tolerate downtime at the same time, and the priority is centralized visibility before a full technical overhaul.
Watch out for: Buys time and reduces risk, but doesn't resolve the underlying fragmentation - each plant's VB6 code still needs its own eventual plan.
European Boiler & Pressure Vessel Compliance
Directive 2014/68/EU (PED) sets EU-wide category and conformity assessment rules by pressure, volume, and fluid group, referencing harmonized standards like EN 12953 (shell boilers) and EN 12952 (water-tube boilers). Calculation logic can be structured so the shared EU rules and country-specific implementation details are separated, not tangled together.
Different plants often work with different Notified Bodies for conformity assessment. A modernized system can track which Notified Body, certificate, and inspection schedule applies to which plant and product line in one place.
Certificate expirations, inspection records, and conformity documentation are common places multi-country manual systems fall behind - not because inspections were skipped at any one site, but because there's no single source of truth across sites.
A Note on PED and National Implementation
The Pressure Equipment Directive is EU-wide, but how it's enforced - which Notified Bodies operate where, what additional national rules apply, what inspection cadence is expected - still varies by member state. A VB6 system built for one plant rarely generalizes cleanly to a second country.
Multi-country manufacturers get the most value from separating the EU-wide PED and EN 12953/12952 logic from country-specific implementation details in the software itself, rather than hardcoding one country's rules and patching exceptions in as new plants come online.
Multi-Country Snapshot
PED and CE marking apply EU-wide, but the practical details - which body assesses conformity, what national rules layer on top - differ by country. A representative snapshot for common manufacturing locations:
| Country | Primary Framework | Marking | Notified Body | Notes |
|---|---|---|---|---|
| Germany | PED 2014/68/EU + national TRD/TRBS guidance | CE | Required for higher categories | Strong existing inspection body network (e.g. TÜV) |
| France | PED 2014/68/EU + national arrêté provisions | CE | Required for higher categories | National inspection body involvement common |
| Italy | PED 2014/68/EU + national implementation decree | CE | Required for higher categories | INAIL involvement for in-service inspection |
| Netherlands | PED 2014/68/EU + national Warenwetbesluit | CE | Required for higher categories | Centralized inspection body coordination |
| Poland | PED 2014/68/EU + national UDT oversight | CE | Required for higher categories | UDT (Office of Technical Inspection) active role |
National detail changes over time and by product category - confirm current requirements with your Notified Body or a compliance advisor before finalizing scope. This table is a starting orientation, not a substitute for legal or regulatory review.
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-3
We review the existing VB6 code across each plant, mapping business logic against PED and the relevant national implementation details, and flag where logic diverges between countries without a clear reason.
Varies by scope
Based on the audit, we recommend rewrite, automated conversion, or hybrid API wrap, and build a scope that separates shared EU-wide logic from country-specific rules so future plants are easier to onboard.
Final phase, per site
The new system runs alongside the existing one at each plant and is verified against real production data before cutover, allowing sites to move over on independent timelines.
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.