VB Remake Workshop: New AI-Powered Method Cuts VB6 Conversion Costs by Up to 25% vs. Conventional Services

VB Remake Workshop: Cutting VB6 to VB.NET Conversion Costs by Up to 25% with Generative AI

FDC Inc., a system and software development company (Headquarters: Chiyoda-ku, Tokyo; CEO: Takanori Wada), has introduced a new development methodology leveraging generative AI into its legacy system modernization (conversion) service, 'VB Remake Workshop,' which supports VB6 to VB.NET migration.

As a result, the company has successfully reduced the overall conversion cost—including unit testing—by 20–25% (approximately one-fourth) compared to previous methods, while fully maintaining the existing conversion quality.

Request a Quote Here

Background and Achievements of the Development Methodology Refresh

Currently, many companies face serious challenges with legacy VB6 (Visual Basic 6.0) assets, including end-of-support and system obsolescence (the so-called '2025 cliff' and legacy system issues).

However, the high cost and long duration of conversion have been major barriers.

To address this, 'VB Remake Workshop' has established a new framework integrating cutting-edge generative AI technology into the conversion process and unit testing phases. By combining AI-powered code analysis with quality control by experienced engineers, the service achieves high cost-performance: maintaining quality while significantly reducing costs.

This enables FDC to offer substantially more favorable terms to companies that previously considered migration but were deterred by cost.

Broad Support for Diversifying Conversion Needs

'VB Remake Workshop' offers not only simple conversion to VB.NET but also flexible solutions aligned with corporate IT strategies.

VB6 to C# Conversion

Supports migration involving language changes to C#, considering future scalability and developer availability.

End-to-End Integration Testing

Beyond unit testing, the service can take full responsibility for integration testing to verify system-wide interoperability.

Phased Migration Planning

To minimize business impact and budget constraints, we propose optimal roadmaps with phase-by-phase migration by functionality.

Further Cost Reduction via Offshore Utilization

By combining overseas development centers under Japan-based quality management, we achieve even lower costs and faster delivery.

Learn More Here

Future Outlook

Going forward, the company will continue to actively adopt cutting-edge technologies such as generative AI to strongly support customers in advancing DX (Digital Transformation) and escaping legacy systems.

We have already begun accepting individual consultations and quotes. We encourage those facing challenges such as 'our previous quote exceeded the budget' or 'we're unsure of the optimal migration path' to contact us now.

Risks of Continuing to Use Legacy Systems Built on VB6 (Visual Basic 6.0)

Risks in the Development Environment

Microsoft has already ended extended support for VB6 (Visual Basic 6.0), and Windows XP support has also ended. This makes system troubleshooting, specification changes, and feature additions difficult, posing security risks. Additionally, as skilled developers become scarce, ongoing maintenance becomes challenging and costly.

Furthermore, various third-party tools previously provided for VB6 development have also ended support.

Risks in the Execution Environment

While Microsoft currently supports VB6 runtime on Windows 7 through 10, the duration of this support is uncertain, posing execution risks.

Other risks include applications failing after security patches, stricter user permissions blocking file access, and ActiveX controls not being guaranteed to work on Windows 7 and later—all of which may prevent systems from running.

▼ Reference: [Simple Explanation] Converting (Migrating) from VB6 to VB.NET

https://www.fdc-inc.co.jp/vbremake/blog/vb-net_conversion/

General Process of Converting (Migrating) from VB6 (Visual Basic 6.0) to VB.NET

Due to significant changes in language specifications, migrating to VB.NET is complex and requires full development phases: new requirements definition, design, development, testing, and deployment preparation.

Simply rebuilding the same system without leveraging existing assets results in excessive time and cost. Additionally, naive webification may compromise the system's user-friendly interface.

Process of Rebuilding from VB6 (Visual Basic 6.0) to VB.NET

Rebuilding from VB6 to VB.NET typically involves 12 development steps.

[VB Remake Workshop] Process of New Development

Process of Converting from VB6 (Visual Basic 6.0) to VB.NET

Converting from VB6 to VB.NET typically involves 7 key steps.

[VB Remake Workshop] 7 Steps of Conversion

Reference: [Simple Explanation] Converting (Migrating) from VB6 to VB.NET

https://www.fdc-inc.co.jp/vbremake/blog/vb-net_conversion/

Converting (Migrating) from VB6 (Visual Basic 6.0) to VB.NET

Enterprises using legacy systems built on VB6 (Visual Basic 6.0) should note that Microsoft ended support on April 8, 2008, and Windows XP support ended on April 19, 2014.

Due to risks in both execution and development environments, many organizations struggle with whether to rebuild or continue using VB6.

We offer short-term, low-cost migration of VB6 assets and legacy systems affected by the end of Windows XP support to VB.NET—please feel free to consult us.