Migrating projects between organization resources

This guide explains the following migration scenarios:

• Migration of projects from one organization to another organization resource.
• Migration of projects that were created with no associated organization resource into the hierarchy of an organization resource.

If you don't have the resourcemanager.organizations.get permission on the parent organization resource of the project, it's likely that your projects don't reflect as expected under the actual organization in the Google Cloud console. This can make it seem like the project is not associated with any organization resource.

To determine whether the project is associated with an organization resource, do the following:

gcloud

Run the following command:

gcloud projects describe PROJECT_ID

Replace PROJECT_ID with the ID of the project that you want to migrate.

If the parent resource is not displayed in the output, it confirms that the project is not associated with an organization resource.

If the parent resource (folder or organization resource) is displayed in the output, it confirms that the project is associated with an organization resource.

For more details related to migrating projects, see the following:

• If you want to migrate projects that were created with no associated organization, see Migrate projects with no organization resource.
• If you want to migrate projects from one organization to another organization resource, see the detailed project migration checklist.

Note: If you want to transfer Google Workspace domains between organization resources, contact your Support representative.

The project resource is the base-level organizing entity in a Google Cloud organization resource. Projects are created under organization resources, and can be placed under folders or the organization resource itself, forming the resource hierarchy. You may need to migrate projects between organization resources due to acquisitions, regulatory requirements, and separation between business units, among other things.

You can use the Resource Manager API to migrate projects between organization resources. The Resource Manager API also lets you roll back the migration, moving the project back to its original place in the resource hierarchy.

Note: It generally takes less than a minute for the project migration to complete. After migrating a project between organization resources, it may take several minutes to reflect this change in the Google Cloud console. For information about finding the current details of a project, see Creating and managing projects.

Quota impact

If you have quotas defined at a certain resource level, the following aspects are applied after migration:

• Any quotas defined at the project level remain unchanged.
• Any quotas defined at the organization resource level are not transferred. The organization loses any inherited quotas.

The following pages can be used to determine what quotas are applied to an organization resource:

• What are quotas?
• List quotas with gcloud
• List quotas with RPC
• Example quota bucket

Example

$ gcloud alpha services quota list --service=compute.googleapis.com --consumer=projects/workloadyee --filter="metric: compute.googleapis.com/cpus"

...
  - defaultLimit: '600'
    dimensions:
      region: us-central1
    effectiveLimit: '650'
...

What's next

To learn about the tasks involved in migrating projects, see the project migration checklist.