- Migration Pattern
- RPG/CL to Java migration
migration-pattern
Migration Pattern
Success Stories
With the only one 100% automated AI-powered conversion and testing technology for modernization, we deliver a genuine open system with exceptional quality and low cost.
Several clients presented case studies at large IT events.

AppModernizer for BB sales management system
in JUAS Square
AS400 Modernization
RPG/CL to Java
DB2 to SQL Server

The IT department takes an aggressive stance to avoid business risks! Breaking away from legacy systems through AppModernizer
in BSIA Symposium
AS400 Modernization
RPG/CL to Java
DB2 to PostgreSQL
Performance Improvement

Launching a distribution system that cannot be offline for even short periods in a highly challenging project environment
in Gartner IT Symposium/Xpo
AS400 Modernization
RPG/CL to Java
DB2 to Oracle
Challenges of Holding on to IBM i (AS/400) and RPG
AS400/RPG will eventually be replaced by modern technologies. Clinging to an outdated legacy is frustrating and inefficient.
Let’s migrate and enjoy the benefits of new technology sooner.
Common Problems in Migrating from RPG to Java
Most migration companies use straight conversion
Maintainability issues
The legacy language is simply replaced with custom functions, inheriting the elements of the legacy system as-is.
As a result, managing the system requires a deep understanding of both legacy and open technologies.
Since it is not standard Java, generative AI tools cannot create or modify source code correctly.
Performance issues
With straight conversion, the existing processing method remains unchanged, leading to frequent performance issues.
Operational quality issues
Comparison testing is conducted with customer-provided test data only, effectively leaving quality assurance to the
customer.
Features of AppModernizer’s Automatic Conversion
Deliver reliable system migrations with exceptional quality and cost efficiency.
Automated Testing Tools Covering All Migration Technical Points
While most migration companies rely on customer-provided test data for quality assurance, we use the only one Al-powvered migration technology to test all the migration technical points to enssure quality with shorter testing time.
Comparison Test through Reproducing Actual Processing
Reliable quality is achieved after data from many business days has been tested. We complete our tests only when data from 3 consecutive business days has been processed without any bugs.
With our testing, you can have peace of mind without having to worry about complex system tests yourself.
Examples of Migrated Source Code
UI Migration
Features of migrated GUI
・Improved operability with mouse and buttons.
・Customizable according to customer UI standards.
・Response speed similar to that of web systems.
AS400 Migration Performance Issues
In RPG, database data can be accessed directly.
In Java, access is through a database interface, which can lead to performance issues if the volume of database queries is high.
Straight conversion struggles to solve this problem. It is recommended to use AI to understand the functionality and generate correct Java code.
Production Data Migration
If there are errors in data migration, business operation issues may arise.
Key implementation items
Over- or under-inclusion
All the data and operation patterns are rigorously checked by SoftRoad’s proprietary tool.
Data migration accuracy
We use the data migration tool to transform data across all test cases and validate the results through comparison.
Especially with the comprehensive testing, which spans a vast volume of data, we ensure the accuracy of structural changes, format conversions, etc.
Key tasks in data migration
Data migration was carried out in most of 850+ system migrations we have completed. All cases are successful.
Implement Specification Changes During Migration
Prolonged system freezes during migration can be avoided using our catch-up solution.
AppModernizer can achieve almost 100% automated conversion. If customer provides the latest source code after each update, we can incorporate the changes by quickly converting them into target language.
Migration cases
Wholesale core system
- Development process
- Inventory & slimming, migration design, UI design – system test, user acceptance test support
- Migration information
- RPG to Java
CLP to Java/Shell
DB2 for i to Enterprise Postgres SE 14
IBM i V7R4 to Red Hat Enterprise Linux 8.4 - Current system scale
- RPG:443KL
CLP:91.6KL - Added new functions scale
- Java:110KL
- Development period
- 21 months
Order, sales, and inventory management core system
- Development process
- Inventory & slimming, migration design – migration test
- Migration information
- COBOL, RPG, RPGLE to Java
CLP, CLLE to Java/Shell
C to Java/C
DB2 for i to SQL Server 2019
IBM i V7R3 to Red Hat Enterprise Linux 8.4 - Current system scale
- RPG, RPGLE:685.3KL
CLP, CLLE:269.0KL
COBOL:2,834.8KL
C:4.8KL - Development period
- 22 months
Logistics management system
- Development process
- Inventory & slimming, migration design – migration test, system test & user acceptance test support
- Migration information
- RPG, RPGLE to Java
CLP, CLLE to Java/Shell
DB2 for i to SQL Server 2019
IBM i V7R2 to WindowsServer2022 Standard Edition - Current system scale
- RPG:614.1KL
CLP:6.3KL - Development period
- 15 months
Inter-company information sharing system
- Development process
- Inventory & slimming, migration design – migration test, system test & user acceptance test support
- Migration information
- RPG to Java
CLP to Java/Shell
DB2 for i to SQL Server 2019
IBM i V7R3 to WindowsServer2022 Standard Edition - Current system scale
- RPG:1,943KL
CLP:30.2KL - Development period
- 18 months
Sales management system
- Development process
- Inventory, migration design, specification documentation, source code migration – system test, user acceptance test support, Go-Live
- Migration information
- RPG to Java
CLP to Java & PowerShell
DB2 to Oracle19c
IBM i V7R1 to WindowsServer2016 - Current system scale
- RPG:110KL
- Development period
- 11 months