Hi Team,
Good Morning..
Current Situation we have
On-Prem Orchestrator version: 2023.4.1 (LTS)
where Multiple production jobs running
Decision: we are planning to Move directly to Orchestrator Cloud instead of upgrading On-Prem to 2024.10.6 .
so if anyone have any suggestion could help on this? will this impact anything?
Thankyou for the help.
Moving directly from On-Prem Orchestrator 2023.4 LTS to Cloud Orchestrator is supported, so upgrading on-prem to 2024.10 is not mandatory if Cloud is the final goal.
Things to note:
No auto-migration — folders, assets, queues, schedules, robots must be recreated/migrated.
Robots need re-connection (different machine/robot keys in Cloud).
Reconfigure triggers, credentials, and identities.
Ensure package & Studio compatibility with Cloud.
Keep on-prem running in parallel until Cloud is validated.
Best practice: set up Cloud in parallel, migrate gradually, then switch production.
Hope this helps 
Thankyou for the response,
Users, Modern Folders also need to recreated?
Yes. When moving from On-Prem to Cloud Orchestrator, Users and Modern Folders do not migrate automatically and need to be recreated/reconfigured in Cloud.
Users: Must be re-added (via Cloud identity / SSO / directory sync as applicable).
Modern Folders: Need to be recreated and users/robots reassigned.
You can use Orchestrator APIs to speed this up, but it’s not automatic.
Hi @Snehamayi_Senapati
Good Morning 
Yes, you can move directly from On-Prem Orchestrator 2023.4.1 (LTS) to Orchestrator Cloud without upgrading to 2024.10.x first. This is a migration, not an upgrade, so assets, processes, queues, and schedules need to be recreated or migrated.
There is no major impact if you plan properly. Ensure robot and Studio versions are compatible, reconfigure assets (especially credentials), and test all production jobs in Cloud. Best practice is to run Cloud in parallel, migrate in phases, and then switch production once validated.
Thankyou for the response
so what about the SQl Db server which is current on prem ?
The on-prem SQL DB is not used in Orchestrator Cloud. Cloud Orchestrator has its own managed database, and your existing SQL DB cannot be connected or reused. You can keep the on-prem DB only for reference or rollback, and decommission it after the cloud setup is stable.
your on‑prem sql db won’t be used once you move to orchestrator cloud. automation cloud has its own managed database and does not allow connecting your own sql server, so the existing on‑prem db becomes legacy/read‑only for reference only.
no data automatically migrates, so logs, jobs history, assets, queues, schedules, and users from the on‑prem db will not transfer unless you manually recreate needed items. running robots will simply point to cloud and won’t rely on the old sql db anymore.
If helpful, mark as solution. Happy automation with UiPath
you can migrate from on prem to cloud
most of the runtime data and logs queue data would be lost as on prem is connected to your local DB and cloud is not connected
processes ..folders etc can be migrated
contact your customer rep to have both on prem and cloud till you migrate and test all process so that no impact is seen by business
cheers
@Snehamayi_Senapati Moving directly from On-Prem 2023.4 LTS to Cloud Orchestrator is a valid approach and you don’t need to upgrade On-Prem to 2024.10.6 first. A few additional considerations to keep in mind: review your existing integrations (AD authentication, network-level access to robots, firewall rules) since Cloud uses a different connectivity model with Cloud Robot connections. Also check if any of your processes depend on on-prem-specific features like local NuGet feeds or custom configurations in web.config. Plan for a parallel running period where both On-Prem and Cloud are active so you can validate everything works before decommissioning On-Prem. Finally, check your licensing — Cloud Orchestrator licensing may differ from your current on-prem license structure.
Sure John.. Thankyou for your inputs.. will take the help from UiPath Customer support