This is something I am just starting to look at myself and what I am looking at is
Potential options include
- Manipulating the database records (This most likely is NOT supported by UiPath)
- Manual Steps via using Web UI, one entity at a time
- Create script [PowerShell?] to move entity types in bulk
- Orchestrator Manager - Published by UiPath Orchestrator Manager - RPA Component | UiPath Marketplace Has some basic functionality, may not cover all use cases.
The biggest challenge for me with the number of Processes, Assets, etc. is User/Robot Asset Credentials due to the following and not so much of a challenge but an annoyance that I’ll have to recreate these credentials / set their value. If you aren’t into your own scripting, I’d probably look at the Orchestrator Manager as it has a configuration property to tell it to create those credentials with a single space value so at least you have a placeholder for the Asset / User.
- REST API will not provide the credential value
- Fetching of Global Asset Credential Values must be done by a Robot that has access to Folder the asset is in.
- User/Robot specific Credentials can only be fetched by that User/Robot.
Orchestrator Manager does most of its work via API, but in the case of Asset Credentials, it can be configured to use the Robot running the job to fetch the Credential values, but you still have the challenge of User/Robot specific Credentials.
Regarding Processes:
In order for Processes to support all the features of Modern Folders they must use UiPath.System.Activities 19.10.1 or higher.
I’m personally less concerned about the queue items, they are easily fetched via API, Database, Export of WebUI, Workflow, etc. Most likely will have the Classic Entities complete processing of any existing items in the Classic Folder and all new work will be pushed to the Modern Folder.
We don’t need the historical queue items once they have been processed in any capacity. We do general maintenance daily that deleted various records from the database including Queue Items after they are a certain age in order to keep the Database size in check. Any historical reporting is done outside of Orchestrator using something like Splunk, Snowflake, Insights, etc.
The Orchestrator Manager Manual.pdf
provided in the Orchestrator Manager download has a good overview of handling the Migration from Classic to Modern Folders and also a couple different structures that can be used.
However you do the migration, you’ll want to double check a couple things
- Deployed packages that use UiPath.System.Activities 19.10.1 or higher (Not a hard requirement)
- For each unattended Robot in a Classic Folder, an equivalent User should be created referencing the same username along with appropriate permissions are provided to the new user.
^^ Probably isn’t something I’ll continue to look at over the next couple weeks, but is on my roadmap to sort out in January as Classic Folders are deprecated with a scheduled deprecation date of Oct 2022, and I’d like to get it out of the way before we upgrade from 2020.10 to 2021.10 as well I am already in the process of migrating Robot and Asset credentials from Orchestrator to an External Credential Provider, so I’d rather only do it once