Your Experience with Classic to Modern folder migration

I am looking for other experiences with migration from Classic to Modern folders especially for on premise Orchestrator environments. What is the deciding factor/s to migration from Classic to Modern folders? What were your challenges?
In our situation, we are concerned about not being able to migrate all of the queue transactions over to new queues. Per instructed, only “new” status transactions will be migrated.
In your opinion, what is the major advantage of Modern folders? Are there any issues or headaches with the migration or working with Modern folders? If the big advantage is categorizing your RPA processes, then what is your suggestion for laying out the folders? Organizational structure? Functional? Thank you in advance for your response.

3 Likes

Following. We were a pre-modern on-prem Orchestrator environment, and have now upgraded - so it’s a mishmash we have to straighten out.

As in mishmash, what do you mean? How to lay out the new Modern? What RPAs can move to the modern? What RPAs need more research before moving? ie queue data left behind?

Thank you for responding!

We had things in classic folders that are still in classic folders, but now have things in modern folders too. Mishmash resulting from the upgrade. I don’t know the answers to your questions. That’s why I’m following this post, I have the same questions.

Great! I hope this thread get’s some feedback that will benefit you.

Migrating to Modern, we will be challenged with our queue data i.e. cannot migrate all queue data to modern folders. Therefore, our bots will think certain transactions because the bots from the Modern folder cannot see the Classic folder queue. Boom! Duplicate transaction. We have an open question with UIPATH technical experts whether or not we can “link” classic and modern folders so that our bots can see both classic and modern queues.

Beyond this, it is a matter of understanding the characteristics and how much benefit it offers. Mostly, modern folders seems to provide more flexibility i.e. subfolders and the modern folders pretty much robot independent instead of one robot per folder. Stay tuned!

Tedious, but you could export what’s in the existing queue then import it into the new queue.

We would use Orchestrator Manager tool. You would only be able to migrate queue transactions in the “new” status. UIPATH hasn’t offered and I haven’t read anywhere where I can export and import everything in the queues. This is why we are seeing if it is possible linking Classic to Modern folders; therefore, no migration of transactions.

Export/Import is built in.

When viewing the items in a queue, click this icon
image

Upload is in the “3 dots” menu
image

The issue is that the downloaded file isn’t the right format to upload. You have to extract just the SpecificContent column from the downloaded spreadsheet then modify it from JSON to columns before you can import. It’s tedious, but it can be done. After once or twice you get quicker at it.

Thank you. I will review this further.

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 :smiley:

Much appreciated. Thank you for your feedback.