Migrating to Windows 10 and Office 2016 with existing UiPath version 2016


#1

Installer(.exe or .msi):

Studio/Robot version:

Current behavior:

Good day,

We have a client that is using UiPath 2016 who are migrating to Windows 10 and Office 2016. Can they keep on using the current version or should they update to the latest version of UiPath?


#2

Hi @Herno

There are several benefits of upgrading the the newest UIPath platform, but the most important one is how much it evolved since the 2016 version. There is a bunch of new, awesome features that could be taken advantage of.

Naturally, there are several considerations here and you can probably guess that they relate to the compatibility issues. I would say that the workflows that were designed to work with the other versions of the software will require some significant rework. You will need to judge how much of maintenance will need to be done and whether you could combine it with adapting the workflows to run with newest version of UiPath software.

I would suggest a trial to see how the project will behave when opened in the newest version in the new environment and go from there.


#3

Hi @loginerror ,

it would be great if we have auto migration capability in UiPath so that it may not need more re work. as UiPath platform is updating quarterly, it would be difficult to do re work for all the existing projects every time we upgraded our platform.

regards,
pathrudu


#4

This is already in place - you can open projects created with earlier versions of UiPath in the newest version and they will be converted.

However, the issue here is of a different kind. If you change the software that you were automating, you might be required to redo at least the selectors, if not some of the logic (different menus, order of actions) :slight_smile:


#5

Hi @loginerror,

Great, thank you for the response!