Ace8 is the modernization practice of AceMQ.24/7 support from AceMQ after go-live
Book an Assessment
ServiceVB6 migration

VB6 migration to .NET, planned before it starts

Most VB6 risk hides in COM components, ActiveX controls and data access. We list them first, then plan the move to .NET.

  • Fixed-price assessment first
  • Tests before any code change
  • An engineer signs every slice
claims-desk · vb6-exitAssess first, partner delivers
Visual Basic 6.NET 8
  • frmClaim.frmremoved
  • modData.basremoved
  • ClaimForm.cs+112−0
  • ClaimRepository.cs+47−0
  • Build
  • Tests match baseline
  • Senior engineer sign-off
Illustrative run. Names and figures are examples, not client data.

Stacks we work in

  • .NET
  • COBOL
  • Java
  • Spring Boot
  • Kubernetes
  • PostgreSQL
  • Kafka
  • Docker
  • Terraform
  • GitHub Actions
The short answer

A VB6 migration moves Visual Basic 6 applications to .NET, usually C# or VB.NET, after an inventory of code, COM and ActiveX dependencies and data access. Ace8 does the assessment and plan, and a vetted .NET partner delivers. Ace8 claims no past VB6 projects. The first phase is a fixed price after a scoping call.

Facts

What does Microsoft say about VB6 on Windows today?

Microsoft's support statement says the VB6 runtime is supported for the lifetime of supported Windows versions, while the IDE has been unsupported since 8 April 2008. The statement is at Microsoft Learn.

ItemMicrosoft's position
VB6 IDENot supported since 8 April 2008; no supported way to create or maintain VB6 apps
VB6 runtime files in WindowsSupported for the support lifetime of the Windows version; limited to serious regressions and critical security issues
64-bit WindowsRuntime is 32-bit only; apps are supported only under the WOW emulation environment
Third-party OCX and ActiveX controlsNot supported by Microsoft; contact the control vendor
Some listed runtime filesMicrosoft lists several files as unsupported, so a component may fall outside the support bar

Inventory

What do you inventory in a VB6 application?

The inventory covers every project, form, class, COM component, ActiveX control and database connection. Each one gets a status: supported by Microsoft, replaceable, or needing a rewrite.

01

COM and ActiveX

Registered DLLs and OCX files, their vendors and whether a .NET version exists.

02

Data access

DAO, RDO and ADO usage, ODBC drivers, Jet or Access files, stored procedures.

03

Forms and reports

Screens, grids, report writers and printing.

04

Win32 API calls, file and registry use, and anything that touches hardware.

05

Deployment

Installers, shared runtime files and the Windows versions in use.

Want this mapped for your applications? Get a fixed scope and price before anything moves.

Options

How should VB6 code move to .NET?

The choice is between automated conversion, a staged rewrite and leaving it in place for now. Which fits depends on how much logic sits in forms and how many components have no .NET equivalent. See .NET modernization for the wider target options.

01

Automated conversion to VB.NET gets running code quickly but leaves VB6 idioms in the result.

02

A staged rewrite to C# on current .NET suits applications that must change a lot.

03

Leaving it on a supported Windows version is a short-term choice, limited by the support terms above.

How it runs

Assess, modernize, run. One team throughout.

Ace8 scopes and delivers the move. AceMQ engineers support the new stack 24/7 from day one.

01Fixed price

Assess

Scope, cost and AI readiness, before any migration starts. Characterization tests and a baseline before we touch a line.

02Ace8

Modernize

AI-assisted, engineer-verified, one capability at a time. Tools draft the rewrite and a senior engineer signs every change.

03AceMQ · 24/7

Run

Tested, reversible cutover. AceMQ engineers support the new stack from day one. Supported after migration →

Method

How does the migration stay safe?

We record real inputs and outputs first and compare them after each slice, in line with the Ace8 method. Data access gets particular attention, because cursor, rounding and null behaviour can differ between old drivers and ADO.NET.

Step 01 of 04

Assess

Inventory the code and score each application. This is the fixed-price assessment.

Delivery

Who does the VB6 work?

Ace8 assessment plus a vetted .NET partner.

  1. 01

    Ace8 does the inventory, plan, test approach and review gates, and the partner does the VB6 and .NET build. The proposal names who does what before you sign.

  2. 02

    AceMQ supports the result 24/7 after go-live; see supported after migration. Mainframe and COBOL work follows the same partner model at mainframe modernization.

Evidence

What have we measured?

Ace8 has no published VB6 project or sample run.

  1. 01

    Results will read Pending until there is one, and this page claims no durations or savings. For the wider picture see legacy application modernization.

Platforms we work with
  • Java
  • Spring Boot
  • Tomcat
  • WebLogic
  • WebSphere
  • JBoss EAP
  • Jakarta EE
  • Kubernetes
  • PostgreSQL
  • OpenRewrite
  • AWS Transform
Partners
  • Broadcom
  • VMware Tanzu
  • Redis
  • OSSeva
Recognition

Broadcom Expert Advantage Tanzu Services Partner of the Year, AMER, 2025 · awarded to the AceMQ engineering team

Proof

Delivered by the AceMQ engineering team.

The engineers behind Ace8 are the AceMQ team, and this is work they delivered. Ace8 is the new name for that practice, not a new team.

Case studyDelivered by the AceMQ engineering team

IBM MQ → RabbitMQ

Phased migration with legacy code refactoring

Legacy messaging replaced in phases while the applications calling it were refactored. No big-bang cutover; each phase reviewed before the next.

American NationalRead the case study
RecognitionBroadcom Expert Advantage Tanzu Services Partner of the Year, AMER, 2025Awarded to the AceMQ engineering team
Since2016Senior engineers working on the platforms enterprises run their business on
After go-liveAceMQ supports the new stack 24/7Supported after migration

FAQ

Frequently asked questions

Short answers to what buyers ask first. Something else on your mind? Ask an engineer.

Partly. Microsoft supports the VB6 runtime for the lifetime of supported Windows versions, limited to serious regressions and critical security issues. The IDE has been unsupported since 8 April 2008.

Start here

Know the cost before anything moves.

A fixed-price assessment gives you the inventory, the risk score and a phased plan. Scope and cost are fixed before the migration starts.

Inventory
Every application, its stack and what it depends on.
Risk score
Where a change is likely to break, ranked.
Phased plan
What moves first, which tools lead, and the fixed price.

Get in touch

Talk to a modernization engineer.

Tell us what you run today. An engineer, not a sales script, replies within one business day.

305-204-2607info@ace8.io

66 W. Flagler St. 9th Floor
Miami, FL 33130

What are you moving off? *

Fixed price. Scope and cost before any migration starts.