We are currently planning (or undergoing) a migration from UiPath On-Prem Orchestrator to UiPath Cloud (Automation Cloud), and I wanted to understand from the community:
What are the common challenges or issues you have faced during this migration?
Specifically interested in areas such as:
Connectivity with on-prem applications (network drives, internal systems)
It’s mainly involves handling connectivity to on‑prem systems, converting legacy projects, and reconfiguring robots, assets, and credentials.
Key challenges are network access, modern compatibility, licensing changes, and governance differences. the best approach is to clean up and upgrade first, run pilot migrations, use hybrid setup for on‑prem access, and migrate in phases aligned with license cycle. Please take the backup of all.
One thing I would add from the migration/readiness side is to avoid treating this only as an Orchestrator infrastructure move.
In practice, I would map the migration in a few layers before moving workloads:
Connectivity: identify which automations still depend on network shares, internal APIs, SAP/on-prem applications, local files, certificates, proxies or allowlists.
Assets and credentials: inventory them first and map ownership/environment differences rather than migrating them one by one as issues appear.
Packages and activities: check not only package versions, but also Legacy/Windows compatibility, deprecated activities, custom libraries and shared dependencies across processes.
Robot/runtime configuration: compare the current execution model with the target Cloud setup, including machines, folders, unattended runtimes and licensing assumptions.
Integrations: email, Microsoft 365, browsers, SAP and other integrations can become a separate migration problem even when the workflow itself looks compatible.
Portfolio dependencies: this is probably the most overlooked part. A package/library/configuration change may affect many automations, so looking at processes individually can hide the real blast radius.
I have found it useful to perform a preflight first and classify processes into something like ready / requires adjustment / blocked / requires architectural decision, before starting the actual migration waves.
For Legacy → Windows specifically, the Activity Migrator can also be useful as one input, but I would not treat its output as the complete readiness assessment. Package dependencies, arguments, integrations, infrastructure and licensing/runtime requirements still need to be correlated around it.
If I were structuring the migration, I would probably go:
Hi @yashwanthb_kumar ,
Migrating from UiPath On-Prem Orchestrator to Automation Cloud can provide better scalability and reduced infrastructure management, but there are a few common challenges to plan for.
Common Challenges
Connectivity to on-prem applications: Cloud services cannot directly access internal systems. You may need Hybrid Robots, VPN, or Cloud Robots with secure connectivity.
Assets and Credential Migration: Credentials, assets, queues, and triggers often need validation after migration to ensure mappings and permissions are correct.
Windows-Legacy Projects: Older projects may require conversion to Windows compatibility and testing of package dependencies.
Robot & Licensing Changes: Cloud uses a different licensing and robot management model, so machine templates, runtimes, and user assignments should be reviewed.
Performance/Latency: Processes interacting heavily with on-prem applications may experience slight delays due to network communication.
Security & Compliance: Verify data residency, firewall rules, access controls, SSO, and compliance requirements before migration.
Best Practices
Perform a detailed assessment of robots, assets, queues, and packages before migration.
Convert and test Windows-Legacy projects early.
Start with a pilot migration of a few non-critical processes first.
Use Automation Cloud Robot/Connectivity options appropriate for your network architecture.
Validate all credentials, triggers, API integrations, and external system connections after migration.
Keep rollback and backup plans ready until production stabilization.
What are the common challenges or issues you have faced during this migration?