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 organizationresource into the hierarchy of an organization resource.

If you don't have theresourcemanager.organizations.get permission on theparent organization resource of the project, it's likely that your projectsdon't reflect as expected under the actual organization in theGoogle Cloud console. This can make it seem like the project is not associatedwith any organization resource.

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

gcloud

Run the following command:

gcloud projects describePROJECT_ID

ReplacePROJECT_ID with the ID of the project that you want tomigrate.

If theparent resource isnot displayed in the output, it confirmsthat the project is not associated with an organization resource.

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

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

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

The project resource is the base-level organizing entity in aGoogle Cloud organization resource. Projects are created underorganization resources, and can be placed under folders or the organizationresource itself, forming theresource hierarchy.You may need to migrate projects between organization resources due toacquisitions, 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 theproject 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 thischange in the Google Cloud console. For information about finding the currentdetails of a project, seeCreating 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 arenot transferred. The organization loses any inherited quotas.

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

Example

$gcloudalphaservicesquotalist--service=compute.googleapis.com--consumer=projects/workloadyee--filter="metric: compute.googleapis.com/cpus"...-defaultLimit:'600'dimensions:region:us-central1effectiveLimit:'650'...

What's next

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

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-18 UTC.