프로젝트를 새 조직 리소스로 마이그레이션하려면 프로젝트를 마이그레이션할 수 있는 조직 리소스를 정의하는 조직 정책을 먼저 적용해야 합니다. 또한 프로젝트를 가져올 수 있는 조직 리소스를 정의하는 조직 정책을 대상에 설정해야 합니다.
마이그레이션에 필요한 조직 정책을 구성하려면 상위 조직 및 대상 조직에 대한 roles/orgPolicy.policyAdmin 역할이 있어야 합니다.
조직 리소스 간에 마이그레이션하려는 프로젝트의 상위 리소스에서 constraints/resourcemanager.allowedExportDestinations 제약조건을 포함하는 조직 정책을 설정합니다. 그러면 대상 목적지가 프로젝트를 마이그레이션할 수 있는 유효한 위치로 정의됩니다.
대상 조직에서 constraints/resourcemanager.allowedImportSources 제약조건이 포함된 조직 정책을 설정합니다. 그러면 해당 소스가 프로젝트를 마이그레이션할 수 있는 유효한 위치로 정의됩니다.
예를 들어 ID가 12345678901인 조직 리소스에 my-test-project 프로젝트가 있고, 이를 보조 비즈니스 단위의 새 조직 리소스(ID 45678901234)로 마이그레이션한다고 가정해 보겠습니다.
organizations/12345678901에 조직 정책을 설정하고, constraints/resourcemanager.allowedExportDestinations 제약조건을 적용하고, under:organizations/45678901234를 allowed_value로 설정합니다.
그런 다음 organizations/45678901234에 조직 정책을 설정하고, constraints/resourcemanager.allowedImportSources 제약조건을 적용하고, under:organizations/12345678901을 allowed_value로 설정합니다.
이러한 조직 정책이 시행되면 권한 할당에 언급된 권한이 있을 경우 organizations/12345678901에서 organizations/45678901234로 my-test-project를 마이그레이션할 수 있게 됩니다.
프로젝트의 결제 계정 변경
여러 조직 리소스에서 Cloud Billing 계정을 사용할 수 있습니다. 조직 리소스 간에 프로젝트를 이동해도 결제에는 영향을 미치지 않으며 이전 결제 계정에 계속 청구됩니다. 그러나 조직 리소스 간에 프로젝트를 마이그레이션하려면 새 결제 계정으로 마이그레이션해야 하는 경우도 많습니다.
[[["이해하기 쉬움","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)."]]
