[[["わかりやすい","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-04-24 UTC。"],[],[],null,["# Configure organization policies\n\nTo migrate a project to a new organization resource, you must first apply\nan organization policy that will define the organization resources to which the\nproject can migrate. You must also set an organization policy in the\ndestination that defines the organization resources from which projects can be\nimported.\n\nTo configure organization policies required for the migration, you\nmust have the `roles/orgPolicy.policyAdmin` role on the parent and the\ndestination organization. For detailed instructions, see [Using constraints](/resource-manager/docs/organization-policy/using-constraints).\n| **Caution:** If you do not set the following organization policies, the migration will result in a `FAILED_PRECONDITION` error. You must do the following:\n\n- On the parent resource of the project you want to migrate between organization\n resources, set an organization policy that includes the\n `constraints/resourcemanager.allowedExportDestinations` constraint. This will\n define the target destination as a valid location to which you can migrate the\n project.\n\n- On the destination resource, set an organization policy that includes the\n `constraints/resourcemanager.allowedImportSources` constraint. This will define\n the source as a valid location from which you can migrate your project.\n\nFor example, say you had a project `my-test-project` that existed under an\norganization resource with the ID `12345678901`, and you wanted to migrate it to a\nnew organization resource for your secondary business unit, with the ID\n`45678901234`.\n\nYou would set an organization policy on `organizations/12345678901` with the\n`constraints/resourcemanager.allowedExportDestinations` constraint enforced and\n`under:organizations/45678901234` set as an **allowed_value**.\n\nThen, set an organization policy on `organizations/45678901234` with the\n`constraints/resourcemanager.allowedImportSources` constraint enforced and\n`under:organizations/12345678901` set as an **allowed_value**.\n\nOnce these organization policies are enforced, you will be able to migrate\n`my-test-project` from `organizations/12345678901` to\n`organizations/45678901234`, assuming you have the permissions noted in\n[Assign permissions](/resource-manager/docs/assign-iam-roles).\n| **Note:** Whether you are using [dedicated import and export folders](/resource-manager/docs/create-migration-plan#import_export_folders) or not, it is good practice to remove these organization policies after you are done moving projects across organization resources. You can enforce them again if you need to perform another project migration.\n\n### Change the billing account for a project\n\nCloud Billing accounts can be used across organization resources. Moving a\nproject from one organization resource to another won't impact billing, and\ncharges will continue against the old billing account. However, migration of projects between organization\nresources often also include a requirement to migrate to a new billing account.\n\nTo change the billing account, do the following:\n\n1. Go to the **Billing page** in the Google Cloud console. \n [Go to the Billing page](https://console.cloud.google.com/billing)\n2. Click the name of the billing account you want to change.\n3. Under **Projects linked to this billing account**, find the name of the Project to migrate and then click the menu button to the right.\n4. Click **Change billing**, and then select the new billing account.\n5. Click **Set account**.\n\nCharges already incurred that have not yet been reported in the transaction\nhistory will be billed to the former billing account. This can include charges\nfrom up to two days prior to when the project was migrated.\n| **Note:** If you change the billing account attached to a project which has active Google Cloud Marketplace subscriptions, those subscriptions are automatically canceled. For more information, see [Managing billing for Cloud Marketplace products](/marketplace/docs/manage-billing).\n\n### Migrate a billing account between organization resources\n\nA billing account can be migrated from one organization resource to another,\nalthough this isn't often a necessary step. Most existing organization resources\nwill already have a billing account that should be used instead.\n\nIf a new billing account has no organization resource associated with\nit, you must get the `roles/billing.admin` role on the billing account and\nthe `roles/billing.admin` and `roles/billing.creator` roles on the\norganization resource that you want to associate with your billing account.\n\nIf you need to migrate an existing billing account:\n\n1. You must get the `roles/billing.admin` role on the source and destination\n organization resources, and the `roles/billing.creator` role on the\n destination organization resource.\n\n2. Go to the **Billing page** in the Google Cloud console. \n\n [Go to the Billing page](https://console.cloud.google.com/billing)\n\n3. Click on the name of the billing account you want to migrate.\n\n4. At the top of the **Account Management** page, click **Change organization**.\n\n5. Select the destination organization resource, and then click **Ok**.\n\nThe billing account is now associated with the specified organization resource.\n\nWhat's next\n-----------\n\nTo learn about how to handle special cases during project migration, see [Handling special cases](/resource-manager/docs/handle-special-cases)."]]
