Cloud migration logs showed success — but configs were still missing. How are you validating at scale?

Help Orchestrator
, , , , , ,
1

Hi Community,

After completing UiPath Orchestrator migration from on-prem to Automation Cloud, one challenge stood out more than the migration itself:

validation.

When migrating environments with:

  • hundreds of processes
  • large folder structures
  • thousands of assets and queues
  • complex roles, triggers, and permissions

…the Cloud Migration Tool completes successfully, but verifying that everything actually moved correctly becomes extremely manual.

Where things got tricky

Migration logs indicate success or failure, but they don’t provide a side-by-side view of:

  • on-prem vs cloud objects
  • missing or partially migrated items
  • folder-level mismatches
  • subtle differences in queues, triggers, or permissions

Exporting via Orchestrator Manager helps, but still leaves the comparison effort largely manual.

What we ended up doing

To solve this, we built an internal migration validation utility using Orchestrator APIs that:

  • pulls configuration data from both on-prem and cloud
  • normalizes objects across all components
  • generates a structured spreadsheet
  • provides automated side-by-side comparisons
  • flags mismatches automatically

A full environment comparison completes in under a minute.

What surprised us

In several cases, migration logs showed everything as “successful,” yet the validator still surfaced:

  • missing assets in certain folders
  • queue configuration differences
  • triggers that didn’t fully replicate
  • minor role/permission mismatches

These are the kinds of issues that usually only show up later, once processes start running and troubleshooting begins.

Curious how others approach this

How are you validating large-scale UiPath cloud migrations today — especially across multiple environments?

Would love to hear how others are handling this.

2

Hello @ravindra.reddy33!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly
Forum_Staff

3

@ravindra.reddy33

Thats a good way to go with..but not sure how much time it would have taken for you to build

What we have done is similar but we did not build from scratch…we used orchestrator manager and extended the functionality

We exported all the data we can and then use another process which takes the two excels as inputs and will write vlookups and formula needed to compare and give the results

this way what we built is only a small process which basically compares two excels

Kudos for your work

cheers

4

Hi @Anil_G,

Thanks a lot for sharing your experience! We looked at extending Orchestrator Manager as well, and it’s definitely a practical route for many scenarios.

In our case, the volume and complexity across environments required deeper comparisons—especially around nested configurations like queue settings, triggers, permissions, and folder-level mappings. Because of that, we moved toward a fully API-driven validator that normalizes both sides and produces a consolidated comparison automatically. It took some upfront engineering, but the consistency and speed made it worthwhile for repeated migrations.

It’s interesting to see how different teams have solved the same challenge. Always good to exchange perspectives—appreciate your inputs.

1 Like