I’m currently evaluating the migration of our UiPath Orchestrator from an on-premise setup to the UiPath Automation Cloud, and I’d really appreciate insights from anyone who has gone through this process.
Specifically, I’d like to understand:
Pricing:
How does the cost structure of Automation Cloud compare to maintaining Orchestrator on-premise?
Are there any hidden or additional costs (licenses, storage, user access, etc.) I should keep in mind?
Risks/Challenges:
What are the main risks when moving from on-premise to cloud (e.g., downtime, data migration issues, security concerns)?
How did you mitigate these risks?
Migration Plan:
What’s a good step-by-step approach or best practice for planning the migration?
Should I run both on-premise and cloud environments in parallel for a transition period?
Any official documentation or community-shared checklists would be great to review.
If you’ve already done this migration, I’d love to hear about your lessons learned. My main goal is to ensure a smooth transition while minimizing disruption for our bots and users.
However, In my view, best approach would be to engage with your UiPath customer representative, get a quote and then also engage your organization security team and network/ops team to understand the challenges this move can pose as this move is really specific to organization’s internal architecture and security practices in place. A decision regarding whether you would continue using your internal VMs for unattended automations or move to UiPath supported ones as well is also to be considered.
It’s not a quick decision, not one-size-fits-all kind scenario and probably the difficult one too. It took us a lot of time to first get approval from our org to even consider moving to cloud- you will have to prepare a business case for same.
Next step would be to engage UiPath and other internal teams like I shared above.
Oh yes, we did need their support regularly to go through challenges/ any concerns along the way.
We had a regular meetings with the UiPath team and our internal teams for months during the transition period.
Also, when it comes to pricing of the model/licensing you pick also depends greatly on your negotiation skills
We ran both on-premise and cloud parallel during the transition period, and did a phased migration. First migration of only test environment to regression test all the processes, then prod one and finally our development environment.
And this order is very important to consider, as for us, we were in 2023 version for on-premise and for cloud we were moving to 2024 version. Now we wanted to ensure while we are still testing our processes on cloud, we do have the ability for any fixes/enhancements in prod, hence dev env was the last one to move to cloud. As changes made from a higher version of studio deployed on a lower version of orchestrator creates problems..
