Everyone’s Guide to Migrating Applications onto AWS

1 Everyone s Guide to Migrating Applications onto AWS Cloudsoft Whitepaper March 2018 Everyone s Guide to Migrating Applications onto AWS 2018 Cloudsoft Corporation. Introduction .. 1 Who should read this whitepaper .. 2 About Cloudsoft and the Author .. 2 Understanding the Six Rs of Application Migration to AWS .. 4 Why some Applications are not migrated to the cloud .. 4 Deciding on a Migration Method .. 6 Important: Choosing the right Migration Partner .. 7 Migration method #1: Repurchasing ( Drop and Shop ) .. 8 Repurchasing: Drivers .. 8 Repurchasing: Benefits .. 9 Repurchasing: Risks .. 9 Repurchasing: How .. 10 Repurchasing: What .. 10 Migration method #2: Rehosting ( Lift and Shift ) .. 12 Rehosting: Why .. 12 Rehosting: 13 Rehosting: 13 Rehosting: How .. 14 Rehosting: What .. 15 Migration method #3: Replatforming ( Lift and Shape ).

2 16 Replatforming: Why .. 16 Replatforming: Benefits .. 16 Replatforming: Risks .. 17 Replatforming: How .. 17 Replatforming: What .. 18 Migration method #4: Refactoring .. 19 Refactoring: Why .. 19 Refactoring: Benefits .. 19 Refactoring: Risks .. 19 Refactoring: How .. 20 Summary .. 21 Everyone s Guide to Migrating Applications onto AWS 2018 Cloudsoft Corporation. Introduction According to leading industry analysts, by 2020 there will be more enterprise Applications running in the public cloud than anywhere else. The current bellwether analysis says the top global 1000 companies have, on average, around 2000 Applications . In that single segment it s two million workloads. Consider that the current state of cloud is 15% of those workloads but, over the next three years, it will rise to 75%, that means workloads will move to the cloud in the near future. But why and how is this happening?

3 There are three drivers for public cloud today: Increase top line revenue The imperative is to compete better in the marketplace by being more agile, characterized by experimentation, velocity and quality, and measured by an increase top line revenue. Improve bottom line net income Eliminate unnecessary IT costs from the business and focus on core productivity to improve bottom line net income. Compete on a level playing field Public clouds democratize the access to the latest technology, which was only previously available to big companies with big IT budgets. This means small-budget fast organizations can now compete on a level playing field, technologically, with big-budget slow organizations. Given these drivers, business leaders seek to measure their success with public cloud adoption across four key vectors: Given these drivers and benefits, it s clear why organizations are adopting cloud at a rate where more than half of all workloads will be on the cloud by 2020, the next question is How are organizations getting on the cloud ?

4 There are two routes to cloud : 1. Deploy net-new Applications straight to the cloud , often referred to as a cloud First strategy. Everyone s Guide to Migrating Applications onto AWS 2018 Cloudsoft Corporation. 2. Migrate existing services, Applications and workloads. This paper has been written to help an organization s management team see the complete picture of application migration to AWS, including definitions, risks, benefits with high-level how-to and what resource guides. With this complete picture, the management team of any organization should be able to begin planning their migration strategy which will generally look something like this: 1. Research the topic (this paper and other resources and expert guidance). 2. Create the Business Plan. 3. Discover the Application Landscape. 4. Decide a Migration Method for each application. 5. Execute the Migrations to AWS 6. Transition to AWS 7.

5 Retrospective adapting and improving migrations through learning Who should read this whitepaper Some say it takes a village to raise a child and it take a team to exploit the cloud . Migrations to the cloud involve multiple actors, therefore this paper has been written with the following three roles in mind to ensure the Why, What and How is explained. Business Leaders What is the business case to migrate to clouds, what are the business outcomes? Change/Program Managers What is the methodology to migrate, what is the cost, what skills are required and the impact/benefit to services? Implementation Experts What tools, technologies and skills will be needed? This paper explains the decision criteria involved in selecting Rehosting, Replatforming, Repurchasing or Refactoring when moving Applications to the leading public cloud , Amazon Web Services (AWS). Each method is detailed with notes on useful tools, process, and the skills required to execute the method.

