
- Migration Pattern
- ASP Migration Service
migration-pattern
Migration Pattern
ASP Migration Service
Legacy ASP systems face numerous challenges, including an outdated technology stack, a shrinking talent pool, end of support for ASP and ASP-dependent components, etc. Failures or delays in modernization can lead to system outages, compliance risks, and loss of competitive advantage.
SoftRoad has helped many customers migrate legacy ASP systems to modern technologies such as ASP.NET, Java, and also supported .NET framework upgrades. Using our proprietary AI-assisted conversion technology, supported by structured analysis, validation, and engineering review, we migrate legacy ASP code and data to pure ASP.NET or Java systems that fully comply with industry standards. The resulting systems are rigorously tested for superior quality, highly maintainable, and generative AI–ready for future maintenance and enhancement.
Success Stories
With our unparalleled AI-assisted modernization technology, supported by structured analysis, validation, and engineering review, we help our clients with their ASP modernization initiatives, delivering a standard compliant open system with high quality and low costs, which sets us apart from the competition.
A number of our clients presented their migration projects as case studies jointly with SoftRoad at major IT events in Japan. Cover pages shown below are from slides for those speaking sessions.
Case studies reference specific modernization projects delivered across different timeframes and regions. Brand names are used for illustrative purposes only and do not imply endorsement or ongoing commercial relationships.
Kao’s system renewal with AppModernizer
at JUAS Square
VB to VB.NET
ASP to ASP.NET
VB.NET upgrade
ASP.NET upgrade
Oracle to SQL Server
Initiatives to improve growth potential of core functions of the Kirin Group system with award-winning AppModernizer
at Nikkei BP IT Modernization Summit
VB to VB.NET
ASP.NET upgrade
SQL Server upgrade
Oracle upgrade
Legacy system renewal achieved through AppModernizer
at Nikkei BP IT Modernization Summit
COBOL/S to Java
COBOL to MF COBOL
JCL to Kshell
RDB, VSAS to PostgreSQL
VB to VB.NET
Java upgrade
ASP to ASP.NET
Inevitable Classic ASP System Migration
Continuing to use the classic ASP system will lead to various problems.

Common Problems in ASP Migration
Lack of expertise · Problematic migrations are common
Similar to new developments, post-migration testing of business functions requires significant time, and testing omissions are common. It often ends up with leaving final verification to customers.
Dedicated tools, appropriate development process and specialized expertise are indispensable for ASP migration.
Features of AppModernizer’s Automated Conversion

AppModernizer converts legacy ASP systems to the latest mainstream technologies and also provides the following advantages in the new system.
☛ Achieve very high automated conversion rate in migration to ASP.NET (including framework migration).
☛ Automatic conversion of all types of ActiveX.
☛ DB change.
☛ Common improvements such as expanding the number ofdigits for item IDs, etc.
AppModernizer ensures remarkably high quality, low costs, and high maintainability, while enabling integration with other Java platforms.
Sample Source Code of ASP Migration
Generate standard ASP.NET code with MVC structure

Separate the mixed Classic ASP source code into front-end/back-end based on the MVC structure.
Change from ADODB to DataTable

AppModernizer Testing Features

Comparison test on critical business functions to ensure reliable quality.

By covering all technical points, our unique testing technology ensures exceptional quality, singificantly reduced costs and man-hours.
Remarkably High Quality and Low Cost Compared to Rewriting

※¹ This is mainly a fine-tuning of the screen and report UI, and does not affect business logic.
※² JUAS (Japan Users Association of Information Systems) states that the industry-standard post-release bug rate is 0.084 to 0.1 per thousand lines of code (KL).
※³ Since business logic processing can be converted with automation, the number of defects in the business logic portion is extremely low. Minor issues such as display position issues may occur, but this will not affect the use of the system.
Migration Options

We will propose the best migration plan based on the characteristics of your existing system, your budget, and characteristics of operation management.
Migration Cases
Business travel management system
- Development process
- Inventory, migration design, specification re-creation − migration test, system test & user acceptance test support
- Migration information
- VB6.0, Delphi4, COBOL to VB.NET
C++ 6.0 to Visual C++ 2005
ASP to ASP.NET
C.O. Reports Ver.7/Ver.8 to C.O. Reports Ver.9
QuickPak Professional V4.0J to InputMan for Windows Forms 6.0J
True DBGrid Pro 6.0J/7.0 to ComponentOne Studio for Windows Forms 2010J
BASP21 to BASP21 Pro
Windows2000/XP to Windows7
Windows Server95/98/NT/2000 to Windows Server 2008 - Current system scale
- VB: 118.8KL, ASP: 44.1KL, Delphi: 10.2KL, COBOL: 2.5KL, C++: 7.1KL, Reports: 46
- Development period
- 11 months
Infrastructure system
- Development process
- Inventory, migration design, source migration − migration test, system test & user acceptance test support
- Migration information
- ASP to ASP.NET 2012(MVC)
VBS to VB.NET 2012
SQL Server 2008 to SQL Server 2012
Windows Server 2003 to Windows Server 2012 - Current system scale
- ASP: 414KL, VBS: 41KL
- Development period
- 10 months
Quality management system
- Development process
- Inventory, migration design, source migration − migration test, system test & user acceptance test support
- Migration information
- ASP to ASP.NET 2013
Keeping Oracle11g
IE8 to IE11
Windows Server 2003 to Windows Server 2012 - Current system scale
- ASP: 389.4KL, VBS:1.1KL
- Development period
- 9 months
Product management system
- Development process
- Inventory, migration design, source migration − migration test, user acceptance test support
- Migration information
- ASP to ASP.NET 2012(MVC)
VB to C#
Oracle11g to Oracle12c
IE8 to IE11
Windows Server 2003 to Windows Server 2012 - Current system scale
- ASP: 298.8KL, VB:23.8KL
- Development period
- 8 months
Transportation management system
- Development process
- Inventory, migration design, source migration − migration test, system test & user acceptance test support
- Migration information
- ASP to ASP.NET2010
VBS to VB.NET2010
SQL Server 2005 to SQL Server 2008
Windows Server 2003 to Windows Server 2008 - Current system scale
- ASP:245.1KL
- Development period
- 8 months
Catalog management system
- Development process
- Inventory, migration design, source migration − migration test, user acceptance test support, go-live
- Migration information
- ASP to ASP.NET MVC(VB.NET2019)
Keeping VBS
T-SQL to PL/pgSQL
SQL Server 2008 to PostgreSQL 13
Edge to Chromium Edge
Excel2013 to NPOI
Keeping IIS 10.0
Keeping Windows 10 - Current system scale
- ASP: 107.1KL, VBS: 3.7KL, T-SQL: 12.7KL
- Development period
- 8 months
Document management system
- Development process
- Inventory, migration design, specification re-creation, source migration − system test, user acceptance test support
- Migration information
- ASP to ASP.NET2019
ASP.NET(C#.NET 2005) to ASP.NET(C#.NET 2019)
.NET Framework 2.0 to .NET Core 3.1
Keeping SQL Server 2016
IE11 to Edge, Chrome
Keeping BASP21Pro
ActiveReports for .NET 6.0J to ActiveReports for .NET 14.0J Professional
Keeping Windows Server 2016
Keeping Windows 10 - Current system scale
- ASP: 77.3KL, ASP.NET: 8.1KL, DTSX: 9.6KL
- Development period
- 6 months



