UiPath, moved to 2025.10 LTS before the support dates pass.
Mainstream support for UiPath 2024.10 LTS ends on 21 October 2026. Extended support for 2023.10 runs out between 23 October and 3 November. We upgrade Orchestrator, Studio and Automation Suite, convert Windows-Legacy projects, and add agents only where they earn their place.
Cohash upgrades, supports and extends UiPath estates.
We move Orchestrator, Studio and Automation Suite to 2025.10 LTS, convert Windows-Legacy projects that Studio STS can no longer edit, harden robot credentials and queues, and build agentic workflows with UiPath Maestro. UiPath's lifecycle page puts the end of 2024.10 LTS mainstream support for Orchestrator and Studio on 21 October 2026.
you probably need this if
Orchestrator is on 2023.10 or 2024.10, and support ends this month.
Most processes are Windows - Legacy projects and nobody owns the conversion.
Robots fail after every SAP or Salesforce release because selectors break.
30 Apr 2025UiPath Maestro GA Maestro went GA alongside the launch of UiPath's Platform for agentic automation. source ↗
21 Oct 20262024.10 LTS mainstream support ends Standalone Orchestrator 2024.10 and Studio 2024.10 leave mainstream support on 21 October 2026. Extended support runs to 21 October 2027. Automation Suite 2024.10 follows on 11 November 2026. source ↗
today · Oct 22, 2026
23 Oct 2026ahead2023.10 LTS extended support ends Extended support for 2023.10 ends product by product: Orchestrator on 23 October 2026, Studio on 25 October 2026, Automation Suite on 3 November 2026. source ↗
no date yetWindows - Legacy projects in Studio STSStudio STS won't create or edit Windows - Legacy projects any more. Studio LTS still can, and will for the foreseeable future.source ↗
the story · uipath estate
From the first call to a setup your own team can run.
Here's what usually prompts a call about your UiPath estate, what we do about it and in which order, and where you end up.
01 · where it hurts02 · what we change03 · how it runs04 · where you end up
incident board · uipath estate3 open
openOrchestrator is on 2023.10 or 2024.10, and support ends this month.
recurringMost processes are Windows - Legacy projects and nobody owns the conversion.
blockedRobots fail after every SAP or Salesforce release because selectors break.
exposure
Orchestrator and Automation…Windows-Legacy project conversionAutomation Cloud migrationAgentic automation with MaestroRobot security and credentialsRun support
S/4
startrehearsehandover
Estate inventory
Upgrade and conversion plan
Rehearse and convert
Cut-over and run
we are here
ready to hand over
The platform is on a supported release again within a short time.
AP reviews matches the agent proposes instead of starting from scratch.
Process inventory with project compatibility, package versions and owner
Upgrade path to 2025.10 LTS with dates from UiPath's lifecycle page
chapter 01 · where it hurts
Why teams reach out
Orchestrator is on 2023.10 or 2024.10, and support ends this month.
Most processes are Windows - Legacy projects and nobody owns the conversion.
Robots fail after every SAP or Salesforce release because selectors break.
chapter 02 · what we change
How we solve it
Orchestrator and Automation Suite upgrades
Windows-Legacy project conversion
Automation Cloud migration
Agentic automation with Maestro
Robot security and credentials
Run support
chapter 03 · how it runs
Our approach
Estate inventory
Upgrade and conversion plan
Rehearse and convert
Cut-over and run
chapter 04 · where you end up
What changes
The platform is on a supported release again within a short time.
AP reviews matches the agent proposes instead of starting from scratch.
Process inventory with project compatibility, package versions and owner
Upgrade path to 2025.10 LTS with dates from UiPath's lifecycle page
what we do
Our UiPath work
6 kinds of UiPath work, each run by engineers who have done it on live tenants.
Standalone Orchestrator or Automation Suite moved to the 2025.10 LTS line, with database backups, tenant settings, queues and assets checked before and after.
Projects converted from Windows - Legacy to the Windows compatibility, activity packages updated and each process regression-tested against the target applications.
On-premises Orchestrator tenants moved to Automation Cloud, with robots, folders, credentials and schedules mapped and cut over by process group.
Long-running processes modeled in UiPath Maestro, with agents, robots and people each doing the steps they are suited to, and human approvals where the risk calls for it.
Robot accounts, credential stores and Orchestrator roles reviewed so unattended robots hold only the access their processes need.
Queue monitoring, failed job triage, and a fix list for the processes that break every time a target application changes.
capability 01 / 06in production
S/4
Orchestrator and Automation Suite upgrades
Standalone Orchestrator or Automation Suite moved to the 2025.10 LTS line, with database backups, tenant settings, queues and assets checked before and after.
Projects converted from Windows - Legacy to the Windows compatibility, activity packages updated and each process regression-tested against the target applications.
Long-running processes modeled in UiPath Maestro, with agents, robots and people each doing the steps they are suited to, and human approvals where the risk calls for it.
We pieced these together from UiPath situations that come up a lot. They're patterns. You won't find a specific client in them.
case file 01
Orchestrator 2023.10, 400 Windows - Legacy processes, support ending this month
composite · not a client story
Beforethe situation
Standalone Orchestrator is on 2023.10, and its extended support ends on 23 October 2026. Most of the 400 processes are Windows - Legacy projects on old activity packages. The CoE has two developers to deal with all of it.
What we dothe work
We rank processes by business impact, move Orchestrator to 2025.10 LTS first, since Studio LTS still edits Windows - Legacy projects, then convert processes in waves with a regression test for each.
Afterwhere you end up
The platform is on a supported release again within a short time. Converting projects then becomes scheduled work, no longer an emergency.
case file 02
Invoice exceptions handled by hand next to a working robot
composite · not a client story
Beforethe situation
A robot posts invoices into SAP, but a third of them fail on mismatched purchase order lines and land in a shared mailbox for the AP team to fix by hand.
What we dothe work
We build an evaluation set from past exceptions first. Then we model the process in Maestro, add an agent step that reads the invoice and PO and proposes a match with its reasoning, and route low-confidence cases to an AP approver.
Afterwhere you end up
AP reviews matches the agent proposes instead of starting from scratch. And thanks to the evaluation set, you know how the agent behaves before it touches production.
We don't start a step until the last one has produced something you can check.
step 01
Estate inventory
We write down which Orchestrator, Automation Suite and Studio versions you run, which processes are on which project compatibility, the activity package versions and robot accounts, and the target applications each process touches.
step 02
Upgrade and conversion plan
A version path to 2025.10 LTS, the order to convert Windows - Legacy projects, and a regression test set for the processes the business depends on.
step 03
Rehearse and convert
We upgrade a non-production Orchestrator, convert and test processes in waves, and fix selectors and package conflicts as they surface.
step 04
Cut-over and run
We upgrade production in a planned window, reconnect the robots and keep an eye on them. Then your CoE gets the queue dashboards and runbooks.
ai on uipath
Where AI fits on UiPath, and where it needs guardrails.
The UiPath Platform is what UiPath sells for agentic automation. Its Maestro, GA since April 2025, coordinates agents, robots and people across long-running processes. Orchestrator hosts and connects MCP servers too. Agents handle the judgement steps robots can't, and in return they need test sets, approval points and narrowly scoped service accounts.
AI agentasks for data or an action
Scoped identityonly the access it needs
MCP serverthe one door into the platform
Logged, approveda person signs off on writes
UiPathdoes the work
Orchestrator has MCP support built in. It covers UiPath, remote, command, coded and self-hosted servers, with Platform and Swagger types still in preview. We run every server under a robot account scoped to its folder and we log its tool calls. A write to any business system has to pass a Maestro approval step first.
UiPath Maestro
Maestro models long-running processes where agents, robots and people each take steps. We put agents on exception handling first, reading documents or triaging cases, say. A person keeps approving actions on live transactions.
MCP servers in Orchestrator
In Orchestrator you can expose UiPath processes as MCP tools and connect remote, coded or self-hosted MCP servers. Two server types, Platform and Swagger, are in preview. We publish only the processes an agent needs. For external servers we stick to trusted providers.
Agent evaluation before production
Agents make probabilistic decisions. So we build a test set out of real past cases and agree the pass criteria with the process owner, and we rerun it after each prompt or model change.
AI help with Windows - Legacy projects
Studio STS no longer edits Windows - Legacy projects. An AI assistant can document old workflows and draft conversion notes. Developers still rebuild and test each one.
Where UiPath sits between people, agents and business systems
Orchestrator schedules unattended robots and Maestro coordinates long-running processes that mix robots, agents and people. Robots work in target applications through UI and API automation, and agents call language models for steps that need judgement.
01 · Triggers
ServiceNowrequests · tickets → UiPath Maestro · start process
Email and documentsinvoices · forms → Orchestrator 2025.10 · queue items
These are working documents, written against your configuration, so your team can run them without us.
inventory01
Process inventory with project compatibility, package versions and owner
yours to keep
document02
Upgrade path to 2025.10 LTS with dates from UiPath's lifecycle page
yours to keep
tests03
Windows - Legacy conversion plan with regression test set
yours to keep
report04
Robot account and credential review with least-privilege changes
yours to keep
runbook05
Orchestrator upgrade runbook with rollback steps
yours to keep
document06
Agent use case brief with evaluation criteria and human approval points
yours to keep
talent and delivery · uipath
Certified engineers, wherever you need them.
Some clients want a project team, some want a couple of engineers on theirs. Either works. Onsite, nearshore or offshore, with handovers across time zones that keep things moving.
Put these to anyone bidding on your UiPath work. The ones who've done it answer differently from the ones who've read about it.
Q1
Which of our components are past or near end of support, by UiPath's own lifecycle page?
Orchestrator, Studio and Automation Suite each have their own dates. Build the plan around one date and you'll miss the others.
Q2
After converting the Windows - Legacy projects, how are you going to regression-test our processes?
Conversion changes activity packages and runtime. Without a test per process, failures show up in production queues.
Q3
What would you change about our robot accounts and credential stores?
Unattended robots often run on broad service accounts. That's an audit and security problem well before anyone starts on agents.
Q4
How will you evaluate an agent before it acts on live transactions?
Agents make probabilistic decisions, so a test set from real past cases and a human approval threshold are the minimum before production.
Q5
What stays on premises if we move Orchestrator to Automation Cloud?
The robots, and their network access to target systems, remain your responsibility. The design should show where each one runs and how it reaches its applications.
01Which UiPath versions are still supported?
2025.10 is the current LTS for Orchestrator and Studio on UiPath's lifecycle page, with mainstream support to October 2027. 2024.10 LTS leaves mainstream support on 21 October 2026. 2023.10 extended support ends between 23 October and 3 November 2026, depending on the product.
02Do we have to convert Windows - Legacy projects?
Not immediately if you stay on Studio LTS, which still edits them. Studio STS no longer creates or edits them, and new projects default to Windows. Most teams convert as part of an upgrade so they aren't tied to one Studio track.
03How long does an Orchestrator upgrade take?
The platform upgrade is the quick part. Most of the time goes on regression-testing your processes, particularly anything built as a Windows - Legacy project or on old activity packages. We size the job from your process inventory.
04Should we move to Automation Cloud?
It depends on data residency, network access to target systems and how much infrastructure work you want to keep. Automation Cloud takes platform upgrades off your plate. What it can't do is give robots a network path to on-premises applications. That's still yours to provide.
05Where do agents fit in our UiPath estate?
Look first at processes that already have exceptions people handle by reading documents or emails. Maestro can route those steps to an agent and add a human approval. The robots keep the deterministic work.
06Do you staff UiPath developers?
Yes. UiPath developers, solution architects and infrastructure engineers, on contract, contract-to-hire or permanent terms. Onsite in the US, nearshore or offshore, any time zone.
services
Related services
Projects on UiPath usually end up touching one of these, so they're worth a look.
