Getting Started with Migrating to the Cloud
The course is part of these learning paths
In this course, we will learn practical planning techniques for migrating business applications to public cloud services.
The course is suitable for anyone wanting to learn more about how public cloud services can be effective in business transformation.
- Identify the benefits of migrating to the cloud.
- Describe the six common migration strategies used in cloud migrations.
- Explain the stages of the Cloud Transformation Maturity model, and identify where an organization might be in cloud maturity.
- Implement a framework for assessing an organization's business and technical migration readiness.
I recommend completing the Cloud Computing for Business Professionals learning path as a pre-requisite. While this is a beginner level course, having a basic understanding of the concepts of Cloud Computing will help ensure you gain the most value from the content.
This Course Includes
In this course, we will learn hands-on strategies and techniques for migrating business applications to public cloud services. At the completion of this course, you will have a working perspective on the steps and processes required to build a migration business case and to implement a migration plan. You will also have an understanding of some of the best practices around migration planning and migration execution.
If you have thoughts or suggestions for this course, please contact Cloud Academy at firstname.lastname@example.org.
- [Instructor] Hello and welcome back. In this lecture we are going to learn how to recognize and explain the Six Rs, or the Six Common Strategies, used when discussing Cloud Migration projects. In 2011, Gartner Group outlined five common migration strategies, which provided a great benchmark for discussing and defining migration strategy in the early days of public cloud adoption. Over the fullness of time that has evolved into six definitions, which were commonly used when discussing migration to Cloud services. They're commonly called the Six R's and they are Rehost, Replatform, Repurchase, Refactor, Retain and Retire. Let's work through these six strategies, so we're clear on the operational benefits and the business merit of each construct. Just before we start, let's just reaffirm that every migration is going to be unique and that these strategies are not meant to be definitive or mutually exclusive. They should be used as guidelines and discussion starters only, something that can be very helpful when you are running a Cloud transformation workshop or a brainstorming session. And as we will see with the Expertise Please migration project, a migration project can easily include elements of all of these strategies at various stages. So first cab off the rank is Rehost, commonly referred to as lift and shift. Now lift and shift is generally as it sounds. Lifting servers or applications from the current hosting environment and shifting them to infrastructure in the public Cloud. Rehosting and the lift and shift is a very common strategy for organizations starting out on their migration journey. There are significant benefits in running servers on the scalable, pay as you go infrastructure of a public Cloud platform. So it is a relatively low resistance migration strategy and this is a great strategy for working backward from a fixed constraint or a hard deadline. In practice, the application or server will be exported via a third party export tool like VMware's V Center, for example, or created as an image that can be exported to a compute instance or container run on a Cloud compute service. Containerized applications make this process a relatively simple exercise as the operating environment is included in the container's schema. If you are running a monolithic application, then this rehosting can again be a simple way of getting started with Cloud services. Second cab off the rank is Replatforming which is to modify lift and shift. Replatforming involves making some optimizations to the application during the migration stage. So the third R is to Repurchase which is sometimes referred to as drop and shop. And this refers to the decision to move to another product. This may mean ending existing licensing and repurposing services on a new platform or service. Examples of this may be a CRM system or an industry specific application not designed to run on Cloud infrastructures. Now this is often not necessary with bespoke applications written with modern application code as with modern code it is possible to transport the code from one provider to another. The Repurchase strategy is often applied when using a proprietary database platform or proprietary product. Our fourth R is Refactorng or rearchitecting and this strategy is usually driven by a strong desire to improve services. Drivers for this might be that it is difficult to make improvements in the current environment or it may be a requirement to improve availability and reliability immediately, say to meet a specific security or compliance requirement. With refactoring, much depends on the nature of the service you want to refactor. If it is not a mission critical service, then it may be possible to rearchitect a service as required during the migration stage. Refactoring is feasible during the first phase of a migration if you do not have a time constraint. Otherwise, it is most likely better done at a later phase of the project. Okay, so strategy number five is to Retain. You may want to retain portions of your IT portfolio because there are some applications that you are not ready to migrate and feel more comfortable keeping them on premise. With this use case it may make sense to retain aspects of your IT services in the current environment and implement a hybrid or part migration strategy. So this approach makes sense if current regulatory or constitutional rules require you to store or run some aspects of your services or business application on premise or within specific regions. So that brings us to strategy number six which is to retire services. Now this strategy involves identifying assets and services that can be turned off so the business can focus on services that are widely used and of immediate value to the business. So that brings us to the end of our brief summary of the 6 Common Migration Strategies.
Head of Content
Andrew is an AWS certified professional who is passionate about helping others learn how to use and gain benefit from AWS technologies. Andrew has worked for AWS and for AWS technology partners Ooyala and Adobe. His favorite Amazon leadership principle is "Customer Obsession" as everything AWS starts with the customer. Passions around work are cycling and surfing, and having a laugh about the lessons learnt trying to launch two daughters and a few start ups.