By Preetham Michael, Client Partner


Let’s start at the beginning – application cloud migration is the process of moving one software application from one cloud computing environment to another. This might sound straightforward, but it’s important to note that different application types may require different paths to the cloud.

Since the early days of cloud computing, developers have referred to these program migration trends as “R” patterns: Rehost, Refactor, Replatform, and Replace.

Rehosting is what transfers servers or software from their current hosting environment to a public cloud infrastructure. For organizations just beginning their migration journey, rehosting and lift and shift are standard strategies.

Each application has its own design. So, it cannot be expected for every application to work efficiently in every cloud environment. Hence, applications may require a complete rearchitecture to better suit their new cloud environments.

Very similar to the above to R’s, replatforming moves applications within the cloud without making any major changes within the application.

When an application is no longer required in a cloud environment it is shifted to a different one where it can serve its purpose after making the required changes to suit its new environment.

As easy and interesting as application cloud migration seems, these 4 R’s do have their risks, including:

  • Technical challenges – Refactoring or replatforming an application with too many dependencies can be much more difficult and time consuming than originally expected.
  • Unforeseen costs – Businesses may incur costs not budgeted for if they don’t prepare ahead. Costs may include licensing fees or training costs for tool education.
  • Unprecedented downtime – Major application changes may trigger conflicts or problems that result in unplanned downtime for the application as well as connected or dependent systems.

Taking control of the 4 R’s is key to a successful application cloud migration. There are a handful of areas that, when managed with foresight, can drive value and success for a migration.

  • Determine the total cost of ownership for rehosting, refactoring, replatforming, and replacing – buying, running, and maintaining on-premises hardware and software licensing.
  • Build a project roadmap that accounts for successes and possible stumbling blocks you may face.
  • Review legacy applications prior to migrating to ensure efficient performance in the new environment.

The path you choose to the cloud can be entirely different from Company B or Company C – what’s important is the way you manage the process to get there and balance the risks along the way.

What application cloud migration path should your company take? Let Paradigm Technology help you find the best fitting “R” for your journey!