Legacy modernisation VB6 / VBA migration COM-free end state

Replace your Visual Basic application with modern software

VB6, VBA and classic ASP still run daily at hundreds of Dutch companies. These applications have served faithfully, often for more than twenty years. But the Visual Basic 6 IDE has been officially out of support since 2008, the runtime only gets "best-effort" support on Windows 11, and the pool of developers who still know VB6 and COM shrinks every year. We replace your Visual Basic application with a maintainable web application or desktop app, preserving all business logic and data.

Form1.frm → app.tsx
Private Sub cmdSave_Click()
On Error Resume Next
rs.AddNew
rs!Naam = txtNaam.Text
End Sub
async function saveCustomer() {
await api.post('/customer',
{ naam: form.naam })
}

VB6 is officially obsolete: what does that mean for your legacy application?

Visual Basic 6.0 was released in 1998 and for years was the fastest way to build Windows applications with forms, databases and COM components. But that era is over. Microsoft ended mainstream support for the VB6 IDE in 2005, followed by extended support in 2008. Since then only the runtime has still shipped with Windows, and even that comes with increasingly clear disclaimers.

What the official status actually means

  • ! VB6 IDE: end-of-life since 2008 — no patches, no security fixes, no MSDN support any more. The MSDN archive is read-only.
  • ! VB6 runtime on Windows 11/12: best effort — Microsoft still ships MSVBVM60.DLL, but promises no functional guarantees across feature updates.
  • ! VBA is getting less attention — Office continues to support VBA, but Microsoft is actively pushing Office Scripts (TypeScript) and Power Automate as its successors.
  • ! 32-bit only — VB6 binaries only run in 32-bit; in fully 64-bit Windows environments this requires a WoW64 compatibility layer.

The silent stack of risks

  • ! Hardware driver incompatibility — old COM add-ins for scanners, weighbridges, cash drawers and barcode printers no longer work with modern USB stacks or TWAIN versions.
  • ! Developer scarcity — staff who understand VB6, COM and ADODB.Recordset are retiring. Finding replacements through a recruitment agency is almost impossible.
  • ! Security patches are no longer coming — known vulnerabilities in MSCOMCTL.OCX, Crystal Reports controls or old ActiveX components are no longer patched.
  • ! Audit pressure — ISO 27001, NIS2 and SOC 2 audits score unpatched runtime components as a compliance risk.

In practice: as long as your VB6 application keeps running, there is little to notice. Acute pressure only arises once Windows ships a breaking change, a COM control no longer registers, or the last employee with VB6 knowledge leaves. At that point a calm migration process is no longer an option. We help you replace it before that moment arrives. Also read our page on replacing legacy software for the broader context of legacy modernisation.

6 reasons to replace your Visual Basic application now

No migration project is cheap. But with VB6 and VBA, the clock is ticking. These are the six most common triggers that lead our clients to decide to replace.

Uncertain runtime on Windows 11/12

Windows feature updates can break MSVBVM60.DLL, OCX controls or the IDE. You no longer have a contractual right to a fix. What works today may be broken after the next KB update.

Scarcity of VB6 knowledge

Developers who are still fluent in VB6, with COM/OLE and manual ADODB recordset management, are retiring. Finding a successor with a market-standard job ad has become virtually impossible in 2026.

Security: no more patches

Known CVEs in old ActiveX controls, Crystal Reports versions or MSCOMCTL.OCX are no longer fixed. For NIS2, ISO 27001 and BIO programmes, an unpatched runtime is a red flag.

Hardware and drivers no longer cooperate

VB6 applications often rely on COM add-ins for specific hardware: scanners, cash drawers, barcode printers, weighbridges, RS-232 terminals. Modern 64-bit Windows with USB stack overhauls breaks those TWAIN or SerialPort integrations. A fix is no longer available from the original supplier.

!
TWAIN scanners without a 64-bit driver
!
Old OCX controls for weighbridge or counting machine readout

No browser, no mobile, no cloud

VB6 applications are fat clients with a Windows installation on every workstation. Home workers, field engineers, warehouse staff with a tablet, or customers who need to log in themselves cannot reach the application without a VPN, RDS or Citrix — and that adds up in licence costs.

!
No mobile workplace possible
!
Citrix/RDS licences as an expensive stopgap

Integrations with modern SaaS get stuck