6 The paper finishes with recommendations on how to choose a partner to help with migrations. > Contact Cloudsoft for help in producing your cloud Migration Business Case and creating your Well Architected AWS Environment About Cloudsoft and the Author Steve Chambers has built clouds, bought clouds and consumed clouds over the past decade. With this unique experience with companies that range from small startups to global organizations, he helps Cloudsoft help Everyone s Guide to Migrating Applications onto AWS 2018 Cloudsoft Corporation. customers win by exploiting the cloud . Steve helps the community by sharing his cloud experiences through papers like this and speaking events like cloud Expo Europe and the Service Desk Institute. Steve is currently the Chief Operating Office of Cloudsoft. Cloudsoft have built up years of experience working with Applications and automation in the cloud and have specially designed services to Migrate, Run and Evolve Applications on Amazon Web Services (AWS) through the Rx3 solution.

7 This delivers real business outcomes for our customers: reducing costs, increasing uptimes, improving performance and responsiveness, and continuously exploiting the pace of AWS innovation. How did Cloudsoft get here? Over the last 9 years, Cloudsoft has delivered successful outcomes through software development and service delivery, both locally and internationally, for companies as large and diverse as BT, IBM and Giumarra (headquartered in California). Having developed cloud capabilities, software, patterns, practices and people solving complex cloud problems with large organisations, Cloudsoft are now democratising access to these special skills by making our services available to a broader range of UK organisations. Cloudsoft is headquartered in the UK and a privately held company. Cloudsoft has a highly talented and experienced team of engineers and business consultants led by seasoned executives backed by a world-class advisory board.

8 Everyone s Guide to Migrating Applications onto AWS 2018 Cloudsoft Corporation. Understanding the Six Rs of Application Migration to AWS This Manager s Guide paper focuses on the second route to public cloud : Migrating Applications to Amazon Web Services (AWS). When an organization is considering Migrating an existing application to AWS they have six options to choose from known as The 6Rs for each application. It is common for complex, multi-application migration programs to use a number of these methods at the same time: there is no one, size fits all approach. Why some Applications are not migrated to the cloud Two of 6Rs Remain and Retire are decisions to not migrate an application to the cloud . Why do organizations choose not to migrate to the cloud ? Why Retain? Existing, significant sunk cost for non- cloud which necessitates the business to sweat existing assets and practices.

9 Legacy OS and Applications are not supported in the cloud The business justification for Migrating is insufficient Why Retire? Applications found during a Discovery project are no longer required (sometimes the fact they are still running is a surprise to the organization, and just turning them off can yield significant savings). Everyone s Guide to Migrating Applications onto AWS 2018 Cloudsoft Corporation. Applications may be duplicated in the organization so some can be retired There may already be a decommissioning or consolidation project in progress, and the application is that scope The application might be redundant, such as an old cluster or DR setup The remaining four choices for migration are selected according to a wide range of drivers in play in the organization at the time that migrations are being considered. These drivers are usually uncovered in the Business Case process and provided as inputs to the migration strategy in the form of compelling events, pain points, application availability, skills available to do the migration, and what the future state of the application needs to be post-migration.

10 Compelling Event or Pain Point? If the organization has a compelling event to evacuate a hosting environment, then a fast-paced Rehosting method can be the only option. Is the application available in a Marketplace? If an application can be Repurchased, then it can be a short-cut to cloud . But if the application is not on AWS Marketplace, then this path may not be possible. Do we have the Skills, can we afford a Partner? If the organization doesn t have the skills to Replatform or Refactor, and they can t afford to partner, then their options are limited to Rehost and Repurchase. What is the application s desired Future State? If the plan is to evolve the application over several years, then Refactor might be the best path. While this is often the initially slowest method, it ultimately delivers the greatest agility and ability to exploit cloud innovation, but it requires deep skills. Everyone s Guide to Migrating Applications onto AWS 2018 Cloudsoft Corporation.