Roll Back from Modern to Classic

I have a workflow created in Modern view, but the client framework is in the Classic view.
The challenge is when I’m importing/moving my Modern view workflows into the Classic view RE Framework the workflows are not recognized.

Need help in migrating the workflows from Modern view to Classic view.

Steps tried:

  1. save as the workflow into the Framework project directly- no luck
  2. Created a new workflow in the Framework and tried to copy the code from their into new workflow - was unable to copy
  3. changes the view of old workflow to Classic view and saved the code again - still no luck

Any help would be appreciated. :slight_smile:

I think you misunderstand why the workflows are not recognised.

Setting a project to classic or modern simply affects the filters in the activities pane and you can also set it so it shows all activities. Both modern and classic activities can be mixed and matched.

The issue you have is not to do with the project being in classic or modern.
Its most likely you are trying to import activities made with a higher version dependency than in the project you started it.

Check your dependencies, see where the versions differ and update your client framework to the relevant version, after that I think your workflow will be recognized.

Hi @mohammedsameer.ali1,
Please make sure that Compatibility is the same for both projects your issue some times appear when you working on Windows project and add sequence or activity to New Windows-Legacy compatibility project

Thanks Jon,
Missed to check this. Will try and update here if it resolves the issue.

Hi @mahmoud.zaky,
I thought I kept in Windows compatibility, will double check again, thanks :slight_smile:

Hello @mohammedsameer.ali1

Even if you are using the modern designer, there is a provision to enable the classic activities as well, from the filter button in the activity panel.

Also you can use both the activites in your workflow as well.


Hi @Jon_Smith,

I checked and both the projects are at their latest packages.

Hi @mahmoud.zaky,
You are right the codes are in different compatibility.
The framework provided by the client is in Windows Legacy mode. Is there a way to migrate from Windows to Windows Legacy or do I have to code everything again in Windows Legacy?

You cannot revert an already migrated project from Windows - Legacy to Windows back to Windows - Legacy.


In case you don’t want to lose your Windows - Legacy project, you need to select Create a new project.


As I suppose you unchecked the Create a new project option at migration → you lose the old Windows - Legacy project, and as you still need the Windows - Legacy project compatibility, you need to create a new Windows - Legacy project now.

Not advisable solution:

Check if in the past you published the old Windows - Legacy project in your Orchestrator. If yes, you can download its nupkg file, extract it and try to open the Main.xaml file.

Reference: Deprecation of the Windows-Legacy Compatibility

Hi @mohammedsameer.ali1,

In my previous experiments there are no official ways to convert a workflow from Windows version to Windows legacy version. In short, not backwards compatible. Windows Legacy version workflow will open in Windows version projects i.e., forwards compatibility.

In order to learn more today I did take a look at what the differences were on the xaml file level of Legacy vs Windows workflows.

Both workflow have the same content but the name spaces used have changed. I am not saying this will work, but you can give it a try.

  1. I would approach this problem by first using Visual Studio Code. Take your Windows version of one workflow and check legacy version of the same workflow (here you will need to recreate the logic as you cannot copy paste from windows to windows legacy projects in UiPath)

    How to compare:
    Visual Studio Code - is there a Compare feature like that plugin for Notepad ++? - Stack Overflow

    My test workflows result in these findings

  2. Now that you know what differences exists, you can go to your Windows version workflows and edit the text in .xaml to match the requirements of namespaces in Windows legacy. Anything which is not different can be retained.

    In other words, you are back-engineering. In my case (screenshot above) I can copy from Windows Legacy version (green) to the Windows version in red. This will convert the workflow (Main.xaml) to a legacy compatible version.

  3. Test on one workflow, and then open in the Windows legacy project, if all goes well then you avoid a lot of work.

  4. On the contrary if you do not have a lot of code, then I would suggest you do redo the logic in windows legacy. Such manipulations are tedious and time consuming.

I followed the first 3 steps and I could convert the Windows version of workflow to work in a Windows Legacy version of a project. So this is doable, it will just take some time to get things right. Hopefully, you do not have to redo this.

I will attach the files here for anyone interested to dive deeper.

  1. Main_Windows.xaml (from a Windows Project) :
    Main_Windows.xaml (3.9 KB)

  2. Main_Legacy.xaml (from a Windows-Legacy Project) :
    Main_Legacy.xaml (3.9 KB)

  3. Main-WindowsToWindowsLegacy.xaml (the converted workflow using the method mentioned) :
    Main_WindowsToWindowsLegacy.xaml (3.9 KB)

This is a long post, but I hope this helps you out.

As I know there is no way to revert back again but try the above two solutions maybe it will solve your case.

Thanks @jeevith, for the detailed explanation. Helped clear many queries.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.