REST/JSON, OAuth 2.0, webhooks, GraphQL, JWT tokens: this is the standard vocabulary of modern SaaS. VB6 speaks it through intermediate layers or not at all. If you want to integrate with a new accounting package, CRM, e-signing platform or invoice portal, the project stalls on the fact that the VB6 side can't keep up.

Our migration approach: from code archaeology to parallel run

VB6 projects are rarely well documented. The original developer has usually left, and the business logic is scattered across form events, modules and dynamic SQL built through string concatenation. That's why our approach is always reverse-first: we understand first, then we rebuild.

1

Code archaeology

We take the VB6 project files (.vbp, .frm, .bas, .cls), inventory all form events and module functions, and map which COM references are active. We count the Form_Load and _Click handlers, find all the GoSub/GoTo spaghetti and flag the On Error Resume Next blocks that silence errors. Everything goes into a readable inventory report.

2

Business logic extraction

Beyond the visible forms, the business value lies in the calculations, validations and workflows. We extract that logic, write it down in pseudocode or TypeScript and validate it against production data. Only what demonstrably works and is actually used comes along; dead code stays behind.

3

COM dependency inventory

Which OCXs, type libraries and COM/OLE servers does your application use? Crystal Reports version, MSCOMCTL, ADODB, MSXML, RDO, old DAO 3.6: we build a complete dependency graph and decide for each item whether to replace it, flatten it or build a runtime shim.

4

Parallel run and data migration

The new application runs alongside the old one for several weeks. Users either enter data in both systems, or the old one is mirrored to the new one nightly. Only when the discrepancy is zero and users are confident does the old application go offline. MDB or ACCDB files are migrated to PostgreSQL or SQL Server using a validated transformation.

For clients with a Microsoft Access front end on a shared MDB, we often work in two steps: first we replace the back end (see Replacing an Access database), then the VB6/VBA front end. This lowers the risk and spreads the investment.

What we replace: forms, controls, data access and reports

A VB6 application consists of a number of fixed components. For each one, we have a modern counterpart ready.

Forms and controls

.frm files with TextBox, ListBox, DataGrid, MSFlexGrid, DTPicker and all their custom OCX extensions are replaced by React or Blazor components with the same layout, validations and keyboard shortcuts. Speed and mouse-free operation are retained, because checkout staff and planners often work using the keyboard alone.

VBA modules and COM add-ins

VBA macros in Excel or Word, COM add-ins for Office and custom-written DLLs in VB6 or VC++: we extract the logic, rewrite it in TypeScript or C# and move it to a server. Office integration can go via Office Scripts, Microsoft Graph or a custom API.

DAO/ADO data access

ADODB.Recordset, DAO 3.6 on MDB files or direct ODBC connections with inline SQL: we replace the entire data layer with an API using parameterised queries, prepared statements and an ORM such as Prisma or Entity Framework. SQL injection via string concatenation disappears and transaction management becomes explicit.

Crystal Reports and reporting

Crystal Reports 8/9/10/11 reports, Active Reports, or custom-written print routines on a form: we convert the output to modern PDF rendering (Puppeteer, wkhtmltopdf, Microsoft Reporting Services), interactive dashboards (Metabase, Power BI Embedded) or simply a clean HTML print view. Layouts stay pixel-identical where that's needed for compliance or customer documents.

Hardware integrations

Barcode scanners, cash drawers, weighbridges, RFID readers, label printers (Zebra, Honeywell), TWAIN scanners, RS-232 terminals: we reconnect them via WebUSB, WebSerial, a local device agent or an MQTT broker on a Raspberry Pi gateway. That way your industrial app keeps running without depending on 32-bit OCX controls.

Typical VB6 applications we replace

Three use cases we come across often, with the choices we make in each.

Industrial app on the shop floor

A VB6 application on an industrial PC in a production hall, connected to a SCADA system, a weighbridge and a MES database. Replaced by an Electron app or Progressive Web App with a local device agent (Node.js or Rust) that handles serial ports and MQTT topics. Front end in the browser, back end on a local Linux server, replication to Azure or AWS for management reporting.

Point-of-sale and order entry system

VB6 on a Windows till with OCX controls for the cash drawer, receipt printer and card terminal. Replaced by a browser app on Chrome OS Flex or Windows IoT, with WebUSB for the card terminal integration, an ESC/POS receipt printer via a local agent, and a central REST API for stock and payments. Offline-first with Service Workers, so the till keeps working during an internet outage.

