VB6 applications are unusual among legacy systems because they still run. Microsoft stopped supporting the Visual Basic 6.0 development environment on April 8, 2008, yet its runtime still ships with Windows. According to Microsoft’s Support Statement for Visual Basic 6.0 on Windows, that runtime is supported for the lifetime of supported Windows versions.
That compatibility is a reason many VB6 applications are still in production decades later. It also hides the risk. There is no supported way to build or maintain VB6 code, the runtime is 32-bit only, and Microsoft does not support the third-party ActiveX controls most VB6 applications depend on. Microsoft’s own support statement strongly recommends replacing VB6 applications with modern technology.
This guide was prepared by the Ticomix team based on hands-on experience modernizing VB6 and other legacy business applications. It explains how a VB6 to .NET migration works, how to choose between VB.NET and C#, where these projects tend to go sideways, and how to plan one without disrupting the business processes that still depend on the application.
What Does a VB6 to .NET Migration Involve?
A VB6 to .NET migration rebuilds a Visual Basic 6.0 application on the Microsoft .NET platform without losing the business logic that makes it valuable.
It isn’t a line-by-line translation that carries every workaround and outdated design decision into a new environment. A successful migration starts by understanding how the application supports the business today, then rebuilds it on a modern architecture designed for current needs and future growth.
A typical migration includes four major components:
- Data: Legacy data sources such as Microsoft Access (Jet) databases, older SQL Server versions, or flat files are migrated to a modern SQL Server or cloud database.
- Business Logic: Rules contained in VB6 forms, modules, and classes are rewritten in C# or VB.NET.
- Integrations: The new application connects with today's business ecosystem, including REST APIs, Microsoft 365, cloud platforms, reporting tools, and AI-powered business applications.
- User Interface: Aging VB6 forms and ActiveX controls are replaced with modern web or desktop interfaces.
For many organizations, a VB6 migration is the first phase of a broader legacy application modernization initiative. It’s an opportunity to redesign workflows around today’s requirements instead of preserving decisions made twenty-five years ago by default.
To learn more about Ticomix’s approach, visit our VB6 migration services page or compare VB6 modernization vendors if you’re still evaluating options.
Why Move from VB6 to .NET?
VB6 was one of the most widely used tools for building Windows business applications in the late 1990s and early 2000s, and many of those systems still run critical operations. When it’s time to move off VB6, .NET is the natural destination for several practical reasons.
A Direct Microsoft Successor
.NET is Microsoft's replacement for VB6, and VB.NET was designed as its successor language. Teams with VB6 experience will recognize much of the syntax and many of the concepts, even when the application moves to C#.
Long-Term Platform Stability
Microsoft actively develops and supports .NET through its published Long-Term Support (LTS) policy, making it a stable platform for organizations planning years ahead.
Fits Existing Microsoft Environments
Organizations already using SQL Server, Azure, Microsoft 365, or Active Directory can modernize without introducing an entirely new technology stack.
Modern Integration and 64-Bit Support
VB6 applications are limited to 32-bit and struggle to connect with modern APIs and cloud services. Modern .NET applications run natively on 64-bit systems and integrate with third-party services far more easily.
Stronger Long-Term Talent Availability
Experienced VB6 developers are becoming harder to find every year. .NET developers are far more common, making future maintenance, enhancements, and hiring substantially easier.
Modernizing also costs less than it used to. Across completed Ticomix REV projects, AI-assisted conversion has reduced development time by roughly 40% compared to a conventional rewrite.
Together, these advantages make VB6 to .NET migration the most common modernization path for organizations that want continuity without trading one niche technology for another.
Can You Keep Running VB6 Instead?
In the short term, often yes. Microsoft’s goal is that existing VB6 applications “just work” on supported Windows versions, and the core runtime is supported for the support lifetime of Windows. If your application is stable, rarely changes, and doesn’t need new integrations, keeping it running while you plan may be a reasonable decision.
The risk is in what that support doesn’t cover:
- No supported development environment. The VB6 IDE is no longer supported, so every fix or enhancement is made with unsupported tools.
- No third-party control support. Microsoft does not support third-party OCX and ActiveX controls, which most VB6 applications rely on for grids, reporting, and charting.
- 32-bit only. VB6 runtime files remain 32-bit, which limits memory, performance, and compatibility with 64-bit components.
- Shrinking expertise. Each year, fewer developers can safely maintain VB6 code.
The question is less whether VB6 still runs and more whether the business can afford to keep depending on it.
If you’re unsure which option makes the most sense, a REV Assessment maps what your VB6 application does today and gives you a clear scope, cost, and plan before you commit.
VB.NET or C#: Choosing a Target Language
Both VB.NET and C# run on the same .NET platform and can use the same libraries, databases, and cloud services. The choice affects who can maintain the application long term more than what the application can do.
| Consideration | VB.NET | C# |
|---|---|---|
| Familiarity for VB6 developers | High: similar keywords and syntax | Lower: different syntax, same concepts |
| Size of developer pool | Smaller and shrinking | Much larger |
| Microsoft's language investment | Stable, with fewer new features | Where most new language features land first |
| Examples, libraries, and community support | More limited | Extensive |
| Best fit | Small in-house teams with deep VB experience | Most new and long-lived business applications |
VB.NET can look like the easier path because the syntax is familiar. But VB.NET is not VB6, and the code still has to be restructured for .NET either way. For most organizations, C# offers stronger long-term hiring and support, which is why it’s the more common target for business-critical applications.
The right answer depends on who will own the application after migration. If your internal team will maintain it and knows VB well, VB.NET can be a practical choice. If you expect to hire, outsource, or grow the system significantly, C# is usually the safer bet.
Desktop, Web, or Both?
The target language is only half the decision. Many VB6 applications move to a modern Windows desktop application, which keeps familiar workflows for users who work at a desk all day. Others move to a web application, which removes installation, supports remote and mobile users, and simplifies updates. A phased migration can also start with the desktop and add web access later.
Can VB6 Be Converted to .NET Automatically?
Partly, but automated conversion is rarely the whole answer. Microsoft once included an upgrade wizard in early versions of Visual Studio .NET, but it was removed years ago, and its output typically needed significant rework. Commercial conversion tools exist today, and they can translate large amounts of syntax quickly.
The limitation is what conversion carries forward. A straight translation moves twenty-five years of workarounds, dead code, and outdated design into a new language, then leaves your team maintaining VB6-shaped code in .NET. ActiveX controls, data access, and reporting usually still have to be replaced by hand.
Most VB6 migrations fall into one of three approaches:
- Automated conversion: Fastest to a first build, but the result often needs heavy cleanup and keeps the old architecture.
- Full rebuild: The cleanest result, with the business logic rebuilt on a modern design. It requires a thorough understanding of what the old application does.
- AI-assisted rebuild: AI tools analyze the VB6 codebase and accelerate parts of the rebuild, while experienced engineers validate the business logic and architecture. This is the approach behind the Ticomix REV methodology.
Any of the three can be done in phases, modernizing one module or business function at a time.
The VB6 to .NET Migration Process, Step by Step
Successful VB6 migrations begin long before any code is rewritten. A structured process preserves years of business logic while reducing project risk.
- Assess the Application. VB6 systems accumulate years of undocumented business logic, often spread across forms, modules, and third-party controls. Before any code changes hands, the assessment surfaces what every form and module does, how the data connects, and which rules users depend on without realizing it. This phase typically includes:
- Reviewing forms, reports, and workflows
- Inventorying ActiveX controls, COM components, and DLL dependencies
- Mapping database structures and data access code
- Identifying business rules
- Documenting existing integrations
- Design the Data Architecture. Many VB6 applications store data in Microsoft Access (Jet) databases or older SQL Server versions, often through DAO, RDO, or ADO code. Rather than simply copying data, this phase creates a modern database that supports performance, reporting, integrations, and growth. Typical work includes:
- Designing the database schema
- Cleaning and validating legacy data
- Improving data integrity
- Preparing for future integrations
- Rebuild the Application. Once planning is complete, the application is rebuilt on modern .NET technologies. This typically includes:
- Rewriting business logic in C# or VB.NET
- Replacing ActiveX controls with modern .NET components
- Building a modern desktop or web interface
- Replacing legacy reporting tools
- Implementing security
- Integrating with APIs and cloud services
- Test and Deploy. Before deployment, the new application is validated against real business workflows. Testing confirms that:
- Business rules behave correctly
- Reports remain accurate
- Users can complete daily tasks
- Performance meets expectations
- Integrations function properly
Where AI helps: AI-assisted conversion can accelerate the assessment and rebuild phases, particularly when analyzing large VB6 codebases or generating initial code. Used correctly, AI improves developer productivity while experienced engineers validate the business logic and architecture.
Many organizations reduce risk further through phased deployments, running the old and new systems side by side until users are confident in the new one.
Common VB6 to .NET Migration Challenges
Most migration risks are predictable and can be avoided with proper planning.
Hidden Business Logic
Years of undocumented business rules often sit behind form events and button clicks. A thorough discovery phase ensures those rules are found and preserved.
ActiveX Controls and COM Dependencies
Most VB6 applications rely on third-party OCX and ActiveX controls for grids, charts, calendars, and reports. Many of those vendors no longer exist, and none of the controls carry over to .NET. Replacing them is often the most underestimated part of the project.
Language Differences
VB.NET looks like VB6 but behaves differently in important ways. Variant data types, On Error error handling, default properties, fixed-length strings, and late binding all need to be reworked, whether the target is VB.NET or C#.
Legacy Data Access
DAO, RDO, and classic ADO code has to be replaced with modern data access such as ADO.NET or Entity Framework. Older Access databases also tend to contain inconsistencies that only surface during migration, so cleaning and validating data early avoids downstream issues.
Legacy Reporting
Many VB6 applications use older Crystal Reports versions or the built-in Data Report designer. Reports are business-critical and need to be rebuilt and verified against the originals.
User Adoption
Successful modernization improves the user experience without disrupting familiar workflows. Involving users throughout the project encourages adoption.
Want to see what these systems look like in practice? Browse real examples of legacy systems still running in businesses today.
When Does a VB6 to .NET Migration Make Sense?
Modernization is often the right choice when:
- The application supports critical business operations.
- It depends on ActiveX controls or components that are no longer maintained.
- Security or compliance requirements have increased.
- Integration with modern systems, APIs, or cloud services has become difficult.
- Finding developers who can safely change VB6 code is becoming challenging.
- The application is limiting future growth.
When several of these conditions exist, modernization becomes a business decision rather than simply a technology upgrade.
FAQs about VB6 to .NET Migration
Is VB6 still supported by Microsoft?
Partly. The VB6 runtime ships with Windows and is supported for the lifetime of supported Windows versions, so existing applications keep running. The VB6 development environment is no longer supported, and Microsoft does not support third-party ActiveX controls. Microsoft recommends replacing VB6 applications with modern technology.
Will VB6 applications run on Windows 11?
In most cases, yes, because the core VB6 runtime is included and supported on current Windows versions. Problems usually come from third-party controls, 32-bit limitations, or installers that no longer work cleanly. Those issues tend to grow over time rather than disappear.
How long does a VB6 to .NET migration take?
The timeline depends on the application's size, complexity, and business requirements. Smaller applications may be completed in 8 to 16 weeks, while larger, business-critical systems often take 6 to 12 months or more. A discovery assessment is the best way to develop an accurate project plan.
What does a VB6 to .NET migration typically cost?
Every application is different. Cost depends on application size, complexity, the number of ActiveX controls and integrations, and modernization goals. As a general range, cost can be as low as $10,000 for simple applications, up to the low six figures for larger, more complex ones.
Should we migrate VB6 to VB.NET or C#?
VB.NET is more familiar to VB6 developers, but C# has a much larger developer pool and receives more of Microsoft's language investment. Most organizations choose C# for business-critical applications they expect to maintain for years. VB.NET can make sense when a small internal team with deep VB experience will own the application.
Can a VB6 application be migrated in phases?
Yes. Many organizations modernize one module or business function at a time. This approach reduces risk, minimizes disruption, and lets users benefit from the new application sooner.
Can existing VB6 data be preserved?
In most cases, yes. Data stored in Microsoft Access, older SQL Server versions, or other sources can typically be migrated to SQL Server or another modern database while preserving historical records and business relationships.
Do you modernize other legacy platforms besides VB6?
Yes. Along with VB6, Ticomix provides Visual FoxPro migration, Delphi to .NET migration, and Microsoft Access modernization, helping clients move from desktop-era technologies to modern, future-ready platforms.
About the Author
This guide was prepared by the Ticomix team based on hands-on experience extending and modernizing legacy business applications since 2001, including VB6, Visual FoxPro, Delphi, and Microsoft Access systems.
Over the years, our team has helped organizations across industries preserve valuable business logic while modernizing legacy applications for improved scalability, integration, and long-term support. Examples include modernization projects completed for BP Aero, USC, and Lodeso. See our work.
Estimate Your VB6 Modernization ROI
Before committing to a migration, it helps to understand both the cost of modernization and the cost of maintaining an aging application.
Within minutes, our VB6 Modernization ROI Calculator estimates:
- Support costs
- Productivity losses
- Modernization investment ranges
- Potential return on investment
The calculator is based on assumptions drawn from more than 25 years of legacy application modernization experience, helping organizations build a practical business case before starting a project.