Major organizations are focusing significant resources to moving their applications to the cloud. A clear majority of them are running their critical systems using legacy applications and potentially legacy infrastructure.
There are 3 critical areas that need to be considered when planning for a modernization project:

  1. Infrastructure
  2. Process
  3. Application

The one thing that is critical is that it is a serious mistake to plan on a “big bang” approach. It is essential that when planning migration it should be tackled in small manageable projects.

Selecting applications for modernization

The first step is identifying which applications are the best opportunities for modernization.
The approach EvolveWare follows when carrying out a project is:

  1. Identify all the applications that are potential candidates for modernization
  2. Determine the business priorities for migration
  3. Finalize the sequence of migration

Identify Applications

Once a list of applications has been created there are 2 things that need to be done:

  1. It is essential to make sure that all the components of the application are available – that is all the code, copybooks, JCL, database, stored procedures etc.
  2. Once there is a complete inventory then the documentation for the code set needs to be produced.
  3. Experience tells us that it is highly unlikely that adequate documentation for legacy applications already exists – so it needs to be created.

    Determine Business Priorities

    This should already have been done by business management. Part of the overall business plan should be an indication of which processes are most important to move to the cloud or just to modernize.
    If this has not been done, then it is an exercise that needs to be carried out with business managers to determine how to best meet business goals.

    Finalize the sequence for migration

    The planners now know the required business sequence for migration and they also have available all the documentation from the legacy applications. Now, they can map the support provided by legacy applications to the priority business process and determine a sequence for migration.

    There are other areas that need to be considered before the plan can be finalized and we will look at those in the next post.