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.

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

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.

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:


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

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

What's next

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