A Guidepost for a Collaborative Modernization Approach


Understand your short and long term cloud goals,

and formulate a strategy to achieve them


The drivers for moving workloads to the cloud are well documented: Organizations need to simplify operations, reduce costs, and increase application agility to meet market demands. Additional motivations for moving workloads to the cloud include balancing the need to meet regulatory compliance requirements with the desire to greatly increase innovation, performance, and scalability.

But the critical question for organizations to first answer is: What are the specific cloud destination options, and what is the recommended approach to get there? To be effective, organizations need a strategy that fully maximizes cloud benefits, including, but not limited to, leveraging a cloud-native landscape.

How we can helpResourcesGet in touch

Discussing the 2022 Mainframe Modernization Report

60 minutes

Watch on demand


Short and Long-Term Destination Options


The selected cloud destination will ultimately depend on the customer’s desired short and long-term goals.

Advanced has the unique ability and experience to migrate legacy workloads to any cloud destination: cloud ready, cloud optimized, or cloud native. The below graphic provides an overview of the three different cloud destination options:

J2C disposition graphic US.png

Disposition Strategies Mapped to Cloud Destinations


Journey to Cloud map graphic US.png

The starting point of any modernization journey should be a comprehensive assessment – encompassing applications, operations, and the supporting infrastructure. Assessment results should look to validate any pre-selected disposition strategies (sometimes referred to as modernization patterns), and ultimately assist in defining the overall modernization approach. Depending on the long term goals – the approach often includes a combination of disposition strategies. For example, a long term goal of re-engineering a large, complex mainframe monolith into cloud-native microservices can be broken into several incremental steps:

  • Refactor applications to a cloud-native language such as Java or C# and run containerized in a cloud ready environment.
  • Optimize applications to obtain desired level of elasticity at the container level, running in a cloud optimized environment. In parallel, re-engineer specific functionality identified during the assessment phase with Java-based microservices.
  • Continue to optimize the application, incrementally re-engineering to microservices and progressing towards a cloud native environment, realizing that it may not be necessary to replace the entire monolith in the short or long term. It’s important for each application to be analyzed critically via an in-depth assessment in order to understand the reality that parts of the monolith might be better served remaining intact.

Disposition Strategies - An Overview


Additional resources to help you modernize



Modernization secrets of the Fortune 1000

This paper highlights the drivers to modernize, and profiles three global businesses who leveraged Advanced solutions for success.

Read guide





The New York Times: COBOL to Java

Advanced's Automated Refactoring solution enabled The New York Times to completely migrate their core IT system to an AWS platform.

Read case study





2022 Mainframe Modernization Report

Exploring the impact of the new era of digitalization and change on the current state of legacy systems and organizations' modernization plans.

Read report



Read blog angle-right-solid.svg

Oct 21, 2022 by Tim Jones, Managing Director of Application Modernization, Advanced

Read blog angle-right-solid.svg

Jun 10, 2021 by Rob Anderson, Vice President of Marketing and Product, Advanced

Read blog angle-right-solid.svg

Sep 22, 2021 by Rob Anderson, Vice President of Marketing and Product, Advanced