Project Migration instructions

[jc123]

In https://cloud.google.com/resource-manager/docs/project-migration#assign_permissions, it says that roles/resourcemanager.projectIamAdmin, roles/resourcemanager.projectMover, and constraints/resourcemanager.allowedExportDestination should be set up on the parent resource and roles/orgpolicy.policyAdmin should be set up on the source organization.  If the source has no organization (no parent resource), should these be ignored or added to the project itself?

We're creating a billing account "offline" for the new organization by going directly to the rep instead of creating it ourselves. How do we associate this account with the new organization?

We're migrating a project with over 50 user accounts to a new organization. We're planning to use Cloud Identity Free.  Will this be problem because of the user limit?  Since these are consumer accounts, I figured that it shouldn't matter.

[alexmoore]

For your first question, yes you need these roles against the source project if it has no org.

To change a billing account associated with a project see this page: https://cloud.google.com/billing/docs/how-to/modify-project#change_the_billing_account_for_a_project

Regarding requesting additional users, please see this page: https://cloud.google.com/identity/pricing#free_edition 

[Clouds]

The project resource is the base-level organizing entity in a Google Cloud organization. Projects are created under organizations and can be placed under folders or the organization resource itself, forming the resource hierarchy. You may need to migrate projects between organizations due to acquisitions, regulatory requirements, and separation between business units, among other things.

You can use the Resource Manager API to move projects across organizations or to another place in the resource hierarchy of the current organization. The Resource Manager API also lets you roll back the migration, moving the project back to its original place in the resource hierarchy.