@Alistair_Moffat_UK (Alistair Moffat) posted a new topic, subject "Community Edition Compatability". It read:

   Hi All,
    
    Is it easy enough to upgrade from a community version of UiPath to the Enterprise version ?
    
    Many Thanks in Advance

To which @Palaniyappan (Forum Leader) replied

    Hi
    
    Welcome to uipath forum
    
    Have a view on this thread for more ideas on migrating from community edition to enterprise edition
    
    Versioning Issues on Upgrading Community Edition to Enterprise Edition Help
    
    > Currently, we are developing Robots using UiPath Community Edition 2019.7.0 and plan to update to Enterprise edition. Will the Enterprise edition also be updated to v2019.7.0 or to any other versions? The above issues or clarification has been raised since UiPath does not support Forward/Backward compatibility 
    
    Have a view on this compatibility matrix for more idea
    
    Overview
    
    ### Compatibility matrix
    
    Standalone The below matrix provides information about the interoperability between Orchestrator and Robot and Studio, Test Manager, AI CenterTM, Insights, and Action Center according to their versions and Orchestrator's delivery model. Patches are...
    
    Backward and forward compatibility also matters when migrating between different edition and different version
    
    UiPath Installation and Upgrade
    
    ### Backward and Forward Compatibility
    
    UiPath Approach Activity Packages Activity package versions are independent of Studio, Robot, or Orchestrator versions, except for Orchestrator activities. For example, the Start Job activity, introduced in v2018.1, only works on v2018.1 Robots or...
    
    Cheers @Alistair_Moffat_UK

After which, @kirankumar.mahanthi1 (Kirankumar Mahanthi) added

    Hi @Alistair_Moffat_UK ,
    
    in terms of development it is easy to migrate from community studio to Enterprise studio. better to migrate from community to LTS enterprise studio.
    
    Please request 60 day Enterprise trail license from UiPath and test your work flows developed by community in Enterprise trail version and make sure that you are using the same package versions (it will automatically detect the version of package from project.json but make sure that we are using same package versions) to avoid un necessary errors in the work flows.
    
    enterprise UiPath software always comes with the MSI file so by default it will come with the service mode. run all your process in enterprise version to make sure that everything is working fine.
    
    Once everything good with all your processes go and opt for enterprise license for development(studio license) and bots from UiPath.
    
    Hardest part is migrating from community orchestrator to enterprise orchestrator. Planning to go for one prem or cloud orchestrator for your enterprise. thanks.
    
    And also please refer the post from @Palaniyappan related to compatibility. it will come into picture if we are using different versions between community and enterprise.
    
    Could you pls share your valuable thoughts on this Tim @codemonkee it would be very helpful for others who are wish to migrate from community to enterprise. thanks in advance.

Then @codemonkee (Tim) said

    Alistair_Moffat_UK:
    
    > from a community version of UiPath to the Enterprise version ?
    
    It's not clear from the OP on what version is meant by “Enterprise Version” as you can have a Private Orchestrator or Licensed in the Cloud. (And of course the private installation can be on bare metal or virtualized on-prem or in your own cloud environment)
    
    If the intent is to maintain your Orchestrator in the Cloud managed by UiPath it is as simple as paying for and updating the license.
    
    If you are looking to migrate from Cloud to Private, it is probably worth asking Support directly if they have any Migration Tools to assist (depending on how much you have to migrate). As they do provide a Migration Tool for Private Standalone Orchestrator to Cloud as well as a Migration Tool for Automation Suite
    
    Depending on your timing, I would setup the closest major version to what you are using in the Community Cloud as you can to minimize any possible backwards/forwards compatibility issues that may come up and/or review the changes and make the decision if you want to setup the next FTS version or the previous LTS. You could always deploy the latest version available even if it is an FTS and than upgrade to next year's LTS when it comes out. You can see the Product Lifecycles for more information and note that Automation Cloud ensures backwards compatibility with the three latest enterprise Robots/Studio Releases.
    
    There is also a check list for Manual Migrations from Private to Automation Cloud, so the general steps you could follow going in the reverse.
    
    And lastly there is the Orchestrator Manager which is a UiPath Studio Project that you run locally. It is unable to cover all use cases due to technical limitations (e.g. User/Robot Specific Asset Credentials), but could probably get you most the way there. I would strongly recommend reviewing the included PDF in the download if you entertain the usage of this tool.
    
    In the end Orchestrator Manager is using a combination of direct actions as a Robot or leveraging the Orchestrator API, so if you are familiar you could do most of the same using your own scripts against the API but again with some limitations such as Credentials not being exposed via API which is why the Orchestrator Manager has a configuration flag to get Global Credentials via authenticated Robot.
    
    If you don't have that many entities to deal with / reconfigure, it would probably be quickest to do a manual migration and/or recreating what is needed.

After which, @kirankumar.mahanthi1 (Kirankumar Mahanthi) added

    Thank you so much Tim @codemonkee for your valuable response.

After which, @system (system) added

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


{'source': 'discourse', 'url': 'https://forum.uipath.com/t/community-edition-compatability/395657', 'title': 'Community Edition Compatability', 'views': 482, 'has_accepted_answer': True, 'word_count': 848, 'like_count': 7, 'reply_count': 2, 'participant_count': 4, 'posts': 6, 'tags': '', 'author': '@Alistair_Moffat_UK (Alistair Moffat)', 'participants': '@Alistair_Moffat_UK (Alistair Moffat), @Palaniyappan (Forum Leader), @kirankumar.mahanthi1 (Kirankumar Mahanthi), @codemonkee (Tim), @system (system)', 'image_url': [None], 'created_at': '2022-01-31T17:04:41.792Z', 'last_posted_at': '2022-02-04T01:40:55.100Z'}