Moving a project  |  Resource Manager Documentation  |  Google Cloud (2023)

• Home
• Docs
• Resource Manager
• Documentation
• Guides

This guide explains how to move a project within your organization.

The project resource is the base-level organizing entity in aGoogle Cloud organization. Projects are createdunder organizations, and can be placed under folders or the organizationresource itself, forming theresource hierarchy. You can move projectresources within your resource hierarchy, but should consider the policyimplications of the move before you make it.

When you move a project, any Identity and Access Management policies or organization policies thatare directly attached will move with it. However, a project in your resourcehierarchy is also affected by the policies that it inherits from parentresources. If a project inherits an IAM role that provides userspermission to use a particular service, users will not have access to thatservice at the destination unless it would inherit the permission at thedestination as well.

For example, consider a service account has the Storage Object Creatorrole bound to a user at Folder A. The service account has permissions to uploaddata to Cloud Storage in any project in Folder A. If you moved one of theseprojects Folder B, which does not have the same inherited permissions, theservice account for that project loses the ability to upload data, resulting ina service outage.

These same considerations apply if organization policies are defined at thesource and destination folders. Like IAM policies, organizationpolicies are inherited. Consequently, you must ensure that your organizationpolicies are consistent between source and destination folders.

To learn more about organization policies, seeIntroduction to the organization Policy Service.

To move a project, you need the Project Mover IAM role(roles/resourcemanager.projectMover) on both the source folder and thedestination folder. If the resource is not in a folder, you need this role onthe organization node.

These roles give you the following required permissions:

• resourcemanager.projects.update on the project
• If the resource is in a folder: resourcemanager.projects.move on thesource folder and the destination
• If the resource is not in a folder: resourcemanager.projects.move on theorganization node

You can also gain these permissions with customroles, or other predefined roles.

gcloud beta projects move PROJECT_ID \--DESTINATION_TYPE DESTINATION_ID

POST https://cloudresourcemanager.googleapis.com/v3/{name=PROJECT_NAME}:move{ "destinationParent": DESTINATION_PARENT}