---
title: Assessment Report Details
slug: blueprint/assessment-report-details
createdAt: 2026-06-10T22:53:14.558Z
---

:::CtaButton{label="🟢 Migrator 🟣 Analyze" openInNewTab="true"}

:::

The report includes a summary organized into phases — **Before Conversion **and **After Conversion** — with a recommended action. Use this as your migration project checklist.

***

:::ExpandableHeading
# Overview

## Automations Assessed

Lists the automations included in the assessment with high-level metrics: number of activities, subprocesses, and applications involved. An appendix provides a GenAI-generated narrative description, size and subprocess metrics, a process diagram, and a structure diagram for each automation.

## Effort Reduction Estimate

Shows Blueprint's estimated effort reduction compared to a full manual rewrite, based on your conversion rate — the percentage of actions Blueprint converted automatically. Your rate is benchmarked against the full range of Blueprint-assessed customers.
:::

:::ExpandableHeading{isOpen="true"}
# Before Conversion

The following sections identify decisions and preparation steps that should be completed before running Blueprint's conversion.

## DLLs

Identifies whether DLL calls are present. By default, DLL calls convert to **Run .NET Script** actions in PAD. Alternatives can be configured via rules:

- External flow calls
- Subflow calls
- Another scripting language

## Work Queues

Lists the total number of queue actions and queue name variables identified. Two handling approaches are available:

- **Rules-based:** Create a rule mapping each queue to its PAD queue ID
- **Variable-based:** Blueprint creates a variable for each queue; you set the value

## External Code

Identifies external code blocks referenced in the automations and indicates whether they appear within active call trees or only in orphaned code. External code found only in orphaned automations typically requires no action.

## Assets

Identifies where assets, constants, and settings are referenced. Two handling approaches:

- **Config sheet:** Populate the Assets sheet with key-value pairs before migration so values are substituted automatically
- **Code modification:** Read from a separate sheet, accept values as environment variables, or use another approach

## Missing Code

Lists source files that could not be found during import. Resolution depends on the cause:

- If missing from the import package: locate and re-import the source files
- If variablized subflows: include those subflows during the export step

## Unused Code (Orphans)

Lists automations that exist in the estate but are not called by any active process:

- If variablized subflows: add them to the export
- If genuinely unused: no action required — exclude from migration

## Custom Packages

Identifies third-party or custom activity libraries in use. The handling approach depends on the package type:

- **Low-code (XAML-based):** Convert using **Export as Library**, then import to PAD
- **Binary/compiled:** Set up a rules-based calling approach in the PAD environment
- **No conversion path:** Write equivalent flow logic manually

## Code Reuse

Identifies duplicated code across multiple call trees. Within a single call tree, Blueprint automatically creates one reused subflow. Across call trees, a Reuse rule can consolidate the copies into a single reusable desktop flow, which each flow calls with a Run desktop flow action. Without an enabled Reuse rule, each flow gets its own copy as a subflow.
:::

:::ExpandableHeading{isOpen="true"}
# After Conversion

## Remaining Manual Work

Four categories of items may require attention after Blueprint's automated conversion:

- **TODO items** — Actions Blueprint flagged for review or that could not be fully mapped. Each TODO includes a reason to inform next steps.
- **Compiler errors** — Converted code that contains errors requiring correction before the flow can run.
- **Selectors requiring re-spy** — UI and web selectors flagged as potentially ambiguous or known to not resolve in the target environment. The report provides counts of web selectors, UI selectors, variablized selectors, and known failures.
- **Possible runtime errors** — Patterns that converted successfully but may produce errors at runtime and should be verified during testing.


:::