The RPA robot that stops on closing day, the robot whose builder left: we read it and migrate it to Kitewell with the same steps.
Migrating off UiPath, WinActor, BizRobo!, or Power Automate Desktop does not mean rebuilding your robots. A migration tool reads your UiPath projects, WinActor scenarios, BizRobo! robots, and Power Automate Desktop flows, turns each into a Kitewell workflow with the same steps, and runs it on your screens. A moved workflow repeats what it learned in the same order every time, and relearns only the operations a changed screen no longer matches, keeping a record of each. Your work's steps stay the same. What changes is how a stop gets fixed, and the cost, which will always be less than today. We move one robot that keeps stopping and show it running, free. Start by talking to us.
A migrated robot at work
A robot that entered invoices by replaying recorded screen elements, moved to Kitewell by the migration tool. On the usual screens it repeats what it learned. When the accounting app's screens change, the old robot stops, and Kitewell relearns only the operations that changed and enters all six.
Five moments that lead to an RPA migration
Moments common to companies with robots: what migrating changes, and what we show you with the first robot.
The robot stopped on the morning of closing day
- What migrating changes
- When a learned operation no longer matches the screen, AI finds it again and carries on, and later runs repeat what it relearned. Which operations it relearned stays on record with screenshots. If it still can't go on, it tells the person in charge and resumes from the step that stopped.
- What the first robot shows you
- A record of a recently stopped robot, moved and running on your screens
One button moved, and you wait for the vendor's quote
- What migrating changes
- Small screen changes are relearned and the work goes on. When the steps should change, someone on your team asks Kitewell and checks the change before it is applied.
- What the first robot shows you
- A record of someone on your team changing one step by asking, and the robot running
Its builder left, and nobody can explain it
- What migrating changes
- The migration tool reads the robot's own files, so it moves without its builder. What the robot does (systems, inputs and outputs, branches, what happens on errors) and a mapping from each old operation to its new step stay in Kitewell.
- What the first robot shows you
- That robot's description and mapping, yours to keep even if you decide not to move it
The renewal quote arrived
- What migrating changes
- After the move it will always cost less than today. Kitewell updates itself, so upgrade work goes away too.
- What the first robot shows you
- Today's cost beside the cost after the move, ready to attach to your approval request
Rebuilding every robot on PAD was quoted
- What migrating changes
- Instead of people rebuilding robots one by one, the migration tool reads them and moves them. Your staff learn no new development tool. What remains is checking the results match, against a record of the two running side by side.
- What the first robot shows you
- One robot from that quote, moved and running, to set beside the quoted effort
The migration tool: read it, then move it
Nothing is rebuilt, and AI does not act on its own. The results are checked side by side with your current robot.
- 1
Read
The migration tool reads the robot and writes up what it does in plain words.
- 2
Move
It becomes a Kitewell workflow with the same steps. What to act on and what to wait for are written in everyday words. A mapping from each old operation to its new step is kept.
- 3
Run
The first run checks and learns each operation; later runs repeat what was learned. Steps that read PDFs or Excel files, or check a screen, use AI every run.
- 4
Side by side
The results are compared with your current robot, and you switch once they match. The old robot is kept stopped, so you can go back.
What to prepare and where the move happens are decided when we talk.
Keep it, rebuild on PAD, or move to Kitewell
Companies that drop RPA on cost alone mostly rebuild on Power Automate Desktop. Compare more than the license: the effort to move, and the upkeep after.
| Item | Keep your RPA | Rebuild on Power Automate Desktop | Move to Kitewell |
|---|---|---|---|
| Cost | Your current contract. UiPath raised prices about 10% in 2023 and ended its on-premises legacy plans; WinActor raised them roughly 10% in January 2025 | Free for local runs. Running unattended needs a paid license | Always less than today. It updates itself, so updates take no work |
| Effort to move | None | Rebuild every robot, and your staff learn PAD | The migration tool reads your robots and Descarty moves them. Your staff learn no new development tool |
| When a screen changes | A developer fixes it. UiPath's self-healing is Enterprise-only, and its fixes are not saved to the project | Self-healing is in preview, fixes only during the run, and is not saved to the flow | AI relearns the operation and carries on, and later runs repeat what it relearned. Which operations it relearned stays on record |
| When steps change | Your RPA developer changes them | Staff who learned PAD change them | The people doing the work ask Kitewell to change them |
| Where screen content goes | Depends on setup (on-premises is possible) | Self-healing needs cloud AI and permission to move data across regions | Only the AI model you choose. With an in-house model, nothing leaves |
PAD suits companies with no limits on cloud use, standardized on Microsoft 365, whose staff already know PAD well.See the sources for PAD's conditions
Kitewell updates itself, so even on-premises there is no update work; for closed networks, we agree how updates are delivered. Learned operations are repeated as they are, and steps that read documents or check screens use AI on every run.
Sorting robots four ways for migration
We do not propose moving everything. The assessment decides robot by robot and groups the robots by license.
Move
Less effort and cost on Kitewell.
- Works screens that change often (SaaS, partner sites, accounting software)
- Stops often and takes effort to fix
- Its builder has left and no one can fix it
- Needs documents read or approvals midway
- Has to be rechecked anyway at the next renewal or server replacement
Keep
Better left in your current RPA.
- Fixed processing in volume that must be fast
- Runs reliably on screens that rarely change
- Citrix or SAP work that runs reliably in your current RPA
Replace with an API
A data connection is more reliable than the screen.
- The other system offers an API or file exchange
Retire
No reason to run it any more.
- No longer used
- The work itself ended or changed
How an RPA migration runs, and how long it takes
We plan back from the date you must give notice to reduce licenses, not from the renewal date. Durations are estimates.
- 1
Talk to us
FreeDuration：One hour online- What you do
- Tell us about your RPA, the robots that trouble you, and your renewal date
- What Descarty does
- We listen and pick the first robot to move with you
- What you keep
- The robot to move, and the schedule
- What you decide next
- Whether to move one robot
- 2
We move one and show you
FreeDuration：About two weeks- What you do
- Watch the robot's screens with us once, then join the review
- What Descarty does
- We take the robot, move it to Kitewell with the migration tool, and show it running on your screens at the review
- What you keep
- A record of the run with screenshots, what the robot does, and the mapping from old operations to new steps
- What you decide next
- Whether to look at all of them
- 3
Migration assessment
FreeDuration：About two weeks- What you do
- Go through the robot list and run history with us
- What Descarty does
- We sort every robot into move, keep, replace with an API, or retire, and set today's cost beside the cost after the move
- What you keep
- A plan and cost comparison ready to attach to your approval request
- What you decide next
- Whether to run a joint verification
- 4
One-month joint verification
Free unless it meets the success criteriaDuration：One month- What you do
- Join a 30-minute review each week
- What Descarty does
- We run the robots to be moved alongside your current ones on production screens and report each week how results match, how often they stopped, and the time to fix
- What you keep
- Weekly records and a final report
- What you decide next
- Which robots to move, and in what order
- 5
Move by the deadline
QuotedDuration：Depends on the plan- What you do
- Approve each switch after seeing the side-by-side results
- What Descarty does
- We move robots in the planned order, check each side by side before switching, and keep the old robot stopped so you can go back
- What you keep
- A next contract without the moved robots' licenses
- 6
Operation
Maintenance support is quotedDuration：—- What you do
- When steps should change, the people doing the work ask Kitewell
- What Descarty does
- We find the cause of stops AI can't fix
- What you keep
- Why each change was made, kept in Kitewell
Migration guides by product
Price and license changes, how self-healing works and what it needs, and how to tell work to keep from work to move, with sources.
Frequently asked questions
- Which RPA can Kitewell replace?
- UiPath, WinActor, BizRobo!, Power Automate Desktop, and others. The migration tool reads each robot and turns it into a Kitewell workflow with the same steps.
- How is a robot migrated?
- The migration tool reads the robot, writes up what it does, and makes a workflow with the same steps. It runs on your screens and is compared with your current robot before you switch. The mapping from old operations to new steps stays in Kitewell.
- What does the migration tool do?
- It reads UiPath projects, WinActor scenarios, BizRobo! robots, and Power Automate Desktop flows and moves them to Kitewell workflows. It also writes up what each robot does and maps each old operation to its new step.
- Do we have to rebuild our robots to replace our RPA?
- No. The migration tool reads your current robots and moves them to Kitewell with the same steps. Your staff do not rebuild them in a new development tool.
- Can we migrate orphan robots whose builder has left?
- Yes. The migration tool reads the robot's own files, so it moves without its builder. What the robot does and the mapping from each old operation to its new step stay in Kitewell, so it is no longer a black box.
- Can we migrate robots with our own AI agent?
- Yes. Connect an AI agent such as Claude or Claude Code to Kitewell over MCP, and it can read a robot, build the workflow, and run it to check. Descarty helps you set it up.
- Does a moved workflow have AI decide each time?
- No. It repeats what it learned in the same order every time. AI is used to relearn an operation a changed screen no longer matches, and in steps that read documents or check screens.
- How does the cost change when we switch off our RPA?
- After the move it will always cost less than today. The assessment compares three years of cost for keeping your RPA, rebuilding on Power Automate Desktop, and moving to Kitewell, based on your current contract and the time upkeep takes.
- Should we move to Power Automate Desktop instead?
- PAD suits you if cloud use is unrestricted, you are standardized on Microsoft 365, and your staff know PAD well. Kitewell suits you if you want to avoid rebuilding, keep working when screens change, keep screen content inside the company, or let the people doing the work fix it.
- Do our current robots stop during the move?
- No. Each moved workflow runs alongside your current RPA until its results check out, and you drop only the moved robots' licenses at the next renewal.
- How long does an RPA migration take?
- It depends on how many robots you have and what they do. We plan back from the date you must give notice to reduce licenses, not from the renewal date. A one-month joint verification proves the first robots, and the rest follow in the planned order.
- How many robots do we need to start?
- One is enough. The assessment sorts every robot into retire, keep, move, or replace with an API, and the ones with the biggest effect move first.
- How does it differ from UiPath Healing Agent?
- Healing Agent is an Enterprise feature, and fixes made during a run are not saved to the project. Kitewell repeats relearned operations from the next run on, and which operations it relearned stays on record. The details and sources are in the guide to UiPath pricing and Healing Agent.
Tell us about the robot that keeps stopping
We move the first robot and show it running, free. Even if you decide not to move it, its description is yours to keep.