UiPath Cloud Migration Tool Docs:
https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/using-the-migration-tool
0:00 Intro
0:09 Background
1:08 Agenda
1:40 Why cloud migration
2:29 Three types of migration
3:18 Migration Strategy
10:00 Cloud Migration Tool
10:50 Orchestrator Manager
11:17 Prerequisites
12:05 Insights Migration
14:41 Automation Hub Migration
15:08 AI Center Migration
16:45 Lessons Learned
🍺 If you've learned something new from this video, buy me a coffee to support this channel =)
https://bmc.link/jennyman
Hey everyone, today we’re going to talk about cloud migration. There’s been a continuous influx of cloud migration projects coming to the PS team, and it’s quite different from your typical RPA implementation projects.
With cloud migration, we’re not necessarily building new things, but we’re helping clients move to the cloud, maybe from on-prem, or from another cloud, or from automation suite, and we have special tools for doing that. Agenda: Today we’re going to talk about: why cloud migration, what are the different types of migration, what are the tools we typically use, the overall strategy, and also, besides the orchestrator, what are other common UiPath products we would migrate data for, including Insights, Automation Hub, AI Center. And, what have been some lessons learned from cloud migration, and a list of resources and people you can go to if you have additional questions on specific aspects of cloud migration.
There’re 3 types of migration. 1. Customer moving from on-prem to cloud, which is probably over 95% of our migration projects right now.2. From one cloud to another cloud (maybe due to corporate restructuring, or business acquisition, they’re retiring one cloud and moving everything into another). 3. Suite to cloud. They already have the automation suite, but they want to move to our cloud. Let's talk about the overall strategy and the process.
We have a migration questionnaire that gets sent out to customers during the scoping and estimating stage, and it looks like this.
They would fill it out, come back to us to understand the level of effort. From there, the SOW gets signed, and typically an SA and a PM get assigned to work with the customer on the migration. And we use this migration tracker to track the status of the migration over the course of the project.
In terms of timeline, I’ve done migration projects that range from, anywhere from 4 weeks to 3 months. It depends on the availability of the customer, how long it takes to get access to their environments so that we can run the migration tools. It could also depend on the readiness of their environment. It also depends on how many tenants they’re migrating. Some customers just have 1 tenant, some have 6. Some customers just have 15 processes to migrate, some have 300. the migration questionnaire helps us understand the size of the data that needs to be migrated, and the scope of the effort a little bit better.
There are two migration tools we use: cloud migration tool and orchestrator manager.
In terms of when to use which one, we try to use the cloud migration tool whenever possible, because it’s faster. It’s for the most part a click of a button after you fulfill the prerequisites. But you can only use the cloud migration tool if you are going from on-prem to cloud, not from cloud to cloud. And also there are a list of excluded entities that the cloud migration tool does not migrate. To fill those gaps, the orchestrator manager can be used. If you’re doing an overall lift and shift at once, the cloud migration tool is perfect for that. But the orchestrator manager gives you a bit more control and flexibility, in that you can migrate incrementally. You can pick specific entities that you want to migrate. It does give you more control, but also requires a bit more set-up and runtime. A lot of times, the customer just wants to migrate everything anyway, so the cloud migration tool is the first choice of tooling. But the orchestrator manager is definitely useful in various edge cases where the cloud migration tool alone does not suffice.
For the cloud migration tool, you use the tool to export the data from your source tenant, then import the data to your target cloud tenant, do any manual clean-up as needed, and then repeat for the next tenant.
For the orchestrator manager, you extract the entities (meaning assets, packages, processes, queues, etc.), then map them to your target as needed, then load the entities to your target tenant, then repeat for each tenant.
In both cases, we’re making a copy of the source, so we are not erasing or replacing anything in the source. Also, there may be some entities that don’t get migrated by the tools, so you’ll need to manually migrate them afterwards. For example, users, roles, and settings.
#uipathtutorial #uipathdeveloper #uipathtraining #uipathtutorial #uipathcommunity #cloudmigration