Migrating projects between organizations on Google Cloud

[alberane]

Hello,

I'm looking for help migrating a project from one organization to another on Google Cloud.

I would appreciate any help you can provide.

Thanks,
Alberane

[lawrencenelson]

Hi @alberane,

Welcome to the Google Cloud Community!

This documentation explains how o migrate projects between organizations for the following 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.

Additionally, this Stack Overflow thread provides a step-by-step guide on how you can accomplish this. 

You can always contact Google Cloud Support to further look into your case. Thank you!

[Alexander0]

Migrating a project from one organization to another in Google Cloud involves transferring the project's resources, configuration, and policies to the destination organization. This process can be done manually or using the Resource Manager API.

Manual Migration:

1. Identify Dependencies: Determine if the project has any dependencies, such as shared VPC resources or custom roles, that may affect the migration.

2. Create Destination Organization: If the destination organization doesn't exist, create it using the Google Cloud console or the Resource Manager API.

3. Export Source Project: Export the source project's resources, configuration, and policies using the Resource Manager API or the Google Cloud CLI.

4. Import Project to Destination: Import the exported project into the destination organization using the Resource Manager API or the Google Cloud CLI.

API-Based Migration:

1. Create Destination Folder: Create a folder in the destination organization where the migrated project will reside.

2. Enable API Access: Enable the appropriate API access scopes for the user performing the migration.

3. Issue Migration Requests: Use the Resource Manager API to issue migration requests for the source project and its resources.

4. Monitor Migration Progress: Monitor the migration status using the Resource Manager API or the Google Cloud console.

Considerations:

1. Permissions: Ensure the user performing the migration has the necessary permissions to access both the source and destination organizations.

2. Testing: Thoroughly test the migrated project to ensure all resources, configuration, and policies are functioning correctly.

3. Rollback: Make sure you have a rollback plan in case of any issues during the migration.

4. Documentation: Document the migration process for future reference.

5. Third-Party Tools: Consider using third-party tools that automate migration, especially for large or complex projects such as ShareGate, Gs Richcopy 360 and GoodSync.

Migrating a project between organizations can be complex, and careful planning and execution are essential to ensure a smooth transition.

[palladius]

I've written an article on this: https://medium.com/google-cloud/how-to-migrate-projects-across-organizations-c7e254ab90af

If you're still stuck please explain how and I'll try to address those issues.

[ricc]

Have you tried following this article? 

https://medium.com/google-cloud/how-to-migrate-projects-across-organizations-c7e254ab90af

Does it help? 

Riccardo