Before leaving UiPath or WinActor for Power Automate (PAD)

The renewal quote for UiPath or WinActor arrived, and you decided to move to Power Automate Desktop (PAD below). PAD comes with Windows 11, and you already pay for Microsoft 365. Then the next quote arrived: rebuilding every robot in PAD.

This column sets out what to check before moving from UiPath or WinActor to PAD, from Microsoft’s documentation and what other vendors publish. Is there a conversion tool? What work does each robot need? What is free, and where do you start paying? Under what conditions does PAD’s AI self-healing work? It also covers which companies PAD suits, and one more option to compare before rebuilding in PAD. Everything is as of October 28, 2026.

Key points

• Microsoft has no official tool that converts UiPath or WinActor robots to PAD. For UiPath, other vendors offer conversion tools and migration services built on them
• We found no tool that converts WinActor scenarios to PAD. Accounts from Japan describe the move as a rebuild in PAD
• Even with a conversion tool, each robot still needs its unconverted operations finished, tests, and a check against the current robot
• What costs nothing extra is a person starting flows on their own PC. Microsoft 365 licenses include no desktop flow rights; running at a set time needs Premium, and running unattended needs Process
• AI self-healing is in preview and recovers at run time only. It needs an organizational Premium account, permission to use Anthropic’s models, and, in Japan, a setting that moves data across regions

No official tool converts UiPath or WinActor to PAD

The only conversion tool of Microsoft’s own we could confirm in Microsoft’s documentation is the Process migrator for Softomotive products (preview), for moving from Softomotive’s products. It does not cover UiPath or WinActor, and it was deprecated on November 3, 2023.

In a January 2022 blog post, Microsoft released an RPA migration guide (a whitepaper written with Cognizant) and pointed to partners’ migration tools and services:

• Avanade: a two-week assessment for migrating to Power Automate
• Blueprint Software Systems: the RPA Bot Migration Assistant
• Cognizant: the RPA Bot Migrator (tool and service)

As far as we could find on October 28, 2026, neither UiPath nor NTT Advanced Technology, which makes WinActor, offers a tool to convert its robots to PAD. A conversion tool, if you use one, will come from another vendor.

From UiPath: other vendors’ conversion tools and what they cover

For UiPath robots, there are tools that convert them into PAD flows, and migration services that use such tools. The table below is each vendor’s own description, and the figures are their own.

Vendor	What the vendor says	What it says remains
Blueprint Software Systems	Converts UiPath, Blue Prism, and Automation 360 automations into PAD flows. 95–99% of source actions convert automatically, with 70–75% less effort than a manual rewrite (its own study)	States that “migration isn’t fully automated” and draws a line between what converts and what the delivery team finishes. For finishing, it lists TODO guidance in the code, selector reports, test generation, and specifications
Kanerika (FLIP)	Reads UiPath workflows (XAML) and maps UiPath actions to their Power Automate equivalents	Complex automations go to engineers for review. Converted flows run alongside the UiPath robots until their results match, and only then is production switched over
AKKODiS Consulting (listed on Microsoft Marketplace)	Moves bots from UiPath, Blue Prism, Automation Anywhere, and others to Power Automate with migration assistant software	Its engineers build out the bots that need manual work

Blueprint’s rate counts source operations (actions), not robots. By that arithmetic, a robot with 200 operations still has 10 left for a person to finish even when 95% convert.

As an example of what a tool-based migration service involves, HCLTech lists a three-week service on Microsoft Marketplace. It assesses 10 bots and moves one of them with Blueprint, and it lists this work:

• Week 1: run the assessment tool, judge each bot’s fit with PAD, and decide how to design the flows and integrations
• Week 2: migrate with Blueprint and build any actions Blueprint cannot map. Write documentation and functional test cases
• Week 3: validate against the existing bots and the business requirements, run the tests, and deploy to test or production

Even when a tool converts the robot, finishing what did not convert, testing, and checking against the current robot remain for each one.

From WinActor: no conversion tool found

As far as we could find on October 28, 2026, no tool converts WinActor scenarios into PAD flows. Companies in Japan that handle these moves describe them as rebuilds.

• C3 Index: this company, which helps businesses adopt PAD, wrote in January 2026 that a migration is not a “translation” but a “rebuild (redesign)”
• 7robots: this service, which builds and maintains RPA, wrote in June 2021 about a move to PAD a WinActor customer had asked for. The finished scenarios could not be carried over, and the robots were rebuilt from scratch. Excel operations that took one part in WinActor took several actions combined in PAD, and a robot of about 150 parts in WinActor could grow to nearly 200 in PAD

A quote to move WinActor robots to PAD will assume rebuilding each one in PAD. When you read it, check that it covers the work in the next section as well as the rebuild.

The work each robot needs when moving to PAD

Whether a tool converts the robots or people rebuild them, each robot needs this work.

