Migrate subscriptions to GCP

Google Cloud Platform (GCP) subscription migration allows partners to migrate existing subscriptions and create new GCP migrations on the marketplace.

To perform migration, you will require only Companies file. For User assignment of the GCP subscriptions, you will require Users file.

Additionally, you will need the following three mandatory columns for Google subscriptions migration.

Heading	Description
METADATA:accountIdentifier	The unique identifier of the account in Google.
ISV:projectId	The unique identifier of the subscription in Google.
ISV:subBillingAccountId	The unique identifier of the billing account ID in Google. Note: The subBillingAccountId must be in the format billingAccounts/<billingAccountID>. Example- billingAccounts/013BC7-1D6960-A065BB.
METADATA:entitlementName	Stores the resource name of the GCP subscription on Google. This field is required only when the new Channel Services is enabled for GCP.

note

In migration file, either projectId or subBillingAccountId has to be available for GCP migration.