Migrating from On-premises to Cloud

Note: This tool is designed only for data migration.

The on-premises to cloud migration tool isn't intended for self-service. UiPath Support and Insights Engineering will manage the execution of this tool on your behalf. Before that, you need to complete the following pre-migration steps and provide the necessary information outlined in step seven to ease the tool's execution.

1. Prepare the Insights platform for migration based on your migration needs.

   Version	Only Insights data is needed	Insighta data and dashboards are needed (ROI values and custom variables are not needed)	Insights data, dashboards, ROI values, and custom variables are needed
   2022.4 and below	Clone and upgrade the Insights database without updating the Insights platform or Orchetrator	Upgrade Insights and Orchestrator to the latest version	Upgrade Insights and Orchestrator to the latest version
   2023.4	No action needed	No action needed	No action needed
   2023.10	No action needed	No action needed	No action needed
   2024.10	No action needed	No action needed	No action needed

   Note:

   To migrate the dashboard from on-premises to cloud, you have to use Dashboard Import/Export option which is available in the following versions:

   • 2023.4 - Base Insights data model (You can't migrate custom variables or ROI dashboards.)
   • 2023.10 - You can migrate the Base Insights data model and custom variable/ROI dashboards.
   • 2024.10 - You can migrate the Base Insights data model and custom variable/ROI dashboards.
2. Upgrade your on-premises environment to the latest version. (You can skip this step if you are already in version 2023.4 or later).
   • Option 1: Full upgrade. Use the: Insights - Upgrading documentation to find more.
   • Option 2: Clone and upgrade Insights DB. Find out more in: Upgrade using cloned database.
3. Execute the SQL script to verify Insights DB and share the results with the Support team. You should fix any issues detected by this script before moving to the next step.
4. Create an AzureSql with collate Latin_1_General_CI_AS. This can be done using the following command: create database <your DB name> collate Latin1_General_CI_AS;
5. 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.
6. 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.
7. Migrate data from the on-premises tenant to the new AzureSql DB using Microsoft’s Data Migration Assistant (DMA). You can install Microsoft DMA on the on-premises machine. You are required to migrate the following seven tables.:
   • dbo.JobEvents
   • dbo.Jobs
   • dbo.QueueItemEvents
   • dbo.QueueItems
   • dbo.RobotLogs
   • dbo.Tenants
   • dbo.__MigrationHistory
   Note: Microsoft’s DMA isn't the only tool that can transfer data to AzureSql. There are alternatives and it's ok to use any tool that you have access to.
8. Execute this SQL script to verify Insights DB and share the results with the Insights team: Insights DB verification script. You should fix any issues detected by this script before moving to the next step.
9. 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.
10. If you want to migrate dashboards, export and import the dashboards. For more information, check the page.