Migration Toolkit for Runtimes 

The tools, reports, and knowledge that help developers modernize applications to run in the cloud and deploy containers at scale.

The Migration Toolkit for Runtimes product will reach its End of Life by September 30th, 2024. All customers using it should start their transition to Migration Toolkit for Applications, as it is fully backwards compatible with all features and rulesets available in Migration Toolkit for Runtimes and will be maintained in the long term.


Use cases and migration paths

The migration toolkit for runtimes contains a rich set of skill sets (rules and code hints) and supports multiple migration paths and use cases. The toolkit is highly extensible and customizable so you can build on existing skill sets or create your own. 


Application modernization and migration use cases

The migration toolkit for runtimes simplifies the migration and modernization of Java applications by examining application artifacts, including project source directories and application archives. The tool then produces an HTML report highlighting areas needing changes.

We've summarized the most commonly used migration paths in the following table.



Source platform

Migration to JBoss EAP 7 Migration to JBoss EAP 8 JWS 6 OpenShift (cloud readiness)


8, 11, 17, and 21

Jakarta EE 9+  Camel 3 Camel 4 Spring Boot in Red Hat Runtimes Quarkus Open Liberty
Oracle WebLogic Server - - - - - - -
IBM WebSphere Application Server - - -      
JBoss EAP 4 ✘ [1] ✘ [1] - - - - - - -
JBoss EAP 5 - - - - - - -
JBoss EAP 6 - - -       -
JBoss EAP 7 - - -       -
JWS 5 - - - - - -       -
Oracle JDK - - - - - -       -
Camel 2 - - - - - - -
Camel 3 - - - - - - - -
Spring Boot - - - - -  ✔ -
Any Java application - - - - -       -
Any Java EE application - - - - - - - - ✔ [2] -
[1] Although the migration toolkit for runtimes does not currently provide rules for this migration path, Red Hat Consulting can assist with migration from any source platform.
[2] Some rules are included to Quarkify Java EE projects. Additional rulesets to support this migration path are under development and will be included in future Z stream releases.

Other use cases

The migration toolkit for runtimes lets you create your own set of rules and hints to adapt to your own particular needs. One example is new transformation paths. Many developers use the tool for non-migration use cases as part of their build process (via Maven plug-in or command-line interface) in order to validate code on a regular basis against organizational standards or to ensure application portability. 

Another common use case is the enforcement of certain libraries and frameworks (using a single logging framework instead of pick-your own). You can also use the migration toolkit for runtimes to avoid the usage of proprietary libraries.

The rules development guide provides instructions about how to customize existing rules and create new rules and rule sets.

Migration toolkit for applications

If you have a Red Hat OpenShift subscription, we recommend using the migration toolkit for applications. It offers additional capabilities that focus on application portfolio management and collaborating across teams for modernization projects.

Learn more