Orchestrator from classic to modern

Help Studio
1

hello everyone,

i should perform a migration between an orchestrator instance to a new automation suite. Coming from classic folder, somewhere I had read, but can’t find where, that before migrating it was necessary to migrate from classic to folder and then onto the new environment. Are you able to share the documentation?

Thank you

1 Like
2

Hi

Hope this helps
https://docs.uipath.com/orchestrator/standalone/2023.4/user-guide/migrating-from-classic-folders-to-modern-folders

To understand the basic difference between classic and modern

https://docs.uipath.com/orchestrator/standalone/2021.10/user-guide/classic-folders-vs-modern-folders

Migration tool

https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/using-the-migration-tool

Cheers @Singh7633

1 Like
3

@Singh7633

From classic to modern already provided in above comment

this is specifically for migration for automation suite

https://docs.uipath.com/automation-suite/automation-suite/2023.4/installation-guide/migration-options#:~:text=The%20full%20installation%20migration%20process,migrate%20other%20products%20and%20services.

cheers

1 Like
4

thanks for the answers, what I meant specifically is, I need to do a migration from standalone with classic folder to automation suite 2023.4. Where is it stated that you need to migrate from classic to modern in the standalone version first and then switch everything to automation suite?

5

@Singh7633

Classic folders have been deprecated…so in the nee version you wont see the classic folders at all…only modern folders are present

Please check this about depreciation

https://docs.uipath.com/overview/other/latest/overview/classic-folders-removal#

Cheers

6

yes, that is clear.

What I wanted to know is: since the new infrastructure will only have modern folders (since classic are deprecated), is it necessary to first migrate from classic to modern on the old platform and then migrate to the new one? This information, where is this reported?

Thank you

7

let me help to answer you.

I recommend no need to migrate to the old platform first. you need to set it again from the beginning with proper Organize. how → https://forum.uipath.com/t/organizing-your-uipath-orchestrator-for-better-management.

1 Like
8

don’t upgrade the old platform, ok.

Make, on the old platform, the upgrade from classic to modern folder before migrating to the new platform, should be done, correct?

Is this process mentioned anywhere on the documentation?

Thanks

9

I think you can not find the doc. this is based on my experiences.

but you need to make sure the version of your robot must be above 19.x. CMIIW

Cheers,

10

It’s not a hard requirement. Since the way that objects are organized in Modern folders are different from Classic folders, you will be reorganizing your robots and users by creating new objects anyway (e.g. folders, machine templates, user-folder assignments). Whether you create them in your standalone Orchestrator first, or create them directly in your new environment, makes no difference.

My suggestion would be that you just create in the new environment directly, there’s no point creating them in the existing environment unless you want to use it to do some testing before moving everything to the new environment.

Consider using the Orchestrator Manager to help with your migration: Orchestrator Manager - RPA Component | UiPath Marketplace | Overview