Stay organized with collections
Save and categorize content based on your preferences.
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 from one organization to another organization
resource, see the detailed project migration checklist.
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:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[],[],null,["# Migrating projects between organization resources\n\nThis guide explains the following migration scenarios:\n\n- Migration of projects from one organization to another organization resource.\n- Migration of projects that were created with no associated organization resource into the hierarchy of an organization resource.\n\nIf you don't have the `resourcemanager.organizations.get` permission on the\nparent organization resource of the project, it's likely that your projects\ndon't reflect as expected under the actual organization in the\nGoogle Cloud console. This can make it seem like the project is not associated\nwith any organization resource.\n\nTo determine whether the project is associated with an organization resource, do\nthe following: \n\n### gcloud\n\nRun the following command: \n\n```\ngcloud projects describe PROJECT_ID\n```\n\nReplace \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e with the ID of the project that you want to\nmigrate.\n\nIf the **parent** resource is *not* displayed in the output, it confirms\nthat the project is not associated with an organization resource.\n\nIf the **parent** resource (folder or organization resource) is displayed in\nthe output, it confirms that the project is associated with an organization\nresource.\n\nFor more details related to migrating projects, see the following:\n\n- If you want to migrate projects that were created with no associated organization, see [Migrate projects with no organization resource](/resource-manager/docs/handle-special-cases#migrating_projects_no_org).\n- If you want to migrate projects from one organization to another organization resource, see the detailed [project migration checklist](/resource-manager/docs/project-migration-checklist).\n\n| **Note:** If you want to transfer Google Workspace domains between organization resources, contact your Support representative.\n\nThe project resource is the base-level organizing entity in a\nGoogle Cloud organization resource. Projects are created under\norganization resources, and can be placed under folders or the organization\nresource itself, forming the\n[resource hierarchy](/resource-manager/docs/cloud-platform-resource-hierarchy).\nYou may need to migrate projects between organization resources due to\nacquisitions, regulatory requirements, and separation between business units,\namong other things.\n\nYou can use the Resource Manager API to migrate projects between organization resources.\nThe Resource Manager API also lets you roll back the migration, moving the\nproject back to its original place in the resource hierarchy.\n| **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](/resource-manager/docs/creating-managing-projects#get_an_existing_project).\n\nQuota impact\n------------\n\nIf you have quotas defined at a certain resource level, the following aspects are applied after migration:\n\n- Any quotas defined at the project level remain unchanged.\n- Any quotas defined at the organization resource level are *not* transferred. The organization loses any inherited quotas.\n\nThe following pages can be used to determine what quotas are applied to an organization resource:\n\n- [View and manage quotas](/docs/quotas/view-manage)\n- [List quotas with gcloud](/sdk/gcloud/reference/alpha/services/quota/list)\n- [List quotas with RPC](/service-usage/docs/reference/rest/v1beta1/services.consumerQuotaMetrics/list)\n- [Example quota bucket](/service-usage/docs/reference/rest/v1beta1/services.consumerQuotaMetrics.limits#quotabucket)\n\n### Example\n\n $ gcloud alpha services quota list --service=compute.googleapis.com --consumer=projects/workloadyee --filter=\"metric: compute.googleapis.com/cpus\"\n\n ...\n - defaultLimit: '600'\n dimensions:\n region: us-central1\n effectiveLimit: '650'\n ...\n\nWhat's next\n-----------\n\nTo learn about the tasks involved in migrating projects, see the [project migration checklist](/resource-manager/docs/project-migration-checklist)."]]
