Financial Services
VB6 to .NET 8: Migrating a 400,000-Line Core Banking Platform
The Challenge
A major U.S. financial services firm was running a core transaction processing platform built entirely in Visual Basic 6 — 400,000+ lines across 340 .vbp projects. The system had not received a meaningful architectural update in 14 years. 34 third-party dependencies contained known CVEs. The team of developers who originally built it had largely retired, and institutional knowledge was concentrated in two remaining engineers approaching retirement.
The security and compliance implications were severe: the platform processed millions of transactions daily on a codebase that had been out of active support for over a decade. A single developer departure could create an unmaintainable system with no clear path to recovery.
Our Approach
We deployed the Smart AI Modernization Analyzer to produce a full Technical Report in 6 minutes. The report surfaced all 34 CVE-flagged dependencies, identified 12 modules responsible for 70% of the codebase complexity, and generated a Business Risk Report that leadership used to secure the modernization budget in a single board presentation.
Execution used AI-assisted code transformation for repetitive VB6 form patterns (converting COM event models to C# event handlers at scale), AI-generated documentation for undocumented business logic identified through static analysis, and a parallel-run testing strategy to validate transaction parity before each incremental cutover. The nearshore team provided same-timezone communication throughout.
The Outcome
- Migrated 400,000 lines of VB6 to .NET 8 in 18 months
- Eliminated all 34 CVE-flagged dependencies
- Reduced annual maintenance cost by 55%
- Zero production downtime during migration (parallel-run cutover strategy)
- System now integrated with cloud APIs and modern authentication that were impossible on VB6
- Developer onboarding time reduced from 6 months to 6 weeks on the new platform
Healthcare
ASP.NET Web Forms Modernization: 180 Pages to ASP.NET Core
The Challenge
A regional healthcare organization's patient management system was built on ASP.NET Web Forms with .NET Framework 3.5. The system handled scheduling, billing, and clinical documentation across 180 .aspx pages and 47 .ascx user controls. ASP.NET Web Forms end-of-life meant no new security patches, and the system had failed a recent HIPAA compliance audit due to outdated TLS implementations in its NuGet dependencies — specifically TLS 1.0 calls found in six dependencies.
The organization faced regulatory pressure to remediate before the next audit cycle. Manual assessment of the codebase would have taken a compliance consultant four to six weeks to complete. The existing development team did not have capacity to audit hundreds of files while also maintaining the production system.
Our Approach
The Smart AI Modernization Analyzer inventoried all 180 .aspx pages, 47 user controls, 23 NuGet packages, and all code-behind files in 4 minutes. The Technical Report identified 8 CVE-flagged NuGet packages and the specific file and line locations of all deprecated TLS 1.0 calls — producing in minutes the audit that would have taken weeks manually. This report was used directly in the compliance remediation conversation with the auditor before a single line of code was changed.
The migration path chosen was ASP.NET Core Razor Pages, preserving all business logic while eliminating the Web Forms dependency entirely. AI-generated documentation captured the business rules embedded in complex code-behind files before migration began.
The Outcome
- All 180 Web Forms pages migrated to ASP.NET Core Razor Pages
- Passed follow-up HIPAA compliance audit with no findings
- Page load time reduced by 60% on the modern .NET runtime
- All 8 CVE-flagged NuGet dependencies eliminated
- Migration completed in 9 months with no disruption to clinical operations
- Platform now eligible for Azure cloud deployment (Web Forms could not run on Linux containers)