How to transfer a project from the organization to another organization

Scenario

We are game developers. Generally speaking, after receiving a case from a publisher, we will create a new project within our organization. After the project is completed and the contract expires, the project authority will be transferred back to the publisher.

The current situation we are encountering is that we don't know how to transfer the projects under our organization to the publisher's organization, and we are not sure whether this transfer is possible?

Operation

First of all, projects in an organization can be transferred to another organization, but projects in an organization cannot be moved out of the organization (to become projects without an organization). This will need to be handled by Google from the backend. If you have such needs, it is recommended that you contact an agent for assistance.

This article explains how to transfer projects between organizations.

IAM Permissions needed

The user executing the project transfer must

  1. Have the "Project Mover" or "Project Owner" role in the source organization (at the organization level) (make sure it is inherited to the project to be moved, otherwise it will be added additionally)
  2. Have the "Project Creator" role in the target organization (at the Organization level) (it does not matter if it is only Project Owner or Organization Administrator)

Steps

You need to enter the IAM > Organization Policies of the two organizations separately:

  1. In the Source Organization, select “Allow destinations for exported resources” > Edit
  • Applies to - Customize;
  • Policy enforcement - Merge with parent
  • Rules > ADD RULE -
    • Policy values - Custom;
    • Policy type - Allow;
  • Custom values - input
1under:organizations/[DESTINATION_ORGANIZATION_ID]
  • DONE > SAVE

2. In the target organization section, select Allow sources to import resources from > Edit

  • Apply to - Custom;
  • Policy Enforcement - Merge with Parent
  • Rules > Add new rule -
    • Policy Value - Custom;
    • Policy Type - Allow;
  • Custom value - input
1under:organizations/[SOURCE_ORGANIZATION_ID]
  • Done > Save

*Remind you to remember to [DESTINATION_ORGANIZATION_ID] and  [SOURCE_ORGANIZATION_ID] Change to real organization ID

Finally, open Cloud Shell and execute the following command to complete the transfer:

1$ gcloud beta projects move [SOURCE_PROJECT_ID] --organization [DESTINATION_ORGANIZATION_ID]

You can use the following command to confirm whether the project has been successfully relocated

1$ gcloud projects describe [PROJECT_ID]

Confirm whether the displayed ID is the ID of the target organization. If so, it means success!

Also, do not use all of the features listed below during project migration to ensure that the project does not behave incorrectly once it is removed from the current organization. If this project uses organizational policy please disable it. If the project resource is located under the folder hierarchy, move it to be directly under your organization resource.

  • Shared VPC
  • IAM Custom Roles
  • Organization Policy
  • Folders

reference document

[1] https://cloud.google.com/resource-manager/docs/perform-migration

Subscribe to Our Newsletters

Grow Your Competitive Edge With Our Insights.