To migrate a project to a new organization resource, you must first applyan organization policy that will define the organization resources to which theproject can migrate. You must also set an organization policy in thedestination that defines the organization resources from which projects can beimported.

To configure organization policies required for the migration, youmust have theroles/orgPolicy.policyAdmin role on the parent and thedestination organization. For detailed instructions, seeUsing constraints.

Caution: If you do not set the following organization policies, the migrationwill result in aFAILED_PRECONDITION error.You must do the following:

• On the parent resource of the project you want to migrate between organizationresources, set an organization policy that includes theconstraints/resourcemanager.allowedExportDestinations constraint. This willdefine the target destination as a valid location to which you can migrate theproject.

• On the destination resource, set an organization policy that includes theconstraints/resourcemanager.allowedImportSources constraint. This will definethe source as a valid location from which you can migrate your project.

For example, say you had a projectmy-test-project that existed under anorganization resource with the ID12345678901, and you wanted to migrate it to anew organization resource for your secondary business unit, with the ID45678901234.

You would set an organization policy onorganizations/12345678901 with theconstraints/resourcemanager.allowedExportDestinations constraint enforced andunder:organizations/45678901234 set as anallowed_value.

Then, set an organization policy onorganizations/45678901234 with theconstraints/resourcemanager.allowedImportSources constraint enforced andunder:organizations/12345678901 set as anallowed_value.

Once these organization policies are enforced, you will be able to migratemy-test-project fromorganizations/12345678901 toorganizations/45678901234, assuming you have the permissions noted inAssign permissions.

Note: Whether you are usingdedicated import and export folders or not, it is goodpractice to remove these organization policies after you are done movingprojects across organization resources. You can enforce them again if you needto perform another project migration.

Change the billing account for a project

Cloud Billing accounts can be used across organization resources. Moving aproject from one organization resource to another won't impact billing, andcharges will continue against the old billing account. However, migration of projects between organizationresources often also include a requirement to migrate to a new billing account.

To change the billing account, do the following:

1. Go to theBilling page in the Google Cloud console.
   Go to the Billing page
2. Click the name of the billing account you want to change.
3. UnderProjects linked to this billing account, find the name of theProject to migrate and then click the menu button to the right.
4. ClickChange billing, and then select the new billing account.
5. ClickSet account.

Charges already incurred that have not yet been reported in the transactionhistory will be billed to the former billing account. This can include chargesfrom up to two days prior to when the project was migrated.

Note: If you change the billing account attached to a project which has activeGoogle Cloud Marketplace subscriptions, those subscriptions are automaticallycanceled. For more information, seeManaging billing for Cloud Marketplace products.

Migrate a billing account between organization resources

A billing account can be migrated from one organization resource to another,although this isn't often a necessary step. Most existing organization resourceswill already have a billing account that should be used instead.

If a new billing account has no organization resource associated withit, you must get theroles/billing.admin role on the billing account andtheroles/billing.admin androles/billing.creator roles on theorganization resource that you want to associate with your billing account.

If you need to migrate an existing billing account:

1. You must get theroles/billing.admin role on the source and destinationorganization resources, and theroles/billing.creator role on thedestination organization resource.

2. Go to theBilling page in the Google Cloud console.
   Go to the Billing page

3. Click on the name of the billing account you want to migrate.

4. At the top of theAccount Management page, clickChange organization.

5. Select the destination organization resource, and then clickOk.

The billing account is now associated with the specified organization resource.

What's next

To learn about how to handle special cases during project migration, seeHandling special cases.