This is the next installment in a series of blogs on the subject of cloud transformation. We decided to call out this specific cloud lift-and-shift migration strategy because of our clients’ experience with this strategy. Many of our clients have seen both negative and positive results from this strategy, however, all of them missed many of the items we have called out below. As a result of missing some of these items, expectations by leadership and others within the organization have been skewed too far in both optimistic and negative ways. It is fully recognized there are at least four other strategies for cloud migration: refactor, revise, rebuild, and replace.
The IT Leader's Guide to Multicloud Readiness
This guide provides practical key insights and important factors to consider to make informed decisions in your multicloud journey.
Lift and shift refers to an application migration (rehost) strategy for movement to a cloud-based environment. Normally, this approach implies little-to-no change in the application and data architecture. Speed and cost are usually the focus when choosing this strategy.
Things to Consider
- This strategy (like most migration strategies) still requires some planning upfront. Successfully running this application on traditional hardware servers or on-premises VMs doesn’t mean it will run correctly in the cloud.
- Be sure to do a deep dive on all connections in and out of the application and data.
- What is the expected life of this application and data? If the life span is shorter than 12 months, it might not be worth moving it to the cloud.
- Give careful consideration to the number and types of access required for this application and data. You need to conduct additional analysis to determine how to provide access to other APIs and/or data that’s not included in the code and/or data being moved.
- Many cloud hosting providers will have automated tools for migrating these kind of standalone applications and data. Examine the tools provided by your cloud hosting provider to determine the capability for your specific situation. These tools are often a quick way to run a “test” migration and work out the architectural kinks in the cloud.
- If you have more than one application that falls into a “lift-and-shift” category for migrating to the cloud, then it might make sense to write a runbook to automate multiple migrations in a batch-type operation.
- This type of migration strategy can be just a “first step” for a broader strategy. Many organizations will have multiple smaller applications and data that should be combined and refactored for native-cloud capabilities. It is often easier to perform the “refactoring” in the cloud when all the applications and data are already sitting in the same cloud location.
- You still need to test once migration has occurred despite this strategy being simpler and faster. Make sure your current test suite can be executed against the application once it is in the cloud environment.
- All of the current application, data compliance, and regulatory requirements will remain the same once it is in the cloud environment. You should check all of these boxes when setting up the cloud environment. You can then run your normal validation testing once it is migrated.
- Like any other project, be sure scope creep is managed closely. It is so easy to turn on additional features in the cloud that might provide some benefit to the application. However, a functioning application may not need all of these features. The ease of this ability to turn something on can lead to many additional hours of testing to validate you have not created a new set of bugs.
The items in the “Things to Consider” section above highlight that the lift-and-shift strategy can be more complicated than anticipated. It is important with any kind of cloud migration to be sure you take the time to properly analyze and evaluate your applications and data. This planning work upfront will save thousands of wasted hours due to improper migration strategy selection. As part of any cloud transformation strategy, there must be a plan to evaluate your “complete” application and data portfolio.
This evaluation should be a multi-level review that segments your portfolio into well defined categories. Lift and shift (rehost) can be an extremely beneficial strategy for many applications. It also provides a great learning exercise for those first migrations to the cloud. However, many applications will benefit both in the short term and the long term from the use of an alternative migration strategy. This is a case where one size DOES NOT fit all.