Component-Aware VB6 Migration Services
Know every component before you move a single form.
Your VB6 application probably still works. Staff use it every day, and Microsoft still supports the runtime it depends on, even on Windows 11. The trouble sits around it: the development environment has been unsupported since 2008, the ActiveX controls it loads may belong to vendors that no longer exist, and the few people who can change it are close to leaving. Every request for a web screen, an API or a security control costs more than it should.
Most projects that move off Visual Basic 6 go wrong in one of two ways. A converter turns Visual Basic into .NET code that compiles but still reads like the original, or a rewrite begins without a list of what the old system loads and calls, and a control, a DLL or a device link surfaces during cutover week. Both fail for the same reason: nobody found every component first.
Cabot starts with an inventory of every form, class, component and dependency, and an assessment that can end in a plain recommendation to keep the system running for now, with the controls to protect it. When a move to C# and .NET is the right answer, we pin current behavior with tests, move the data, rebuild logic and screens, and run old and new side by side until the outputs match.


























