Projects are structured into several workstreams that extend over time, reflecting the evolving nature of many project activities. For instance, the project plan, which is initially established in the first few weeks, is not a static document. Instead, it is continually updated and modified to accommodate changes and developments as the project progresses. 

Our approach begins where we establish access, evaluate the appropriate tools, initiate data compilation, and identify all the necessary integration points between you and WWT. This step is crucial in setting the foundation for a successful migration and ensuring that all aspects of the process are thoroughly understood and prepared for.

In addition to the foundational preparations, we will also initiate an Optimization and Licensing Assessment (OLA) process with you during this period. This will enable us to gather the necessary data to optimize licensing and right-size environments as they are migrated to AWS.  We will install the agentless collector(s) and start to collect usage and inventory data from your environment.

We also commence the evaluation of your code repositories using an industry-leading application imaging tool. This will provide us with valuable insights into the appropriate cloud disposition of the applications, enabling us to make optimal decisions that align with your business needs and objectives.  We will install the tool and start the collection to evaluate the code.

In the Mobilize Phase, WWT continues the evaluation of existing data, applications, and infrastructure. This evaluation will focus on understanding dependencies, performance requirements, security needs, and the ability to operate in the selected cloud environment. The inventory process will leverage data from the OLA and Application Imaging processes. It's important that the applications operate for a certain period to gather accurate usage metrics. These metrics will help us optimize the destination workloads in terms of CPU, memory, network, storage, and licensing.

During this time, we create the design for the network, compute, storage, databases, and security architecture, all based on the data collected. We ensure the designs follow the AWS Well-Architected Framework, which is a comprehensive set of design principles and best practices divided into five distinct pillars.

The migration phase involves moving data, applications, and any required infrastructure to the cloud. This includes post-migration technical validation, contingency plans, and facilitation of end-user acceptance testing. 

WWT creates detailed wave plans throughout the migration effort, grouping application sets based on the application dependency mapping and the cloud disposition of each workload (re-host, re-platform, repurchase, retain, retire, and re-factor). Instead of moving everything at once, applications and data are migrated in waves. This approach allows for better control over the migration process and the ability to troubleshoot and adjust the approach as needed. Once the initial wave plan framework is developed and a small number of pilot wave plans are complete, we start moving workloads over to the AWS landing zone in accordance with established standards.