Production planning and order management

A VB6 front end on a shared Access MDB, used by planners and work preparation. We first replace the back end with PostgreSQL or SQL Server (see custom ERP system), then the front end with a React application with real-time updates via WebSockets. Planning, order intake, capacity overview and exports to Excel or the ERP remain familiar to users.

Back office for financial administration

VBA macros in a large Excel file with formulas, integrations with SQL Server and automated reports to the accountant and management. We recode the logic into a web app with explicit data typing, audit trails and role-based authorisation. To keep the Excel feel, we retain keyboard navigation and spreadsheet grids with copy-paste support. Also read about building custom software for the broader context.

Visual Basic 6 versus a modern web application

Aspect Visual Basic 6 / VBA Modern web application
Microsoft support IDE end-of-life since 2008, runtime best-effort on Win 11/12 Actively maintained frameworks (React, .NET, Node)
Workstation Windows-only, fat client per PC, 32-bit Browser, mobile, tablet, laptop, kiosk
Data layer DAO/ADO with inline SQL, vulnerable to injection API with parameterised queries and ORM
Error handling On Error Resume Next makes errors invisible Try/catch with central logging and alerting
Deployment Setup.exe per workstation, COM registration required Browser load or CI/CD deployment, no client installation
Auditability No built-in audit log, often manual Audit trail per record, NIS2/ISO 27001-ready
Talent Scarce, average age over 50 Plentiful in the Netherlands

Frequently asked questions about VB6 and VBA replacement

On Windows 11, MSVBVM60.DLL still runs and most VB6 applications start without problems. But Microsoft classes runtime support as "best-effort": no contractual guarantee, no security fixes for the IDE components, and specific OCX controls can break with Windows feature updates. Nothing has been promised for Windows 12 at the time of writing. For business-critical applications, that is too thin.

First we establish which version you are running (Crystal 8.5, 9, 10, 11, XI or newer) and which data sources it touches. Then we decide per report: convert it to PDF rendering with Puppeteer or wkhtmltopdf, to an interactive dashboard in Metabase or Power BI, or to server-side reporting via Microsoft Reporting Services. Layout-faithful where it has to be for customer documents or compliance, simpler where it can be.

Yes. Business logic extraction is at the heart of our approach. We read through the VB6 code line by line, write the logic down in pseudocode or TypeScript and validate the results against production data. MDB or ACCDB databases and SQL Server tables are migrated using a validated transformation and spot checks. During the parallel run, the old and new systems run side by side until the results are identical.

That is the rule rather than the exception. Our code archaeology phase is designed for exactly this: we open the .vbp, .frm, .bas and .cls files, map all form events and module functions, trace COM references and use them to build readable functional documentation. We then interview the end users to establish what is actually used in practice and which edge cases they know about.

Yes. We usually replace VBA macros in Excel or Word with a web application or an Office Script (TypeScript) when the workflow needs to stay inside Office. For VBA in Microsoft Access, we first look at whether we can decouple the Access back end (see our page on replacing an Access database). We then replace the Access front end with a browser-based application with the same forms and reports.

For modern hardware, we use WebUSB or WebSerial in a Chrome or Edge browser. For older peripherals, we install a local device agent (Node.js, .NET or Rust) that runs on the Windows or Linux workstation and serves the browser via a local WebSocket or REST endpoint. For industrial environments, we often place an MQTT broker on a Raspberry Pi or industrial gateway in between, so the browser app stays stateless.

Yes. We always work with a parallel run. Your existing VB6 application stays live until the new application has been fully verified. We synchronise data nightly or in real time, users practise on the new environment, and we only switch off the old application once everything gets the green light. No big-bang go-live where everything can go wrong at once.

By default, we use React or Next.js for the front end, Node.js or .NET for the back end, PostgreSQL or SQL Server for the database, and Azure or AWS in a Dutch or EU data centre for hosting. We stay agnostic where we can: if your IT department already manages .NET or Java stacks, we align with those. The starting point is that the new application must remain maintainable for ten years with talent that is available in the Netherlands in 2026 and beyond.

Ready to replace your Visual Basic application?

Let Appfront analyse and rebuild your VB6, VBA or classic ASP application into a maintainable modern application. We start with a legacy scan, after which you know exactly what the risks are and what the approach will cost. No big bang, but a calm parallel run that preserves your business logic and data.

Edit content