Upgrade of UiPath Orcestrator - standalone

Help Orchestrator
,
1

Hi everyone,

I recently took over UiPath platform maintenance. My background is more on the development side, and I’m still getting familiar with UiPath Orchestrator architecture and upgrade procedures, especially for on-prem setups.

We are currently running UiPath Orchestrator v2022.4.x (on-prem) and would like to upgrade to the latest stable version. Our licenses are active.

At the moment, I’m unsure whether it’s better to upgrade step by step (via an intermediate version) or to go directly from 2022.4.x to the latest stable release. The plan is to perform and validate the upgrade in UAT first, before proceeding to production.

In parallel, we’ve initiated the process of creating/activating our UiPath Customer Portal account, but it has been two days without any response, which blocks us from downloading newer Orchestrator versions and opening official support tickets. Because of this, I’d like to ask where we can best request help in the meantime, and if there is any alternative way to access the installation media or get guidance on the upgrade.

Any advice or shared experience would be very helpful.

Thanks in advance.

Forum Engagement Daily Reports
2

Hi @mkriznjak,

Direct upgrade from Orchestrator 2022.4.x to 2025.10.x (latest stable) is supported for standalone on-prem using UiPathOrchestrator.msi.

Safe Steps

Backup DB, web.config (decrypt EncryptionKey), certs.

Run Platform Config Tool to validate.

UAT: Install MSI, test robots/licenses.

Repeat in prod post-UAT.

Downloads: Need Customer Portal (escalate via rep/support). No community standalone option.

Verify path:

1 Like
Forum Engagement Daily Reports
3

Hi @mkriznjak

You are taking the right steps.

You can also reach out to your customer manager and request their opinions on the matter. Then, accordingly you can proceed. I think there may be difference in licensing also between these versions as license types have also changed.

They would be the best to guide you. Every enterprise customer has their customer manager assigned. Reach out to them via email and take it forward.

Hope this helps.

4

There is more to it than just upgrading the software. There are major changes to the way things are organized in Orchestrator (for example, modern folders). Our on-prem upgrade was a huge project. I highly recommend working directly with UiPath to analyze your current system and make a detailed plan for the upgrade and migration to the way Orchestrator works now.

1 Like
5

Hi @mkriznjak

For on-prem Orchestrator, it’s safest to upgrade step by step rather than jumping from 2022.4.x to the latest version. Test each step in UAT, back up your database, and ensure robot/activity compatibility. While waiting for portal access, you can use UiPath forums or email support for guidance.

6

Thanks, I’ll need that, as we’ve already been waiting 3–4 days for a response regarding Customer Portal access.

7

Quick question, do you know if the Orchestrator 2025.10 can work on .net 10?

8

@mkriznjak

No, UiPath Orchestrator 2025.10 does not support .NET 10, as it does not exist—Microsoft’s latest is .NET 9 (November 2024 release).

1 Like
9

UiPath Orchestrator Parallel Migration Guide (Classic/Modern Folder Compatible)

Before initiating the migration, first identify whether your current automations reside in Classic or Modern folders, as this impacts asset, queue, and permission mappings.

:white_check_mark: Phase 1: Pre‑Migration Assessment

  1. Identify Orchestrator Folder Structure
  • Check if automation components (robots, assets, queues, processes) reside in:
    • Classic folders, or
    • Modern folders
  • Document any dependencies, Orchestrator tenants, AD mappings, and certificate usage.
  1. Validate Your Current Version & Target Version
  • Ensure the new environment is prepared for the latest stable version of UiPath Orchestrator that you plan to use.

:white_check_mark: Phase 2: Infrastructure Setup (Parallel Environment)

  1. Provision New Servers
  • Prepare new Orchestrator application servers (single-node or multi-node depending on your setup).
  • Install necessary prerequisites (.NET, IIS roles, URL Rewrite, etc.).
  1. Provision New SQL Server Instance
  • Prepare the new SQL Server instance to host the new Orchestrator database.
  • Ensure network connectivity, firewall rules, and SQL permissions.
  1. Install the Latest Stable UiPath Orchestrator
  • Install Orchestrator on the new servers.
  • During installation:
    • Choose Self‑signed certificate for initial installation.
    • You will replace this later with your production certificate.

:white_check_mark: Phase 3: Database Migration

  1. Back Up Existing SQL Database
  • Take a full backup of the old Orchestrator database.
  • Ensure database consistency and no running jobs.
  1. Stop Old Orchestrator Application Servers
  • Stop the websites or shut down the IIS site to prevent changes during migration.
  1. Restore Old DB Backup to New SQL Instance (Optional)
    If performing full DB migration, restore the backup into the new SQL instance.
  2. Update Connection Strings in New Orchestrator
  • In the new Orchestrator configuration, update the connection string to point to the old SQL database (or the restored DB).
  • Ensure proper SQL authentication and permissions.
  1. Restart the New Orchestrator Services
  • After restarting, Orchestrator will automatically detect the existing automation data, and all robots, assets, queues, jobs, and logs will appear.

:white_check_mark: Phase 4: Parallel Run Period

  1. Run Both Environments in Parallel (Recommended: 1 Month)
  • Continue to operate from the new Orchestrator.
  • Monitor robot connections, job execution, logs, and queue performance.
  1. Verify Stability & Decommission Plan
  • Validate robot licenses, tenant configurations, audit logs, and API integrations.
  • Ensure all external systems (queues, webhooks, API clients) are re‑pointed to the new Orchestrator.

:white_check_mark: Phase 5: Certificate Update & Final Cutover

  1. Replace Self-Signed Certificate
  • Install and bind your original production SSL certificate to the new Orchestrator server.
  • Update hostnames and bindings accordingly.
  1. Perform Final Switch-Over
  • Redirect DNS from old Orchestrator to the new server.
  • Validate access for all tenants and users.
  1. Decommission Old Infrastructure
  • After the stabilization period (≈1 month):
    • Decommission old Orchestrator server(s).
    • Decommission old SQL database if no longer required.

:wrench: Special Considerations

For Multi‑Node Orchestrator Clusters

If you’re using a multi-node architecture:

  • Repeat the installation and configuration steps on all new nodes.
  • Ensure:
    • Same Machine Key
    • Same Encryption Keys
    • Shared Logs & NuGet folder paths
    • Load balancer configuration is updated

For Classic Folder Environments

  • Re-check robot mappings after migration.
  • Validate permissions & AD user sync.

For Modern Folder Environments

  • Confirm that folder permissions, assets, and modern robot connections remain intact.

Refer below link you can use for upgrade as well it will be suitable for parallel migration