At a glance
Legacy sources: VB 1–6 · ActiveX · COM · VBA · VB.NET (legacy)
Modern targets: C# .NET 10 · Go (Golang) · Rust · Delphi 13 · TypeScript
Typical timeline: 6 weeks to 9 months depending on scope
Project range: $15,000–$250,000
U.S. delivery: 100% U.S. citizen workforce, U.S.-soil delivery
What to know before you modernize
Which Visual Basic you have, and what it implies
The version tells us most of what the first phase looks like. Microsoft ended support for the Visual Basic 6.0 and Visual Studio 6.0 IDEs on April 8, 2008. The VB6 runtime files are 32-bit only, so a VB6 application runs on 64-bit Windows only inside the WOW emulation layer. A program built with a 16-bit edition of Visual Basic is a harder case: 64-bit Windows does not run 16-bit x86 code of any kind, and Microsoft's documentation says 16-bit controls load only in 16-bit containers. Those programs, and the older VBX custom controls they use, need a port before anything else can happen. Visual Basic 5 and 6 projects are 32-bit and run, but the toolchain that builds them is no longer supported. Legacy VB.NET projects are a separate category and are covered below. We read the project files first, because the compiler version, the control list, and the data-access references decide which of these situations you are in.
DAO, RDO, ADO, and the Jet database
Visual Basic applications reach their data through one of three generations of library, and a single project often uses two. DAO talks to the Jet engine that Access uses and suits single-system or small local deployments. RDO is a thin layer over ODBC, common in client-server applications on SQL Server and Oracle. ADO is the successor to both, and Microsoft's own migration notes say it is not automatically code-compatible with DAO or RDO. The structural risk is Jet. Microsoft's SQL Server support documentation states that the OLE DB provider for Jet has no 64-bit version, and the Access Database Engine 2016 Redistributable, a common substitute, passed its end of support on October 14, 2025. A .mdb file behind a VB application is therefore a data-migration task to SQL Server or PostgreSQL, scheduled before any language work begins.
Automated conversion vs manual rewrite →
Controls and libraries outside the supported list
Microsoft's support statement sorts the VB6 files into groups. The core runtime ships in Windows. A second group, which includes MSCOMCTL.OCX, MSFLXGRD.OCX, MSCOMM32.OCX, and the RDO library MSRDO20.DLL, is supported but must be redistributed with the application. A third group, which includes DAO350.DLL and the Jet 3.5 files, is unsupported, with compatible updates available. A fourth group has no support at all: THREED32.OCX, SPIN32.OCX, GRAPH32.OCX, GAUGE32.OCX, GRID32.OCX, and VISDATA.EXE appear on that list. Microsoft explains that some unsupported files came from the \Tools folder of the VB4 and VB5 media or were third-party controls. Third-party OCX controls are also outside Microsoft's support. The assessment sorts every reference in the .vbp files into these groups, because the unsupported group is where the replacement work is.
VBA, Office macros, and 64-bit Office
Visual Basic for Applications is a different product from Visual Basic 6, and Office support policy governs it. It matters here because many VB6 applications automate Excel, Word, or Access, and many Office workbooks hold business logic in VBA that nobody lists as software. Office 2010, 2013, and 2016 install the 32-bit version by default; Office 2019 and Microsoft 365 default to 64-bit. VBA written before Office 2010 fails on 64-bit Office when it calls the Windows API, because Declare statements need the PtrSafe keyword and handles and pointers must change from Long to LongPtr. Adding PtrSafe alone silences the compiler but still truncates a 64-bit handle held in a Long. The same bitness rule applies to a VB6 program that automates Office: a 32-bit process cannot load a 64-bit Office library in process.
What the Visual Basic Upgrade Wizard did, and why it is not a plan
Visual Studio shipped a Visual Basic 6.0 upgrade wizard through the 2008 release, and Microsoft no longer ships it. It never produced C#. It read a .vbp file and created a new Visual Basic .NET project, leaving the original untouched, along with an upgrade report listing errors to fix and warnings to review. Microsoft's documentation states that the wizard cannot catch all incompatibilities and that the upgraded program must be run and compared against the original. Upgraded projects lean on the Microsoft.VisualBasic.Compatibility.VB6 namespace, which exists to emulate control arrays, fixed-length strings, and ADO data binding. That namespace is documented for .NET Framework. If you hold an upgraded project from that era, it is a candidate for the same refactoring as any other converted codebase, with the compatibility shims removed as the first step.
AI-assisted modernization for Visual Basic systems →
Legacy VB.NET and the .NET Framework
A VB.NET application built on .NET Framework 2.0 through 4.x is in a different position from VB6. .NET Framework 4.8 and 4.8.1 are supported as components of Windows for as long as the Windows version that carries them is supported, and 4.8.1 is installed in current Windows 11 releases. The pressure on these applications is direction, not an expiry date. Microsoft's Visual Basic language strategy describes a stable language with a consumption-only approach to new features, no new syntax, and no extension to new workloads such as web front ends or cross-platform UI frameworks. A Windows Forms application can move to current .NET and stay in Visual Basic. An application that needs a browser front end, Linux hosting, or a hiring pool that writes C# is migrated to C#. The assessment records which of those goals applies.
Why Visual Basic applications are still in service
Visual Basic applications, once the backbone of business-critical software in the 1990s and 2000s, powered client-server apps, utilities, and workflows across many industries. They are still running because they work and because the business rules inside them were never written down anywhere else. What has changed is the ground under them: the IDE has been unsupported since 2008, the runtime is 32-bit only, third-party controls have lost their vendors, and the Jet database behind many of them has no 64-bit provider. Modernizing them is about removing those dependencies while keeping the rules intact, and the gains are specific to each system: a supported toolchain, a database other tools can read, and an application the current team can change.
Understanding the Visual Basic ecosystem
The Visual Basic ecosystem, designed for 16-bit and 32-bit Windows environments, used VB-specific libraries and third-party controls such as ActiveX. The lack of modern IDE support and the shrinking pool of developers who know it are the practical problems. These applications are often incompatible with 64-bit processes and depend on legacy Windows behavior. Our approach across 14 verticals has been the same: preserve the business logic first, then modernize the platform around it.
Obstacles in Legacy Visual Basic Applications
Legacy Visual Basic applications now face significant challenges due to their reliance on outdated hardware and software. They often run on unsupported 16-bit or 32-bit systems, making replacement parts difficult to source and increasing the risk of system failures. The lack of support poses serious security vulnerabilities, while maintenance costs rise as fewer developers possess the expertise to manage these aging systems, particularly in sectors like manufacturing and government where reliability is crucial.
Transforming Visual Basic applications
Our Visual Basic modernization work migrates applications to C# .NET, Go, or Rust. The transition preserves the business logic while moving the application onto a supported runtime that can run on Windows, macOS, Linux, or mobile devices and in the cloud. Where the domain warrants it, we re-architect around the business processes, with event-based patterns such as CQRS and event sourcing applied only to the parts that need history or integration. AWS or Azure hosting is available where it fits.
Start with an assessment for a Visual Basic codebase
For a Visual Basic codebase the read-only assessment inventories the facts that decide the path: the Visual Basic edition and the 16-bit or 32-bit build of each project, every reference in the .vbp files grouped by Microsoft's supported, redistributable, unsupported, and third-party categories, ActiveX and COM interfaces in both directions, DAO, RDO, and ADO usage, the Jet or Access files and the server databases behind them, Declare statements and other Windows API calls, VBA and Office automation, reports and printing, the installer, and whatever tests exist. Everything is read from source, project files, and configuration; nothing is run and nothing in production is touched. The result is a written recommendation to keep and document, bridge, or migrate. The fee is quoted after the free 1-hour consultation and creditable toward a subsequent modernization project.
Deliverables
- Target codebase in C# .NET 10, Go, Rust, or Delphi 13
- Cross-platform support (Mac OS X, Linux, Windows, mobile)
- Business-logic preservation with parity testing
- Event-based architecture (CQRS, event-sourcing) where useful
- AWS or Azure integration for scalability
Common questions
Is Visual Basic 6 still supported by Microsoft?
Partly. The VB6 IDE has been unsupported since April 8, 2008. The runtime files that ship inside Windows, including Windows 11, are supported for the lifetime of each Windows version, limited to serious regressions and critical security issues. The runtime is 32-bit only and runs under WOW on 64-bit Windows. Third-party controls are not covered by Microsoft's statement.
Can Visual Basic be converted to C# automatically?
Tools can translate the syntax, but the output needs work. Microsoft's own wizard, which shipped through Visual Studio 2008, produced Visual Basic .NET rather than C#, and its documentation says it cannot catch every incompatibility. Converted code keeps VB6 structure, such as global state and logic inside event handlers, so it still needs refactoring and parity testing against the original behavior.
What happens to our Access or Jet database when we migrate a VB application?
It moves to a server database such as SQL Server or PostgreSQL. The Jet OLE DB provider has no 64-bit version, so a .mdb file cannot stay behind a 64-bit application. The migration covers schema, data, and the queries that relied on Jet behavior, and it is rehearsed and compared before cutover rather than done on the day.
Will our Excel or Access VBA macros work in 64-bit Office?
Only if they are updated. VBA written before Office 2010 breaks on 64-bit Office wherever it declares Windows API functions. Each Declare statement needs the PtrSafe keyword, and handles and pointers must be declared LongPtr instead of Long. Macros that avoid API calls usually need no change, and the assessment lists which ones fall in each group.
Can the Visual Basic application keep running during the migration?
Yes. Because the VB6 runtime stays supported with each Windows version, the original can remain in production while its replacement is built and tested beside it. The new system is checked against the old one on the same inputs, then modules or sites are moved over in stages. The original is retired only after the parity results are accepted.
How much does a Visual Basic migration cost and how long does it take?
The bands on this page apply: $15,000–$250,000, and 6 weeks to 9 months depending on scope. A small utility with one database sits at the low end. A multi-module application with third-party controls, reports, and Office automation sits at the high end. The price and schedule are fixed after the Legacy Software Assessment.
Should we move Visual Basic to C# or stay on VB.NET?
Move to C# if you need a browser front end, Linux or cloud hosting, or developers who write C#. Microsoft's language strategy puts Visual Basic in a stable, consumption-only mode with no new syntax and no new workloads, such as web front ends or cross-platform UI frameworks. Staying on VB.NET is reasonable for a Windows Forms application that only needs a supported runtime.
Sources
- Microsoft: Support Statement for Visual Basic 6.0: IDE unsupported April 8, 2008; runtime 32-bit only and WOW; supported/redistributable/unsupported file groups; third-party controls; VBA hosting rules
- Microsoft: ADO Compared with RDO and DAO (VB6 docs): DAO/RDO/ADO roles; ADO not automatically code-compatible
- Microsoft: MSJET 4.0 in 64 bit environment: Jet OLE DB provider has no 64-bit version
- Microsoft Download Center: Access Database Engine 2016 Redistributable: Support ended October 14, 2025
- Microsoft: 64-bit VBA overview: PtrSafe, LongPtr, Office default bitness
- Microsoft: Visual Basic Upgrade Wizard (VS 2008): Wizard creates new project; upgrade report; cannot catch all incompatibilities
- Microsoft: VB 6.0 migration resource center note: Wizard shipped through 2008; no longer shipped
- Microsoft: Microsoft.VisualBasic.Compatibility.VB6 namespace: Compatibility shims for upgraded VB6 projects; .NET Framework docs
- Microsoft: Visual Basic language strategy: Stable design, consumption-only, no new workloads
- Microsoft: .NET Framework support policy: 4.5.2+ is a Windows component; 4.8.1 supported while Windows is supported
- Microsoft: Install .NET Framework on Windows: 4.8.1 included in Windows 11 22H2 and later
- Microsoft: NTVDM and 16-bit app support: x64 and ARM Windows do not run 16-bit x86 code
- Microsoft: Porting and Upgrading OCXs and VBXs: 16-bit controls only in 16-bit containers
Not sure where to start?
Start with a fixed-scope Legacy Software Assessment: a read-only review of your application’s source, database, configuration, logs, and architecture, ending in findings with evidence and a written recommendation. Quoted after the free 1-hour consultation; creditable toward a subsequent modernization project.