[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-11。"],[],[],null,["# Execute your migration\n\nAfter [planning your migration](/migration-center/docs/migration-planning-overview),\nyou can continue to the execution phase.\nThis and the following documents provide you with a synthesis of the methods\nand tools you can use to execute your migration.\n\nBefore you start\n----------------\n\n- Complete the first wave of [discovery](/migration-center/docs/start-asset-discovery), [assessment](/migration-center/docs/stratozone-assessment-overview), and [migration planning](/migration-center/docs/migration-planning-overview).\n- Complete the [foundation design](/foundation-toolkit) and [landing zone design](/architecture/landing-zones).\n\nInitial migration preparation\n-----------------------------\n\nThe **cloud migration project** is the major organizational effort that drives\nthe migration of your workloads to Google Cloud.\n\nEach migration project is divided into **waves**. A wave is a group of\napplications that share common characteristics or interdependencies, as\nidentified by the workload discovery and assessment. Standalone applications and\ndatabases are typically good candidates for a first migration wave given their\nlow external dependencies.\nOn the other hand, workloads with significant interdependencies\nwould constitute a complex migration wave that requires additional planning.\nIn this case, you need to refine the migration plan to review the business\nimpact of interdependencies, and remove the blockers that potentially\nprevent the migration.\n\nWorkloads within a migration wave are divided into **move groups** and migrated\nto Google Cloud in **sprints**.\nA move group is a group of infrastructure\nresources and workloads that you need to migrate together---these can be part of\nthe same application or a group of applications that are interdependent.\n\nDuring every sprint, you need to perform the following actions:\n\n- Prepare and integrate the tools required for migration.\n- Develop a sprint plan.\n- Execute the sprint plan.\n\nMigration process and methodology\n---------------------------------\n\n### Sprint planning and playbook\n\nIn the sprint plan, define how you are going to execute the migration waves\ncategorized into a sprint. Create a playbook by addressing the following\nbuilding blocks.\n\n### Migration execution\n\nAfter you have completed the migration planning and preparation phase,\nthis section describes how to perform repeatable migrations\nand validations to Google Cloud.\n\n#### Assess\n\nThe first iteration of assessment happens during the migration planning phase,\nand produces data on dependencies between workloads and\ninfrastructure components.\nYou must continue to perform discovery and assessment throughout your\ncloud migration project to\nrecalibrate and enrich data relating to the following aspects:\n\n- Application and database mapping to infrastructure mapping (to identify all of the infrastructure and platform components for a business workload)\n- Mapping between infrastructure to applications, databases, and services (to identify all of the business workloads attached to an infrastructure or platform component)\n- Dependencies across business workloads\n- Resource consumption by workloads\n- Identification of any workloads that were not discovered in the initial wave of assessment\n- Identification of new or changed landing zone requirements that have not been identified in the initial wave of assessment\n- Identification of blocking issues that potentially prevent the migration\n\nAn ongoing assessment is critical to continuously calibrate and refine\nmove group, identify and mitigate risks, and refine and optimize migration\nwave plans.\n\n#### Plan\n\nThe planning phase in a migration wave aims at defining the final scope of the\nsprints within a wave, and consolidates the component-specific migration plans\ninto a single plan.\nThe outputs of this phase are the following:\n\n- Move group(s) within the scope of the current sprint\n- Migration sprint checklist\n- Mitigations to remediate blocking issues\n- Migrate, build, test, and deployment plan\n- Rollback plan\n- Scheduling of execution\n\nLow-level detailed planning is critical for a successful deployment that\nfollows.\n\n#### Deploy\n\nDuring the deployment phase, your migration team\nexecutes the migration plan and removes any critical issues.\nIt is recommended to set up regular status meetings\nto track the execution plan. These status meetings, however, should not be used\nto troubleshoot issues.\nInstead, set up separate, dedicated sessions with respective technical\nexperts.\n\nThe outputs of the deployment phase are the following:\n\n- Migration plan updates (status per step, notes)\n- Migration issue tracker updates\n- Post-migration test results\n- CMDB updates (if applicable)\n- Migration results communication to stakeholders\n\nIf the deployment is unsuccessful, for example, if the migration plan fails,\nthe tests fail or the fix is impossible within the defined migration timeframe,\nyou need to execute the rollback plan.\nIt is advised to run application tests after the rollback\nand ensure any external changes that were part of the migration plan,\nsuch as upstream and downstream systems configuration, are rolled back as well.\n\n#### Optimize\n\nThe optimization phase lets your project team regroup after completing the\ndeployment phase to document the lessons learned and implement\nimprovements for the following waves and sprints.\nFor the scope that has already\nbeen migrated, the optimization phase can be used to resolve non-critical\npost-migration issues.\n\nThis phase is important as it enables continuous improvement throughout the\nproject timeline.\n\nThe outputs of the phase are the following:\n\n- Migration issue tracker updates\n- Project knowledge base updates, if applicable\n\nMigration tools\n---------------\n\nAutomation tools play an important role in the migration lifecycle.\nDuring the execution phase of your migration, you need to create an\narchitecture of automation tools based on a number of factors, such as the\ntype of workloads to be migrated, geographical distribution and rollout\nstrategy, and security requirements.\n\nThe following documents present several automation tools that address the\nfollowing capabilities:\n\n- [Migration and modernization tools](/migration-center/docs/migration-modernization-tools)\n- [Build and CI/CD automation tools](/migration-center/docs/build-ci-cd-automation-tools)\n- [Testing tools](/migration-center/docs/testing-tools)\n\nWhat's next\n-----------\n\n- Learn more about the [tools for migration and modernization](/migration-center/docs/migration-modernization-tools).\n- Learn more about [Google Cloud migration](/products/cloud-migration)."]]