Conversion of Windows legacy projects

Help Activities
, ,
1

Hi,

We are having processes developed with WindowsLegacy framework and there has been notification to migrate to Windows. So, for this wanted your inputs to understand below points.

Do we also need to migrate already working prodcution processes with Window Legacy?
What is impact and what we need to take care before choosing click convert to Windows option?
Any specific software requirements needed for Windows projects?
Best approach for this migration?

Thanks!

2

Hi @Rama_Thota,

How to convert legacy projects to Windows, please refer below links for detailed info:

Below shares 2 approaches to convert the project (I would suggest going with the 1st method but sharing just in case):

Follow below one, incase the conversion pop-up doesn’t show up in studio when you open your legacy project:

Last but not the least, follow below tutorial, you will be able to find almost everything you would need to understand wrt conversion:

See below for info regarding support for legacy projects:

The image contains a notice explaining that Windows - Legacy projects will not receive new features and instructions for creating Windows - Legacy projects, encouraging the use of the Windows compatibility for new projects to access new features. (Captioned by AI)
The image contains a notice explaining that Windows - Legacy projects will not receive new features and instructions for creating Windows - Legacy projects, encouraging the use of the Windows compatibility for new projects to access new features. (Captioned by AI)1170×436 61.1 KB

One Tip: Please take a backup of your project before converting it to windows. As once conversion is done, few activities may fall out of place which are no longer supported/offered. Having the backup, you will be able to draw a comparison between the legacy and windows project to know which activities fell off and then you can create new (windows supported) activity versions for those.

Hope this helps.

Regards
Sonali

3

Hi,

Although next Enterprise version has not been released yet, I think that’s very possible.
It may be better to migrate all the project by around Oct 2027 which is extended support expired date of 2024.10.

What is impact and what we need to take care before choosing click convert to Windows option?

If you use lower version activity packages, they will upgrade to the higher version. This means robot behavior may change. (And it may be necessary to test them) The following document also helps you.

Any specific software requirements needed for Windows projects?

.net core (.net 5/6/8) is required. (Basically UiPath installer will install it.

Best approach for this migration?

It depends on the characteristics of your automation process. If your automation process is mission critical, testing is recommended before deploying production environment.
And it may be better to investigate behavior difference b/w Windows-Legacy and Windows project against each system in advance.

FYI, the following may also help you when troubleshooting.

Regards,

1 Like