プロジェクトを移動すると、Identity and Access Management ポリシーまたは直接接続されている組織のポリシーがすべてそのプロジェクトとともに移動します。ただし、リソース階層のプロジェクトは、親リソースから継承するポリシーの影響も受けます。特定のサービスを使用する権限をユーザーに付与する IAM ロールがプロジェクトから継承されている場合、エクスポート先で権限を継承しない限り、ユーザーはエクスポート先でそのサービスにアクセスできません。
たとえば、サービス アカウントでフォルダ A のユーザーにストレージのオブジェクト作成者のロールがバインドされているとします。サービス アカウントには、フォルダ A 内の任意のプロジェクトで Cloud Storage にデータをアップロードする権限があります。同じ継承された権限を持たないいずれかのプロジェクトをフォルダ B に移動すると、そのプロジェクトのサービス アカウントはデータのアップロード権限を失い、結果的にサービスが停止します。
[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2024-12-21 UTC。"],[],[],null,["# Moving a project\n\nThis guide explains how to move a project within your organization resource.\n\nThe project is the base-level organizing entity in a\nGoogle Cloud organization resource. Projects are created\nunder organization resources, and can be placed under folders or the organization\nresource itself, forming the\n[resource hierarchy](/resource-manager/docs/cloud-platform-resource-hierarchy). You can move project\nresources within your resource hierarchy, but should consider the policy\nimplications of the move before you make it.\n| **Note:** The following instructions are only for moving a project within an organization resource. For information about migrating a project between organization resources, see [Migrating projects](/resource-manager/docs/project-migration).\n\nWhen you move a project, any Identity and Access Management policies or organization policies that\nare directly attached will move with it. However, a project in your resource\nhierarchy is also affected by the policies that it inherits from parent\nresources. If a project inherits an IAM role that provides users\npermission to use a particular service, users will not have access to that\nservice at the destination unless it would inherit the permission at the\ndestination as well.\n\nFor example, consider a service account has the **Storage Object Creator**\nrole bound to a user at Folder A. The service account has permissions to upload\ndata to Cloud Storage in any project in Folder A. If you moved one of these\nprojects to Folder B, which does not have the same inherited permissions, the\nservice account for that project loses the ability to upload data, resulting in\na service outage.\n\nThese same considerations apply if organization policies are defined at the\nsource and destination folders. Like IAM policies, organization\npolicies are inherited. Consequently, you must ensure that your organization\npolicies are consistent between source and destination folders.\n\nTo learn more about organization policies, see\n[Introduction to the organization Policy Service](/resource-manager/docs/organization-policy/overview).\n\nTo move a project, you need the Project Mover IAM role\n(`roles/resourcemanager.projectMover`) on both the source folder and the\ndestination folder. If the resource is not in a folder, you need this role on\nthe organization resource.\n\nThese roles give you the following required permissions:\n\n- `resourcemanager.projects.update` on the project\n- **If the resource is in a folder:** `resourcemanager.projects.move` on the source folder and the destination\n- **If the resource is not in a folder:** `resourcemanager.projects.move` on the organization resource\n\nYou can also gain these permissions with [custom\nroles](/iam/docs/creating-custom-roles), or other predefined roles. \n\n### Console\n\nTo move a project:\n\n1. In the Google Cloud console, go to the **Manage resources** page.\n\n [Go to Manage resources](https://console.cloud.google.com/cloud-resource-manager)\n\n \u003cbr /\u003e\n\n2. Select your Organization from the **Organization** drop-down on the top\n left of the page.\n\n3. Click on your project's row to select your project from the list of\n resources. Note that you *must not* click on the name of the\n project, which takes you to the project's IAM page.\n\n4. Click on the options menu (the vertical ellipsis) in the row and click\n **Move**.\n\n5. Click **Browse** to select the folder to which you want to move the\n project.\n\n6. Click **Move**.\n\n### gcloud\n\nTo move a project, run the\n[`gcloud beta projects move`](/sdk/gcloud/reference/beta/projects/move)\ncommand: \n\n```\ngcloud beta projects move PROJECT_ID \\\n--DESTINATION_TYPE DESTINATION_ID\n```\n\nWhere:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e is the ID or number of the project you wish to\n move.\n\n- \u003cvar translate=\"no\"\u003eDESTINATION_TYPE\u003c/var\u003e is either `organization` or `folder`.\n\n- \u003cvar translate=\"no\"\u003eDESTINATION_ID\u003c/var\u003e is the ID of the organization resource or folder to which\n you want to move the project. You can only specify one target.\n\n### API\n\nYou can use the v3\n[`projects.move`](/resource-manager/reference/rest/v3/projects/move) method\nto move a project.\n\nRequest: \n\n```\nPOST https://cloudresourcemanager.googleapis.com/v3/{name=PROJECT_NAME}:move\n{\n \"destinationParent\": DESTINATION_PARENT\n}\n```\n\nWhere:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_NAME\u003c/var\u003e is the name of the project you want\n to update. For example, `projects/415104041262`\n\n- \u003cvar translate=\"no\"\u003eDESTINATION_PARENT\u003c/var\u003e is the new parent organization resource\n or folder under which you want to move the project. For example:\n `organizations/12345678901`\n\nIf successful, the request will return an\n[Operation](/resource-manager/reference/rest/Shared.Types/Operation) which\ncan be used to track the project move."]]
