Legacy Rescue · VB6

VB6 Migration UK: A Safe Exit Plan

Microsoft ended all support for the VB6 development environment on 8 April 2008 and says plainly that there is no supported way to maintain VB6 applications. The applications still run, which is exactly why so many are still out there. We rebuild them as modern web applications, with the old system live in parallel until the new one has proven itself.

Book a free Legacy Risk Audit Back to Legacy Rescue
The facts

Is VB6 end of life?

Yes, as a development platform. Mainstream support ended in March 2005 and the IDE left all support on 8 April 2008; Microsoft states there is no supported method to create or maintain VB6 applications and recommends replacement. The runtime is the nuance: core runtime files still ship inside Windows 11, supported for that OS’s lifetime for critical fixes only. Your application runs; nobody supports changing it.

VB6 released 1998, the last classic VB
IDE support Ended 8 April 2008
Maintaining VB6 apps No supported method, per Microsoft
Runtime Critical fixes only, tied to Windows
Architecture 32-bit only, runs under WOW64
IDE unsupported since 2008
SYSTEM STATUS VB6.EXE
IDE SUPPORT . . : ENDED 2008
RUNTIME . . . . : CRITICAL FIXES ONLY
OCX VENDORS . . : MOSTLY GONE
SUCCESSOR . . . : FROZEN TOO
PRESS ANY KEY TO WORRY
Sources: Microsoft: VB6 support announcement · Microsoft: VB6 support policy · Microsoft: Visual Basic language strategy · IT Jobs Watch: VB6
Staying costs too

The risks of staying on VB6

  • No supported toolchain Microsoft states there is no supported method to maintain VB6 applications, and the IDE was never supported on 64-bit Windows. Every change is made on borrowed tooling.
  • Runtime support is narrow Microsoft fixes only serious regressions and critical security issues in its own runtime files, and only while the host Windows version is in support. Windows 10 left support in October 2025.
  • The controls are orphans Most real VB6 applications lean on third-party OCX and ActiveX controls. Microsoft explicitly does not support them, and many of the vendors no longer exist.
  • A 32-bit dead end VB6 binaries are 32-bit only and run under WOW64 emulation, which blocks 64-bit Office integration and modern server environments.
  • Even the successor is frozen Microsoft stopped evolving VB.NET as a language in 2020, so a like-for-like conversion lands on a platform with no forward roadmap.
Honest trade-offs

Your exit options, compared

OptionWhat it means RiskVerdict
Stay Keep running on the runtime inside supported Windows. Works until a control breaks or the developer leaves; no supported way to change the app. Borrowed time.
Refactor Machine-convert to VB.NET with a migration tool. Lands on a language Microsoft froze in 2020; converted code still needs hand-finishing. A sideways step.
Replace Off-the-shelf package, migrate the data. Decades of bespoke logic rarely fit a package. Works for simple systems.
Rewrite Rebuild as a modern web application, parallel run, then cut over. Managed by the parallel run; old system stays live. Our method.
The process

How the migration runs

  1. Audit

    A free 30 minute call plus a written one-page risk summary.

  2. Roadmap

    Code and data audit, migration options, fixed-price proposal. £1,950, credited against the build.

  3. Parallel run

    Your old system stays live until the new one has proven itself.

  4. Cutover & aftercare

    Switch over when ready. We stay on hand.

VB6 specifics: source lives in plain-text .vbp, .frm, .bas and .cls files, so behaviour can be read even where the IDE cannot run. The first technical step is a dependency audit of the OCX and ActiveX controls; data usually sits behind ADO or Jet and extracts cleanly into a modern SQL schema.

The safety net

The parallel run is the proof.

We do not ask you to trust a brochure. Your VB6 system stays live and primary while the new one runs alongside it, reconciled record by record until the comparison is boring. Cutover happens when you say so, with the old system kept as a fallback.

Read the Field Notes
Asked by VB6 owners

Questions

Our VB6 application still runs fine on Windows 11. Why worry?
Because the runtime is kept alive for existing applications only, with critical fixes at most. The moment you need a change, you are relying on unsupported tooling and a developer pool that has all but gone: IT Jobs Watch counted three UK permanent adverts citing VB6 in the six months to June 2026.
Should we convert to VB.NET instead?
Conversion tools exist and sometimes make sense. But Microsoft froze VB.NET as a language in 2020, so you would be paying to land on another platform without a future. The Roadmap compares that route honestly against a rebuild.
We have no source code, only the .exe. Now what?
The data can still be extracted and the behaviour rebuilt from the running system. It narrows the options but it does not close them.
What happens to our third-party controls?
They are catalogued in the audit. Their behaviour, grids, reports, charts, is rebuilt with supported modern equivalents rather than emulated.
How long does a VB6 migration take?
The Roadmap gives a range for your system. Parallel running means the timeline carries no downtime risk either way.

Get a straight answer on your VB6 system.

Book a free Legacy Risk Audit
Replies within one working day, from the engineer, not a sales team.