This checklist will help you to move projects between organizations. The checklist below contains a list of the major tasks involved in moving a project between organizations, brief instructions for each step, and a link to more information.
Click on a checklist item to see more information and click the box when you complete a task.
Create a plan to make sure that any potential impacts are mitigated during your project move. To help inform your plan, use the Move Analysis API to get a detailed breakdown of blockers for the project move.
For more information, see Create a migration plan.
For a list of special cases and how to handle them, see Handling special cases.
You can get these permissions by acquiring the following roles:
Project Mover (
roles/resourcemanager.projectMover) on the project you want to move and its parent resource.
Project Creator (
roles/resourcemanager.projectCreator) on the destination folder or organization.
Organization Policy Admin (
roles/orgpolicy.policyAdmin) on both the source and destination organizations.
For more details about the roles and permissions you need, see Assign permissions.
constraints/resourcemanager.allowedExportDestinationsconstraint, which defines the organizations to which the project can be moved.
On the destination side, you must set the
constraints/resourcemanager.allowedImportSources constraint that defines the
organizations from which projects can be imported.
If either of these constraints are not properly set, the migration will fail
For more information about these organization policy constraints, see Configure organization policies.
gcloud beta projects move
gcloudcommand-line tool command, or the
projects.update()REST API method to perform the move.
For more details about migrating your project, see Perform the migration.