Modernizing Legacy Without Inheriting Its Bugs
Migrating a training and competency management back office to a modern React and ASP.NET Core stack, and uncovering 84 dormant bugs along the way.
- Industry
- Training & Compliance Software
- Services
- Enterprise Software Development
84
Dormant legacy bugs found and fixed
<1 sec
To open ~13,000 test questions
0
Bugs reported in the client feedback round
Summary:
A commercial software provider’s training and competency management platform relied on a back-office application built on aging technology. We redesigned and migrated it to a modern stack, preserving business workflows while improving the interface and correcting defects uncovered in the legacy system. AI-assisted testing exposed 84 dormant legacy bugs, and the team corrected all of them in the migrated code.
The Challenge: Aging Technology and Vendor Support Risk
The main driver of this project for our client was to avert risk. Many key versions and components of their system, including the .NET Framework stack, Crystal Reports, NHibernate and dashboard libraries, were facing the loss of vendor support. Our goal was to preserve the business workflows users depend on, improve the interface, and correct the defects uncovered in the legacy system rather than carry them forward.
From Legacy Technology to a Modern Architecture
- Legacy: C# and ASP.NET Web Forms on .NET Framework 4.8, with AjaxControlToolkit, AngularJS/EasyUI, NHibernate and BLToolkit data access, Crystal Reports and Microsoft SQL Server.
- Target: React 19 and TypeScript with an ASP.NET Core 10 REST API, EF Core 10 and SQL Server. PDFsharp/MigraDoc replaces Crystal Reports, and ECharts supports interactive dashboards.
- Deployment: the system runs in production in Linux containers, with SQL Server 2022 retaining compatibility with the restored legacy database.
The Solution: Cleaner Code, Better Interface
The redesign separates the browser interface from backend services, and several decisions make the application easier to change:
- Metadata-driven screens: shared renderers assemble forms, grids, tabs and report parameters, reducing repeated screen code and making changes more consistent.
- Explicit permissions: typed authorization makes access rules clear.
- Modern data access: EF Core replaces the old data-access libraries, while parameterized SQL and selected stored procedures preserve complex workflows and support performance.
The GUI was redesigned to look and feel like a modern, polished business application, with consistent typography, icons, navigation, forms, grids and validation.
- Interactive dashboards: drilldowns, exports and saved user preferences.
- Faster response: query and grid optimization let a list of approximately 13,000 test questions open in under one second in the migration environment.
- Faithful reports: migrated reports reproduced the legacy Crystal Reports output with pixel-level accuracy.
AI-Assisted Three-Layer Differential Testing
We combined three views of each workflow in one verification loop:
- The interface: an AI agent exercised the graphical interface.
- The data: the resulting database changes were compared.
- The code: the corresponding source-code logic was examined.
Cross-checking these layers exposed edge cases in which the legacy application itself behaved incorrectly. This avoided treating every legacy behavior as the expected result, and the process identified 84 dormant legacy bugs, which were corrected in the migrated code.
The Outcome: Migration Performance and Delivery
- Responsive to feedback: one round of client feedback with several additional requested improvements, all implemented, tested, debugged and deployed.
- Quality: the client reported no bugs in the migrated system during that feedback round.
Conclusions
Modernization doesn’t have to mean carrying yesterday’s problems into tomorrow’s technology. By pairing a clean architecture with AI-assisted differential testing, we delivered an application that keeps what works, fixes what never did, and removes the vendor support risk.