In our first blog about AWS migration<\/a>, we discussed how to get started on the huge lift that is migrating your business to the cloud. The assess phase plays a crucial role in preparing for your migration.<\/p>\n In this blog, we\u2019ll look at the second phase, the mobilize phase, which is the next major step in your AWS migration journey.<\/p>\n The “mobilize” phase in an AWS migration aims to establish a functional base for the migration process and address any deficiencies identified in the assess phase. The mobilize phase streamlines the migration process by offering clear guidance on migration strategies.<\/strong><\/p>\n Per AWS best practices, you will want to prepare a scalable framework that will work for your migration. Generally, this stage can take around two to six months, depending on your industry and regulations. As we mentioned in the first blog, we highly recommend using a vendor to make sure your migration is a success.<\/p>\n The mobilize phase focuses on eight core areas:<\/p>\n Let\u2019s take a closer look at what each area means for your AWS migration journey.<\/p>\n During this phase, your goal is to perform a very detailed discovery. This discovery includes identifying data sources, application level information, and establishing a migration strategy. You will uncover detailed performance metrics that will assist with allocating and right-sizing target resources on AWS. Also, service naming and tagging will help you identify patterns and group servers and applications.<\/strong><\/p>\n Although you and your partner would have already completed some data capture in the assess phase, you now need more detailed information. This includes dependencies, server network activity and application information. You can then use this information to create the migration waves.<\/p>\n AWS offers several services to help with this planning, including AWS Application Discovery Services<\/a> (ADS), an agent-based discovery tool.<\/p>\n Discovery tools cannot collect all the information required for your migration planning (criticality of your application, business units, service level requirements). You can collect this extra detail using the AWS Migration Portfolio Assessment<\/a> (MPA) tool. MPA allows users to create a questionnaire to capture all the relevant information.<\/strong> Once designed, it sends a link to the application owner, and they can provide the requested information.<\/p>\n The reason you want to collect this information is to help determine the migration strategy for each application. Gartner<\/a> originally introduced the 7Rs concept, which lists seven cloud migration options: refactor, re-platform, repurchase, rehost, relocate, retain and retire.<\/p>\n AWS follows the shared responsibility model, meaning the customer is responsible for what is in the cloud, and AWS is responsible for the security of the cloud.<\/p>\n When looking at security and compliance, you must identify the organization\u2019s needs. You need this step to ensure you correctly configure the landing zone and security controls. Some key areas of security are:<\/p>\n During this step, you need to review all the existing operating models and make updates to support the would-be environment in the cloud. The goal is to provide best-practices guidance and enhance the operational model both in hybrid mode and when in AWS. These AWS migration best-practice guidelines would include:<\/strong><\/p>\n A landing zone is an AWS environment that acts as a starting point for deploying workloads and applications. You should design this with a well-architected, multi-account setup, which includes elements such as identity management, governance, security, network design and logging.<\/p>\n AWS offers two options for creating a landing zone: using a service-based AWS Control Tower or building a custom landing zone.<\/strong> AWS manages the former option and uses automated processes to save time and ensure a secure and scalable environment. The latter requires a higher level of AWS knowledge. With Control Tower, you can use integrated services like AWS Service Catalog and AWS Organizations to manage access to accounts in the landing zone.<\/p>\n CCoE is a cross-functional team from across the organization made up of experts on cloud best practices. They are responsible for enabling the organization to use the value of the cloud. When creating a CCoE, diversity and cross-functional representation are key. The team\u2019s structure should evolve as the business progresses through the transformation stages.<\/strong><\/p>\n Ideally, the CCoE team will help enable business-facing software teams to focus on rapid experimentation and delivering customer outcomes by codifying routine platform tasks and best practices. Your CCoE team will help implement consistent patterns and frameworks, so teams can flexibly operate according to their unique needs and remain within the organization\u2019s governance and compliance standards.<\/p>\n During the AWS migration mobilize phase, you or your partner want to provide multiple, highly accurate data points and create a business case for the adoption or reinvention of the cloud. The business case should include a total cost of ownership (TCO) analysis<\/a> comprised of your company\u2019s baseline spend, migration cost, and AWS run costs.<\/strong> Be sure to include business benefits such as staff productivity, operational resiliency and business agility.<\/p>\n Migration governance refers to the policies, processes and practices an organization follows to manage and control its migrated data. This includes planning and risk management, compliance, data security and change management. The purpose of migration governance is to ensure you execute your AWS migration efficiently and that it aligns with any regulatory requirements. Ideally, you\u2019d like to avoid risks and minimize downtime, ensuring that the migration process results in a positive outcome for the organization.<\/p>\n This is the final stage of the mobilize phase. Here, you can expect to migrate a handful (three to five) of pilot applications. These pilot migrations should represent the architecture and technology stack of similar business applications.<\/strong> Once you\u2019ve identified and actioned these pilot applications, this will test out the newly created landing zone. It will also provide hands-on skills for tools you can use as a blueprint during the migration.<\/p>\n The mobilize phase of an AWS migration is where you get into the nitty-gritty aspects of preparation, even beginning your first migrations by the end of the phase. We highly recommend partnering with a vendor proficient in migrating exhaustive and mature solutions.<\/p>\n Our next blog will cover the final phase of AWS migrations, the migrate phase.<\/p>\n\n What is the AWS Migration Mobilize Phase?<\/h2>\n
\n
Eight Areas of the AWS Migration Mobilize Phase<\/h2>\n
Discovery and Planning<\/h3>\n
Data Sources<\/h4>\n
Application-Level Information<\/h4>\n
Migration Strategy<\/h4>\n
Security and Compliance<\/h3>\n
\n
Operating Model<\/h3>\n
\n
Landing Zone<\/h3>\n
Cloud Center of Excellence<\/h3>\n
Business Case<\/h3>\n
AWS Migration Governance<\/h3>\n
Applications Migrated \u2013 Pilot Migrations<\/h3>\n
Conclusion<\/h2>\n