At last there's a cost-effective, rapid method to migrate your applications from Windows XP (VB, PowerBuilder, et al) to Windows 7, 8, and 10.

Mobilize.Net migration technology gets your application 95% of the way to a finished VB.NET or C# code base running on Windows 7/8/10 at a fraction of the cost of a manual rewrite.

The technology relies on the same advanced migration engine of the Visual Basic Upgrade Companion--Microsoft's preferred route for migrating VB code to .NET. VBUC has been used to migrate over a billion lines of VB code.

Windows XP is at end of life

Microsoft has stopped all support for Windows XP on April 8, 2014. After that date no more patches or updates. Security vulnerabilities and new-found bugs won't be addressed. No device driver updates will be available; no new hardware certifications.

Windows XP applications (Win32/.NET 1.1) can be run on Windows 7+ in compatibility mode, but this also has known vulnerabilities.

The only safe solution is migrating your applications to .NET 3.5 or later for Windows 7 / 8 /10 deployment.

Migrate Faster, Lower Cost

  • Customizations for your specific project reduce code cleanup and manual replacement steps
  • On-site migration engineers ensure you get maximum productivity by learning best practices in code modernization, developed over two decades performing thousands of similar migrations.
  • 24x7x365 support ensures you have expert help when you need it.

Why choose Mobilize.Net?

  • Faster: Four times faster to deploy than a rewrite
  • Cheaper: Up to 95% less expensive compared to a manual rewrite
  • Lowest risk: Guaranteed success with fixed price and schedule
  • Increased developer productivity
  • Preserves years of IP investment
  • 100% native code without third-party runtimes
  • Break away from old platform constraints

laptop.png

Here's what you get:

  1. All source code converted to the target .NET language (VB.NET or C#).
  2. The migrated source code will compile without errors but the code may still have runtime execution issues.
  3. All application screens will render correctly in the Visual Studio designer and will be visually equivalent to their VB6 counterparts. A workaround will be arranged for any areas where visual equivalence cannot be attained.
  4. The application main form will run and all initial values are equal to the original VB6 application. Additionally, all forms that can be reached directly from the main menu will be revised to ensure they display properly and have the same initial values as the VB6 application. The objective is to verify that the main form and all associated forms are properly displayed in the new .NET application.
  5. On-site migration engineer to migrate and deliver the code and train the customer on the final phase of the process.

Let us help you move to .NET

Talk to an Engineer