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.
Most VB6 risk hides in COM components, ActiveX controls and data access. We list them first, then plan the move to .NET.
frmClaim.frmremovedmodData.basremovedClaimForm.cs+112−0ClaimRepository.cs+47−0Stacks we work in
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
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.
| Item | Microsoft's position |
|---|---|
| VB6 IDE | Not supported since 8 April 2008; no supported way to create or maintain VB6 apps |
| VB6 runtime files in Windows | Supported for the support lifetime of the Windows version; limited to serious regressions and critical security issues |
| 64-bit Windows | Runtime is 32-bit only; apps are supported only under the WOW emulation environment |
| Third-party OCX and ActiveX controls | Not supported by Microsoft; contact the control vendor |
| Some listed runtime files | Microsoft lists several files as unsupported, so a component may fall outside the support bar |
Inventory
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.
Registered DLLs and OCX files, their vendors and whether a .NET version exists.
DAO, RDO and ADO usage, ODBC drivers, Jet or Access files, stored procedures.
Screens, grids, report writers and printing.
Win32 API calls, file and registry use, and anything that touches hardware.
Installers, shared runtime files and the Windows versions in use.
Options
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.
Automated conversion to VB.NET gets running code quickly but leaves VB6 idioms in the result.
A staged rewrite to C# on current .NET suits applications that must change a lot.
Leaving it on a supported Windows version is a short-term choice, limited by the support terms above.
How it runs
Ace8 scopes and delivers the move. AceMQ engineers support the new stack 24/7 from day one.
Scope, cost and AI readiness, before any migration starts. Characterization tests and a baseline before we touch a line.
AI-assisted, engineer-verified, one capability at a time. Tools draft the rewrite and a senior engineer signs every change.
Tested, reversible cutover. AceMQ engineers support the new stack from day one. Supported after migration →
Method
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.
Inventory the code and score each application. This is the fixed-price assessment.
Capture cases for calculations, reports and data writes.
Move one module or application at a time, with engineer review of every change.
Compare old and new on the same data before cutover.
Delivery
Ace8 assessment plus a vetted .NET partner.
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.
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
Ace8 has no published VB6 project or sample run.
Results will read Pending until there is one, and this page claims no durations or savings. For the wider picture see legacy application modernization.
Broadcom Expert Advantage Tanzu Services Partner of the Year, AMER, 2025 · awarded to the AceMQ engineering team
Proof
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.
IBM MQ → RabbitMQ
Legacy messaging replaced in phases while the applications calling it were refactored. No big-bang cutover; each phase reviewed before the next.
FAQ
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.
Microsoft's statement lists the VB6 runtime as supported on Windows 11, as 32-bit under WOW. Third-party controls are outside that support, so test your own application.
Tools can convert much of the code. Forms, COM components, data access and third-party controls usually need engineers and tests.
No. Ace8 does the assessment and plan and a vetted .NET partner delivers. The proposal names who does what.
Start here
A fixed-price assessment gives you the inventory, the risk score and a phased plan. Scope and cost are fixed before the migration starts.
Get in touch
Tell us what you run today. An engineer, not a sales script, replies within one business day.