조직 리소스 간에 프로젝트를 마이그레이션할 때는 프로젝트 및 조직 리소스 수준에서 특정 시나리오를 해결해야 할 수 있습니다. 마이그레이션 계획의 일부로 고려해야 하는 관련 서비스가 있을 수 있습니다. 프로젝트 운영과 관련된 서비스를 사용하는 경우에 이러한 사례를 고려해야 합니다.
위 단계를 완료하면 Resource Manager API를 사용하여 프로젝트를 마이그레이션할 수 있습니다. 마이그레이션을 수행하는 데 gcloud beta projects move Google Cloud CLI 명령어 또는 projects.update() REST API 메서드를 사용할 수 있습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-05-05(UTC)"],[],[],null,["# Project migration checklist\n\nThis checklist will help you to migrate projects between organization resources. The\nchecklist below contains a list of the major tasks involved in migrating a\nproject between organization resources, brief instructions for each step, and a link\nto more information. \n\n\n### [Create a migration plan](#create_migration_plan)\n\nYou should consider how your migration will impact the services running inside the project. Changes in the resource hierarchy caused by a project migration can lead to changes in inherited policies, such as organization policies and Identity and Access Management (IAM) allow and deny policies.\n\n\u003cbr /\u003e\n\nCreate a plan to make sure that any potential impacts are mitigated during your\nproject migration. To help inform your plan, use the\n[Move Analysis API](/resource-manager/docs/analyze-move) to get a detailed breakdown of blockers for\nthe project migration.\n\nFor more information, see\n[Create a migration plan](/resource-manager/docs/create-migration-plan).\n\n### [Assign Identity and Access Management roles](#assign_roles)\n\nYou need a particular set of IAM roles to migrate a project between organization resources. You will also need permission to create and manage organization policies.\n\n\u003cbr /\u003e\n\nYou can get these permissions by acquiring the following roles:\n\n- Project Mover (`roles/resourcemanager.projectMover`) on the project you want\n to migrate and its parent resource.\n\n- Project Creator (`roles/resourcemanager.projectCreator`) on the destination\n folder or organization resource.\n\n- Organization Policy Admin (`roles/orgpolicy.policyAdmin`) on both the source\n and destination organization resources.\n\nFor more details about the roles and permissions you need, see\n[Assign permissions](/resource-manager/docs/assign-iam-roles).\n\n### [Configure organization policies](#set_organization_policies)\n\nTo perform a project migration between organization resources, you must set the following organization policies:\n\n\u003cbr /\u003e\n\n- Set the `constraints/resourcemanager.allowedExportDestinations` constraint on the parent resource to the project that you want to migrate. This constraint defines the organization resources to which the project can be migrated.\n\n- Set the\n `constraints/resourcemanager.allowedImportSources` constraint on the destination resource. This constraint defines the organization resources from which projects can be imported.\n\nIf either of these constraints are not properly set, the migration will fail\nwith a `FAILED_PRECONDITION` error.\n\nTo configure organization policies required for the project migration, you\nmust have the `roles/orgPolicy.policyAdmin` role on the parent and the destination organization.\n\nFor more information about these organization policy constraints, see\n[Configure organization policies](/resource-manager/docs/configure-org-policy).\n\n### [Address any special cases](#special_cases)\n\nWhen you migrate a project between organization resources, there is a chance you'll need to address certain scenarios at the project and organization resource level. There can be services involved that you'd need to consider that As part of your migration plan, you should consider these cases if you depend on the services involved for the operation of your project.\n\n\u003cbr /\u003e\n\nFor a list of special cases and how to handle them, see\n[Handling special cases](/resource-manager/docs/handle-special-cases).\n\n### [Perform the migration](#perform_migration)\n\nOnce you have finished the above steps, you can use the Resource Manager API to migrate a project. You can use the `gcloud beta projects move` Google Cloud CLI command, or the `projects.update()` REST API method to perform the migration.\n\n\u003cbr /\u003e\n\nFor more details about migrating your project, see\n[Perform the migration](/resource-manager/docs/perform-migration)."]]
