--- title: Importing RPA Files to Migrator slug: blueprint/importing-rpa-files-to-migrator docTags: yO7XZ9PJxDCKZ-Mf4TSYB,3lbpbXxTS6GkR2MAW1UVV,beX1uo1606aQy6uHFcLIm,qDedWHgNZqWNK_paaZ7TV createdAt: 2026-04-17T18:28:53.382Z --- :::CtaButton{label="🟒 Migrator" openInNewTab="false"} ::: **Migrator **supports importing automations from UiPath, Blue Prism, and A360. Before importing, you will need to export your automations from the source tool β€” see [Exporting Source RPA Files](docId\:CyHzZMDDXKxCGp5H_GmBi). *** # Supported Sources & Import Formats - PAD - Dataverse connection or Solution file (.zip) - UiPath - .zip, .nupkg - UiPath projects that use VB.NET or C# expressions can be imported - Blue Prism - .zip, .bprelease - Automation Anywhere (A360) - A360 connection, .zip, .aapkg *** # Import Size Limits RPA imports can be large and resource-intensive. If your import exceeds the limits below, consider splitting it across multiple Blueprint projects. - **Project limit** β€” 100,000 actions per project - **.bprelease (uncompressed)** β€” 300 MB maximum - **.zip, .nupkg (compressed)** β€” 50 MB maximum - **.xaml (single file)** β€” 5 MB maximum :::hint{type="info"} β“˜ If you are running Blueprint on-premise, ensure your server has adequate resources to handle large imports successfully. ::: *** # Import Steps :::::WorkflowBlock :::WorkflowBlockItem In the Project Explorer, select the folder or project where you want the imported processes placed ::: :::WorkflowBlockItem Click the **More** button in the navigation bar and select the RPA tool you are importing from ::: :::WorkflowBlockItem Click **Choose File** and select the file to import. The accepted file type is shown above the field β€” selecting an unsupported file type will display an error ::: ::::WorkflowBlockItem *Optional: * Choose a **Template** β€” UiPath, Blue Prism, and A360 all support templates. Leave blank if unsure :::hint{type="info"} β“˜ If you encounter errors saving Blue Prism import templates, see [Blue Prism: Troubleshooting Import Templates](docId\:p3BPOEUTD7j4clvG0OvgN). ::: :::: ::::WorkflowBlockItem *Optional: * Choose **Also Import to Analyze** β€” select this if you plan to use **Analyze** capabilities for this data or generate a Migrate Assessment Report. If GenAI is configured, you can also choose to **(✨GenAI)** generate a Process Diagram and scan for Sensitive Data :::hint{type="success"} When using **Also Import to Analyze**, a link is created between the **Migrator** and **Analyze** imports for quick cross-reference. - In **Migrator**, the link appears in the Utility Panel. - In **Analyze**, it appears under **Details -> General Information -> Migrate Link**. ::: :::: :::WorkflowBlockItem Click **Continue** ::: ::::WorkflowBlockItem A modal displays the contents of the file. Select or deselect files for import as needed. Use the **Show Unsupported** checkbox to include or exclude unsupported file types :::hint{type="info"} β“˜ For Blue Prism imports, additional options are available. See [Blue Prism: VBO Matching on Import](docId\:s-OAmmBCcs3s4fR2dfnlI). ::: :::: :::WorkflowBlockItem Click **Import** ::: :::WorkflowBlockItem A notification confirms the import has been scheduled. Click the link in the notification to monitor progress on the Jobs page, or click **OK** to dismiss ::: :::WorkflowBlockItem Once the import job completes, refresh the page or click the **Refresh** icon in the Explorer Panel to view the imported processes ::: :::WorkflowBlockItem Depending on your system configuration, processes may need to be activated before they can be exported. Only activated processes can be exported to Power Automate Desktop ::: ::::: β“˜ See [License and Activity Reporting](docId\:TIIVvOfaT-cCSyu2p3MMm) and [Migrator/MigrateDashboards: License Consumption](docId\:Ytu76e7qoCXu2DX1ec2-2) for more information on activating processes. *** # Files Created on Import Two additional files are created alongside every import: - **Source File** β€” A copy of the original imported source file, available to download if needed - **RPA Import Log** β€” A record of all processes and sub-processes imported, including details on any failures. See [RPA Import Log](docId\:Lh0YlRTxzB3w8G175L1oU) for details.