After planning your migration, you can continue to the execution phase. This and the following documents provide you with a synthesis of the methods and tools you can use to execute your migration.
Before you begin
Ensure that you have completed the following tasks:
- Discover your assets.
- Assess your infrastructure.
- Plan your migration.
- Review the Enterprise foundations blueprint and landing zone design.
Initial migration preparation
The cloud migration project is the major organizational effort that drives the migration of your workloads to Google Cloud.
Each migration project is divided into waves. A wave is a group of applications that share common characteristics or interdependencies, as identified by the workload discovery and assessment. Standalone applications and databases are typically good candidates for a first migration wave given their low external dependencies. On the other hand, workloads with significant interdependencies would constitute a complex migration wave that requires additional planning. In this case, you need to refine the migration plan to review the business impact of interdependencies, and remove the blockers that potentially prevent the migration.
Workloads within a migration wave are divided into move groups and migrated to Google Cloud in sprints. A move group is a group of infrastructure resources and workloads that you need to migrate together—these can be part of the same application or a group of applications that are interdependent.
During every sprint, you need to perform the following actions:
- Prepare and integrate the tools required for migration.
- Develop a sprint plan.
- Execute the sprint plan.
Migration process and methodology
Sprint planning and playbook
In the sprint plan, define how you are going to execute the migration waves categorized into a sprint. Create a playbook by addressing the following building blocks.
| # | Item | Description |
|---|---|---|
| 0 | Migration tools architecture | Architecture of tools constituting a migration factory (tools for ongoing assessment, wave plan refinement, workload-specific migration, build, testing, deployment, and monitoring) |
| 1 | Migration checklist | Checklist for use before and during the migration sprint |
| 2 | Inventory | List of workloads that will be migrated to Google Cloud |
| 3 | Sprint runbook | Execution guidelines for migrating each workload |
| 4 | Migration plan | Step-by-step migration plan (process) to be followed during the migration sprint |
| 5 | Network and security rules | List of all of the firewall rules for ingress and egress on
Google Cloud DNS changes during migration to Google Cloud |
| 6 | Risks and mitigation | Possible risks during the migration sprint and mitigation steps |
| 7 | Testing and validation | Test plan to validate functional and non-functional requirements |
| 8 | Rollback plan | Rollback steps by workload |
| 9 | Team composition | Team composition and roster with contact details |
| 10 | Governance | RACI matrix of migration execution team, cadence and reporting, escalation resolution mechanisms |