Migrating from Classic folders to Modern folders possible problem

RPA Discussions
,
1

We are migrating an OnPrem from Classic Folders to Modern Folders - this is needed to upgrade the Orchestrator.
We have approached this by first upgrading a test instance - which went fine, now we are planning to upgrade the dev instance, but we have a question, we weren’t able to answer so far: if we migrate to Modern Folders on the dev Orchestrator platform and we are not able to also immediately migrate to modern folders the Orchestrator production instance (because we need to prepare the production upgrade more in-depth), what are the potential problems? Do packages of automations made on modern folders still work on classic folders if we need to deploy something in production?

2

Migration should be fair simple with the migration tool. You can find the specific details and answers to your concerns on the link below

Orchestrator - Migrating From Classic to Modern Folders

3

Yes - Migration is fairly simple. We have done that on the test Orchestrator, then we’ve upgraded Orchestrator to the 2024 version.
That is not my concern for the moment.
My problem is that I want to migrate the dev platform on which a lot of developers work, from classic folders to modern folders.
but the production platform won’t be upgraded immediately - it may take another week until we touch the production.

Do you think we might have issues when importing packages from the dev Orchestrator to the prod one, given that one will be on modern folders, while the other one is on classic folders?

My first though is no - there should be no problems - we will create everything (processes, triggers, assets) on production if a new deploy is needed, everything but the package - which will be imported from dev…

4

I don’t see any problem with that since packages are virtually unaffected. My best recommendation is to make a package inventory to ensure everything is transferred over, and a remediation plan in case something fails. I do recommend taking a second look at the article I shared as it highlights known issues, that information could be useful to draft a migration strategy.

It would be safe to draft a checklist of what you need.

Queues, Triggers, Assets, credentials
Packages
Create machine templates
Verify user access to folders

Environments will disappear, so it could be confusing

Whit all that in mind plus the steps you already took. I believe you’re prepared :slight_smile:

5

@GabrielaJ

Ideally from package perspective there is no difference in modern or classic folders…

unless you are using orchestrator folder path in your processes

as mentioned by @Botzilla there would not be any environments so the triggers might be little different

cheers