---
title: Preparing Migrated Flows for Production
slug: blueprint/preparing-migrated-flows-for-production
docTags: yO7XZ9PJxDCKZ-Mf4TSYB
createdAt: 2026-05-26T16:43:09.972Z
---

:::CtaButton{label="🟢 Migrator" openInNewTab="false"}

:::

# Completing PAD Code Post-Migration

Migrated flows are not production-ready out of the box. Platform differences between legacy RPA tools and Power Automate Desktop mean code completion work is always required after export. This article explains what to expect in your output and what you'll need to address manually.

***

# What You'll Need to Fix Manually

## TODOs and Compiler Errors

TODOs and compiler errors make up the bulk of post-migration completion work. Resolving these is required before a flow can run.

## Selectors

Resolving TODOs and compiler errors alone does not make a bot production-ready. **Selectors must also be reviewed and tested.** Blueprint cannot validate selector efficacy during migration because it does not have access to your target applications.

:::hint{type="info"}
ⓘ If you encounter selector issues in migrated flows, contact Blueprint Support or your Success Manager.
:::

## Custom Actions and Libraries

Blueprint migrates standard actions only. For custom actions and libraries, Rules can be configured to define how Blueprint handles them during export.

# If Processes or Subflows Appear Missing

By default, Blueprint inlines subflows that are called only once or are very short — they won't appear as separate flows in output. If you believe logic is missing:

::::WorkflowBlock
:::WorkflowBlockItem
Verify your selections in the Export Wizard
:::

:::WorkflowBlockItem
Check the RPAImportLog in your project folder for import failures — failures are listed at the top
:::

:::WorkflowBlockItem
Use Bulk Reimport/Recalculate to force a fresh migration of specific processes
:::
::::