UiPath Community - Orchestrator Upgrade and Migration Strategies.pptx

Editor's Notes

• #6: Just to make the delivery options, and capabilities of each a little clearer, we have this chart. It shows clearly how Automation Cloud and Automation Suite enable you to get the most capability from UiPath – both in terms of the integrated products included and what we call “Unified Admin” – built-in technical capabilities that maximize enterprise capability. We operate a “cloud-first, customer choice” policy, which means that the absolute most capability is available first as SaaS in Automation Cloud. Following that, in a future on-prem release we bring those new capabilities into Automation Suite, for customers who cannot go with Automation Cloud for policy or other reasons. Both Automation Cloud and Automation Suite are licensed with UiPath Flex SKU’s, which, as the name implies, allow you to run either SaaS or Self-hosted, and move between them as you wish. Perhaps less obviously, but very importantly though, Automation Cloud and Automation Suite have Unified Admin. This is a value multiplier across all those included products and you see some of the highlights on the right. But broadly there are two ways you get additional value: First: There are lots of additional features for operating efficiently in an enterprise environment. Second: There are additional integrations between the products, and in some cases additional features within the products. We expect this differentiation between standalone and Cloud or Suite versions of products to continue. So going to Automation Cloud or Automation Suite isn’t just about getting all the products a different way. It’s much more. The MSI Standalone column shows you what we have available as our standalone, RPA centric products. As you can see, this is quite a subset of the full capability, and does not include products like UiPath Apps and Automation Ops. They also don’t include the additional capabilities across and within the products (like Insights offering analytics of additional areas across the platform), or significant additional tooling to deliver, govern and operate the business UiPath Automation Platform itself more cost-effectively and with a faster time to value. So, as the slide makes clear, we are about cloud-first, customer choice for delivery of the Business Automation Platform – with flex licensing, you can use either Automation Cloud or Automation Suite. Our typical recommendation for most customers is that Automation Cloud offers the fastest time to value with the lowest TCO, both for getting up and running quickly and, importantly, for adding more capability in the future as your automation needs change.
• #9: While every environment is different, many admin tasks and costs associated with on-premises deployed can be eliminated by moving to Automation Cloud. These are tasks that will simply no longer exist for the customer. They include time and risk associate with updating (often a major pain point), compliance certification and related audits, as well as infrastructure optimization and monitoring (whether the infrastructure is physical or virtual). UiPath takes care of all these things at scale. And, of course, they happen almost instantly. This includes some high business impact areas like adding new services when an urgent need or opportunity arises. Adding services like AI Center or Insights becomes a few minor administrative clicks, not an installation and configuration project – and again it can happen in minutes, not days or weeks Another group of common IT/admin tasks are greatly reduced in scope by moving to Automation Cloud, and therefore cost less. For example, Automation Cloud Robots require no administration at the server/OS level, and they make configuration of the Robot VM and connection back you our own network much quicker and easier than self-hosting robots. So not only does the IT work required go down, but again you can be delivering value much more quickly, and with fewer risks associated with implementation. This also applies to in-product administration and monitoring tasks – you no longer have the work and cost of monitoring hardware/virtual hardware, and only need to manage in-product tasks (like, for example, log analysis or reporting on trends with Insights). Because Automation Cloud has shared platform services and RBAC also across all product services, User and Role Management is simplified, and can still be integrated with leading integrated directory providers (IDP’s). Finally, even if you intend to keep self-hosting robots (instead of SaaS Automation Cloud Robots), Automation Cloud offers full support for that “hybrid” configuration and you will still find your admin costs reduced through not needing to configure/run your own orchestrator. Flexible robot options are an important part of the UiPath value proposition. Automation Cloud can seamlessly manage any combination of robots, so you can optimize for the best combination of admin costs vs. the robot delivery approaches that best fit your specific needs.
• #17: Confirm that UiPath Cloud supports customer applications and external applications based on customer's necessary security policies Prepare a comprehensive roll back procedure For security and authentication with SAML/Azure AD, etc., suggest doing a quick PoC before the real migration to make sure these integrations work as expected for your organization Prior to migration, experiment with the Cloud Migration tool (if following "Lift and Shift") to see what components are migrated. Then, you can complement the plan with list of items that will need to be migrated using Orchestrator Manager or migrated manually (Folder feeds, Users, Queue items, Action Catalogs, Webhooks, etc.) Leverage the tools at your disposal as much as possible (Cloud Migration tool for "Lift and Shift" & Orchestrator Manager for "Incremental Migration") Backup the decommissioned environment after the migration (config files, databases, VMs). This will ensure you have a way to roll back in case something goes wrong during monitoring phase. The DB backup will allow you to have old logs if needed for compliance reasons
• #22: Link to article to help criteria
• #23: Link to the respective tools (cmt + om) Which of the methodologies do we generally see the customers take + what do we recommend based on what TAMs have done? (Add to talk track)