- Migration Pattern
- Delphi to Java migration
migration-pattern
Migration Pattern
Why move from Delphi to Java?
Delphi will eventually be migrated to new technologies.
Modernizing your Delphi system early, while your internal team still retains much of the legacy system knowledge, can better support your migration and lead to lower migration costs.
Operational and modification expenses will also be reduced after migration.
Features of Our Conversion Service
Our proprietary rule-based AI tool can understand Delphi system items accurately, and create pure-Java system comparable to those built by human programmers, with the highest quality and the lowest cost, proven in many past projects.
Features of AppModernizer’s Automatic Conversion
Achieves extremely high quality, low cost, and high maintainability, while also enabling integration with other Java platforms.
Testing for Superior Quality with Fewer Man-Hours
Instead of solely on customer-provided test data for quality assurance, we conduct test of all technical points and critical business processes to rigorously ensure quality and reduce test cost.
Extremely 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 almost 100% automatically, 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.
Samples of AI-powered Language Conversion
①Change program structure from Delphi to Java
②Generating pure Java code
Modernizing to pure Java and the latest Java technology standards is important for maintenance and improvement.
UI migration
Change the Delphi screen to a standard HTML5-based web screen
Migration Cases
Insurance management system
- Development process
- Inventory, migration design, UI design − migration test, system test & user acceptance test support, Go-Live support
- Migration information
- Delphi 10.1 to Java11
VB.NET2015 to Java11
QuickReport to SVF 9.2
Excel2010 to Excel2019
SQL Server 2012 to PostgreSQL 10.14
Windows Server 2012 to RedHat Enterprise Linux7.4
Adopting Apache Tomcat 8.5
Adopting SpringMVC
.NET Framework to SpringMVC
Keeping Windows 10 - Current system scale
- Delphi:276.7KL, VB.NET:47.3KL
- Development period
- 12 months
Production management system
- Development process
- Inventory, migration design, UI design − migration test, system test & user acceptance test support, Go-Live support
- Migration information
- Delphi 10.1 to Java1.8
Delphi screen to HTML5+Thymeleaf
Report (Quick Report) to SVF 9.2
Adopting Spring MVC
Adopting Edge
SQL Server 2012 to SQL Server 2016 - Current system scale
- Delphi:295KL, Report:100
- Development period
- 12 months
Reservation management system
- Development process
- Inventory, migration design, UI design − migration test, system test & user acceptance test support
- Migration information
- Delphi 7 to Java1.8
Delphi screen to BootstrapFramework
Adopting Spring MVC
Adopting Google Chrome/Edge
SQL Server 2008 to PostgreSQL 10.14 - Current system scale
- Delphi:245KL
- Development period
- 11 months
Sales management system
- Development process
- Inventory, migration design, UI design − migration test, system test & user acceptance test support, Go-Live support
- Migration information
- Delphi 10.3 to Open JDK8
Delphi screen to HTML5+Thymeleaf
Report (Quick Report) to SVF 9.2Framework
Adopting Spring MVC
Adopting to Edge
Oracle 11gR2 to PostgreSQL 13 - Current system scale
- Delphi:192KL. Report:23
- Development period
- 10 months