Google Cloud Platform migration instructions

To migrate your Google Cloud Platform(GCP) instance, follow the steps below:

1. Upgrade your on-premises environment to 2023.4 or skip this step if you are already in version 20223.4 or later. More details are available in step one from Migrating from On-premises to Cloud.
2. Create a new SQL Server in your GCP account.
3. In your cloud environment, create a new tenant (it'll be referred to as the cloud tenant from this point onward). Take note of the tenant key as it will be needed later on.
4. Run the UiPath’s Orchestrator Migration Tool to migrate Orchestrator data from on-premises tenant to the cloud tenant. After this step is complete, navigate to the Orchestrator page and verify that all folders, including classic folders, machines, and queue are migrated to cloud.
   Note: If some entities (Processes, Queues, etc.) are missing on cloud, you should manually create them with your on-premises names. If you don’t create missing entities, it will be assumed they have been deleted and proceed accordingly.
5. Migrate your Insights Datatbase (DB) to the new SQL Server. You can do this using the Import/Export functionality of SQL Server. It's required to have migrated at least the following 7 tables:
   • dbo.__MigrationHistory
   • dbo.JobEvents
   • dbo.Jobs
   • dbo.Jobs
   • dbo.QueueItemEvents
   • dbo.QueueItems
   • dbo.RobotLogs
   • dbo.Tenants
   Note: Make sure the Collation of the DB is Latin1_General_CI_AS.
6. Connect to your DB and verify that the required tables are present.
7. Ask UiPath for a list of IP addresses to allow list. Go to Authorized networks from Connection section to allow list these IP addreses.
8. Send a migration request via Customer Portal with the following information:
   • The AzureSQL connection string.
   • The TenantKey of the on-premises tenant.
   • The TenantKey of the cloud tenant.
   • The Tenant Name of the cloud tenant
   • The Organization Name of the cloud environment.
   • The region of the cloud tenant.
   Note: Insights service downtime is expected until the migration is completed by UiPath Support team. Based on the ticket volume, the migration can take approx two weeks to complete from end to end.