Any impact if we dont convert legacy workflows to Windows?

Help Studio
, ,
1

Current have around 190++ process in production running using legacy workflow in UiPath studio 20.10.
Any impact if we dont convert them to upgrade to UiPath studio 23.10 and convert to windows workflow?

2

Hi @cheemun.wong
Welcome to UiPath,

As per my knowledge , Yes, there will be impacts. Performance may slow down, compatibility issues could arise with new features, legacy workflows might lose support in future updates, security patches may be missed, and maintenance could become harder.

For more follow link,

1 Like
3

The main impact you will face is that at some point, you will be compelled to update to a version of UiPath Studio that has removed support for these workflows, in the meantime you will not be able to leverage new features as they will not be designed to have Windows-Legacy support.

I strongly urge you to start migrating these processes, you need to do it at some point, its worth doing it as you go as you do any maintenance work on these projects and keep a list of them where you can do others when you have down time.

2 Likes
4

Hi @cheemun.wong,

In short, we will still be allowing editing of the Legacy projects for the foreseeable future, but only on the Studio LTS releases. For a variety of reasons already listed above, the earlier the migration is planned and executed, the easier it will be for you down the line.

And to touch on this a bit more:

You will find more details in this document:

To summarize the most important points:

  • The last version of Studio which supports the creation of Windows - Legacy projects is Studio 2024.10 LTS.
  • Editing Windows - Legacy projects will continue to be supported in upcoming LTS releases for the foreseeable future (but it isn’t and won’t be supported in the bi-monthly Studio releases, such as the one released last February, 25.0.161).
  • The activities have their own LTS timeline depending on each release; each activity package will soon drop the Windows - Legacy projects support, meaning:
    • You will not be able to install new versions of that activity package on your Legacy project; for example, System 25.2.x does not show up in Legacy projects anymore.
    • The latest LTS version of each activity package that still supported the Legacy projects will continue to receive support even beyond the current LTS term, as long as Studio keeps offering the option to edit your Legacy processes as well (which, once again, will remain an option for the foreseeable future).

I hope this clarifies the matter a bit :slight_smile:

4 Likes
5

Hi Guys,

Thanks for the input and information.
You guys are helpful.

Regards,
Chee Mun

6

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