The path you choose to a cloud migration will provide a roadmap. There is no one best choice that can be applied to every situation, because you need to have a granular understanding of the specific application to know which approach is most appropriate.

Consider the various cloud migration options:

Rehost: This is often referred to as a lift-and-shift migration, because it basically takes an on-site application and puts it in the cloud, without any code modification. It utilizes automation to make migration quicker and to conserve resources.

Reinstall: Similar in some ways to re-hosting, a reinstallation uses new virtual machines that are created in the cloud. Software is then installed from scratch, but with no configuration changes. While slightly more complex than re-hosting, it does allow for cleanup during migration, and your enterprise can avoid copying certain software unnecessarily.

Re-platforming: This option moves an application to the cloud with a bit of up-versioning. This might be using a managed database or adding automation for the purpose of auto-scaling. One of the hallmarks of re-platforming is the use of containers and virtual machines. Code is only altered when necessary for certain base platform services. It also allows workloads to access cost optimization without the complexity of re-factoring.

Re-factoring: This takes advantage of cloud-native frameworks or functions by using advanced re-architecting and some re-coding of parts of the application. It often involves changing middleware and certain components in order to capture advanced concepts, such as microservices.

There are certain instances in which none of these options are appropriate, because as you consider an application for cloud migration, you realize that it has little business value or because it has met your criteria for end-of-life applications.

Taking a self-assessment of your migration path: You’ll need to take time to examine the feasibility and cost-benefit analysis for each of your applications. Consider the following questions, among others:

• How critical is the application to your business? Is it critical for revenue generation, or does it simply sustain operations and should be migrated and sustained at the lowest total cost of ownership possible?
• If it’s a sustain application, consider whether it can be rehosted in the cloud. If not, there may be a Software as a Service (SaaS) application that performs the same functions.
• Capture the total cost. Whether it’s a sustain application or one that generates revenue, be sure to include any business development costs and the cost of business interruptions during cloud migration.

Cloud migration requires the right approach from the very beginning. At eXemplify, we assist enterprises just like yours in determining the best option for each application, considering the full cost and other factors in the analysis. Contact us for more information.