Resource Hierarchy - Migrating an existing project to a new GCP Org

[dheerajpanyam]

I have an existing project , let's call it project A that is a live project already associated with a billing account and part of a GCP Org (source). The goal is to migrate / move this project A  to a new GCP Org (target). When i go to the source Org and select the project to move it doesn't list the new Org for some reason. I have Org Admin, Project Mover and billing Admin permissions in source project so IAM permissions wise i don't see anything missing.  Also when i migrate the project  will  the billing account linked to the project also get transferred to the target Org or do i need to do anything special ?

Note :- The IAM principal / email  address in source and target GCP Orgs are from their respective domains. Also I have added the target IAM principal to the source Org but still doesn't help.

[DarwinVinoth]

1. You must have resourcemanager.project.create on the target org.
2. Ensure that Organization Policy does not restrict the project move on both the source and target org. 

Ref: https://cloud.google.com/resource-manager/docs/project-migration

Thanks, 
Darwin Vinoth.
Linkedin 

[dheerajpanyam]

Thanks @DarwinVinoth . Yes i have those permissions and no Org policy. Note that i have different gmail accounts associated with source and target GCP Org. Do i need to add user account from target GCP Org in source Org?

[DarwinVinoth]

You need to add the target organisation principal to the source organisation, and the target org does have access to the source project's billing account. 

Thanks, 
Darwin Vinoth.
Linkedin 

[dheerajpanyam]

Yes i added  target org principal to source Org with project mover, project creator, org admin. What about target org access to source project's billing account, i did not understand? I am assuming that once the project is moved to target or , billing account linked to the project will also transfer.

[DarwinVinoth]

This link give us the billing account related permissions, please go through that too. 

https://cloud.google.com/resource-manager/docs/project-migration-checklist 

Thanks, 
Darwin Vinoth.
Linkedin 

[dheerajpanyam]

Thanks @DarwinVinoth it is not clear which principal/identity  it is referring to, source or target. 

[dheerajpanyam]

One more interesting observation. I am looking at this page and it is missing the GCP console option (it has gcloud and API only), why is that? I see a "Move" option under manage resources page in GCP console, is this used to migrate projects within the org only?

[srinivasa12]

Hi @dheerajpanyam 

For migrating Project A from current GCP Organization to a new one, but the target Org isn’t showing up in the UI. we need a necessary roles (Org Admin, Project Mover, Billing Admin).

It appears the target Org is missing the required allowProjectMove policy for our source Org. Also, note that the billing account will not transfer, and we’ll need to manually reassign it post-migration, anyway this is not issue for you.

For Conformation, Kindly check the below Points.
1. Ensure IAM permissions on both orgs
2. Set allowProjectMove policy on target org
3. Retry moving project via Console or CLI
4. After move, update billing account if needed
5. Double-check IAM bindings after the move


Thanks, 
Srinivasa G

[dheerajpanyam]

Thanks @srinivasa12 for your reply. There is no Org policy named "allowProjectMove" rather there are a couple of org policies on source and destination Org as per this documentation that are already setup.

[dheerajpanyam · Accepted solution]

Turned out that i had to use the gcloud CLI  and it worked , the move option from the manage resources page in the GCP console did not show the target Org.