Work	What it involves	Easy to miss
Understand it	Find out which systems it uses, what it enters, where it branches, and what it does on failure	Without its builder, some operations have no known purpose. The 7robots team also checked such operations with the staff as it went
Rebuild it in PAD, or finish the conversion	Make PAD actions do the same thing. With a conversion tool, build the operations that did not convert	Something that was one part in the old product can become several actions in PAD
Check it	Run it on the same input as the current robot and compare the results	Check the branches that only run occasionally, such as at month-end or on closing day
Prepare where it runs	To run unattended, register the PC with Power Automate as a machine and assign licenses	Registering a machine needs Premium. One Process license runs one flow at a time
Train people to fix it	Have people who can fix it in PAD when it stops	WinActor is a flowchart of blocks and lines; PAD is a text-based script. The screens and habits differ

A quote to rebuild every robot is the number of robots times this work. Check in particular that it includes the period of running both side by side and comparing, and the time of the people who will fix the robots in PAD afterwards. How to find out what a robot does is explained in Taking over an RPA bot whose builder has left.

What is free, and what you pay for

Which use is “PAD is free” about? Microsoft’s documentation says:

• It comes with Windows 11: Power Automate has been built into Windows 11 since its general availability in October 2021. On Windows 10, you download and install it
• No extra cost when a person runs it on their own PC: using it with a Microsoft account costs nothing extra, and the flows you build are saved to OneDrive. With a work or school account, the Free license also lets you build desktop flows and run them on your own PC (attended), but not share them
• Microsoft 365 licenses include no desktop flow rights: the Power Automate rights in Microsoft 365 stop at cloud flows with standard connectors. Windows licenses include only running desktop flows on the PC itself, with no starting or managing them from the cloud

Attended means running on a PC where a person is signed in. Unattended means a bot signs in to the PC on the user’s behalf, runs the flow, and signs out. The licenses each use needs are below (prices exclude tax and are the monthly equivalent, billed annually, from Microsoft’s Japanese pricing page).

Use	License needed
A person starts it on their own PC	No extra cost (a Microsoft account, or the Free license on a work account)
Share flows, or register the PC with Power Automate as a machine	Premium (¥2,248 per user)
Start it attended from a cloud flow (including at a set time)	Premium
Start it with a run URL, such as from Task Scheduler	Premium, or a pay-as-you-go environment
Run it with no one present (unattended)	Process (¥22,488 per bot). A Premium user registers the machine, and the creator of the connection a cloud flow uses to start it also needs Premium
Run it on a virtual machine Microsoft provides	Hosted Process (¥32,233 per bot)

Each Process bot runs one unattended flow at a time, so you need as many Process licenses as flows that run in parallel. One bot comes to about ¥269,856 a year, excluding tax. A person starting flows on their own PC can also run only one flow at a time.

Robots that run unattended overnight in UiPath or WinActor do not become free by moving to PAD. The ways to run a flow at a set time, with their conditions, are compared in Scheduling Power Automate Desktop on the free version, and how to add up the total, beyond licenses, in What RPA costs to keep running.

The conditions on AI self-healing (preview)

PAD has a self-healing feature: when a screen element cannot be found, AI looks for it again and the run continues. Microsoft’s documentation, dated June 30, 2026, sets these conditions and limits:

• Preview: available to organizational Premium accounts at no extra cost. Not available in government or sovereign clouds
• Run time only: the flow itself is not fixed. Microsoft describes a person making the needed changes to the flow later
• Limited cases: it works only for actions that act on a single element, such as clicking a button, and only on “element not found” and “window not found” errors. Actions on several elements, such as drag and drop, are out of scope
• Turned on per action: in Power Automate for desktop 2.66 or later, in each action’s error handling settings
• Admin settings: allow Anthropic as an AI provider in both the Microsoft 365 admin center and the Power Platform admin center, and turn on Copilot in Power Automate. Outside the US, also turn on “Move data across regions” for the environment
• Screen images go to AI: it collects a screenshot of the missing element, the title of its parent window, and an image of the whole desktop, and uses GPT-4.1 mini and Claude Sonnet 4.5 to find the element. Microsoft warns that it may pick an unintended element
• Records: the portal’s action-level logs do not show self-healing details. The run page shows a summary of up to three successful repairs

Whether screen contents may go to AI outside your region depends on your IT department’s policy. If they may not, you cannot use this feature. How UiPath’s Healing Agent works, and its conditions, are set out in UiPath pricing and Healing Agent.

Companies PAD suits

PAD clearly suits some companies.

• Most of the work stays inside Microsoft 365: Office 365 Outlook, Microsoft Teams, SharePoint, and Excel Online (Business) are standard connectors, usable in cloud flows within a Microsoft 365 license. With no screens to operate, screen changes cannot stop them
• Few robots, mostly started by people on their own PCs: these run at no extra cost
• Staff already know PAD well: they can fix a robot in-house when it stops
• The screens it operates rarely change: RPA’s strength of repeating set steps applies as is
• No restrictions on cloud use: sending screen contents to AI outside your region for self-healing is also allowed
• Many standard UiPath robots, with the time and budget to convert and verify them: another vendor’s conversion tool lets you move them to a plan

If “free” is the only reason, add the licenses that unattended and scheduled runs need, and the work to move each robot, before you compare.

Before rebuilding in PAD, compare rebuilding in Kitewell

Faced with a quote to rebuild every robot in PAD, set one more option beside it. Kitewell does not read robot files either, so it is also a rebuild, but of a different kind: you describe the current steps in words, and AI builds the workflow on the real screens. Your staff learn no new development tool.

• It repeats what it learned: a moved workflow repeats its recorded operations in the same order every run, and relearns only the operations a changed screen no longer matches. Which operations it relearned stays on record. Steps that read PDFs or Excel files, and steps that check a screen, use AI every run
• Checked side by side before you switch: the new workflow’s results are checked against the current robot before you switch. Your own staff can do the moving, or hand it to Descarty or a partner
• Cost: Kitewell Team is ¥14,800 per computer a month, or ¥148,000 a year (excluding tax), the same for building and running computers

You do not have to move everything. You can keep the robots that run reliably on your current RPA, leave work that stays inside Microsoft 365 to Power Automate cloud flows, and move the robots that keep stopping, or whose builders have left, to Kitewell.

You can try Kitewell free for 14 days, or ask for a 30-minute demo. RPA migration covers how it runs, and the guides for UiPath, WinActor, and Power Automate Desktop cover each product.

Frequently asked questions

Can UiPath robots be converted to PAD automatically?

There is no official Microsoft tool. Other vendors’ tools and services, such as Blueprint and Kanerika, convert them, but each says that finishing what does not convert, and testing and validation, remain.

Is there a tool that moves WinActor scenarios to PAD?

We found none as of October 28, 2026. In the accounts from Japan, the robots were rebuilt in PAD.

With Microsoft 365, can we run PAD robots across the company?

Running them on your own PC, started by a person, costs nothing extra. That right comes from the Windows license or the Free license, though; Microsoft 365 licenses include no desktop flow rights. Sharing flows, registering machines, and starting flows from cloud flows need Premium, and running with no one present needs Process.

With PAD’s self-healing, can we stop fixing robots when screens change?

No. Self-healing only looks for the element again during a run; the flow itself is not fixed. It is a preview feature that needs an organizational Premium account and admin settings, and in Japan a setting that moves data across regions.

Summary

• Microsoft has no official tool that converts UiPath or WinActor to PAD. Other vendors convert UiPath, and each says finishing and testing remain
• No tool converting WinActor to PAD was found, and accounts from Japan describe the move as a rebuild
• Each robot needs to be understood, rebuilt, checked, given somewhere to run, and given people who can fix it
• No extra cost covers a person running flows on their own PC. Microsoft 365 licenses include no desktop flow rights; set-time runs need Premium, and unattended runs need Process
• Self-healing is in preview and recovers at run time only. It needs a setting that moves data across regions
• Before rebuilding every robot in PAD, compare it with rebuilding them in Kitewell

Sources

• Microsoft: Process migrator for Softomotive products (preview) (December 16, 2020)
• Microsoft: Proven methods to modernize your RPA approach with Power Automate (January 14, 2022)
• Blueprint Software Systems: RPA Migration to Power Automate and beyond, Blueprint Demos (both checked October 28, 2026)
• Kanerika: UiPath to Power Automate Migration Services (checked October 28, 2026)
• AKKODiS: End-to-End RPA Migration to Power Automate with Intelligent Automation (Microsoft Marketplace, checked October 28, 2026)
• HCLTech: RPA Migration Assessment - Sher.PA (Microsoft Marketplace, checked October 28, 2026)
• C3 Index: From WinActor and UiPath to Power Automate (January 28, 2026, in Japanese)
• 7robots: What we noticed moving from WinActor to Power Automate Desktop (June 28, 2021, in Japanese)
• Microsoft: Getting started with Power Automate for desktop in Windows 11 (October 4, 2021)
• Microsoft: Get started with a Microsoft account (February 17, 2023)
• Microsoft: List of all Standard tier connectors (checked October 28, 2026)
• Microsoft: Types of Power Automate licenses (September 22, 2026), Deep dive on specific licenses (October 17, 2026)
• Microsoft: Power Automate pricing (checked October 28, 2026, in Japanese)
• Microsoft: Trigger desktop flows from cloud flows (May 5, 2026), Run desktop flows via URL or desktop shortcuts (February 25, 2026)
• Microsoft: Self-healing (preview) (June 30, 2026)