How to Migrate a Power Virtual Agents Bot to Microsoft Copilot Studio

You have a working bot built in Power Virtual Agents and need to move it to Microsoft Copilot Studio. The two platforms share a common code base, but the migration process is not automatic. Without the correct steps, you risk losing topic logic, trigger phrases, or authentication settings. This article explains the exact migration process, including the prerequisites, the export and import steps, and what to check after the move.

What Migrating a Power Virtual Agents Bot to Copilot Studio Involves

Power Virtual Agents is the older bot-building platform that was part of Microsoft Power Platform. Microsoft Copilot Studio is the newer platform that combines Power Virtual Agents capabilities with generative AI and Copilot features. The two platforms share the same underlying Power Platform infrastructure. This means you can migrate a bot by exporting it as a managed solution from one environment and importing it into another environment that uses Copilot Studio.

The migration does not copy the bot exactly. Some settings, such as authentication details, channel configurations, and environment-specific variables, are not included in the export. You must configure these items manually after the import. The bot topics, trigger phrases, entities, and Power Automate flows are preserved.

You need the following prerequisites before starting:

• A Power Virtual Agents bot in a Power Platform environment where you have System Administrator or System Customizer permissions.
• A target environment in Copilot Studio where you have the same permissions.
• Access to the Power Platform admin center.

Steps to Export a Power Virtual Agents Bot and Import It into Copilot Studio

Follow these steps in order. Do not skip the manual configuration steps after the import.

Step 1: Export the Bot as a Managed Solution from Power Virtual Agents

1. Open the Power Platform admin center
   Go to https://admin.powerplatform.microsoft.com. Sign in with your work or school account that has System Administrator permissions.
2. Select the environment containing your bot
   From the left navigation, select Environments. Find the environment that contains your Power Virtual Agents bot. Click the environment name to open its details.
3. Open the Solutions area
   In the environment details page, select Solutions from the top menu. You see a list of all solutions in that environment.
4. Locate the bot solution
   Find the solution named after your bot. The naming convention is usually “BotName” with a solution type of “Managed.” If you do not see it, use the search box to filter by your bot name.
5. Export the solution
   Select the bot solution by clicking the check box next to it. Then click Export in the top toolbar. In the Export pane, select Managed as the package type. Click Export. The export process starts and may take a few minutes. When it finishes, you receive a download link for a .zip file.
6. Download the exported solution
   Click the download link to save the .zip file to your local machine. Keep this file safe. You use it in the import step.

Step 2: Import the Solution into Copilot Studio

1. Open Copilot Studio
   Go to https://copilotstudio.microsoft.com. Sign in with the same account that has permissions in the target environment.
2. Select the target environment
   In the top-right corner, click the environment selector. Choose the environment where you want to import the bot. If you do not see the correct environment, you may need to switch tenants or request access.
3. Open the Solutions area in Copilot Studio
   From the left navigation, select Solutions. If you do not see this option, click the three-dot menu and select Solutions.
4. Import the solution
   Click Import in the top toolbar. In the Import pane, click Choose File and select the .zip file you downloaded earlier. Click Next. The import process validates the solution. If there are no errors, click Import. The import may take several minutes. A green success message appears when it finishes.
5. Verify the imported bot
   After the import completes, go back to the main Copilot Studio dashboard. Your bot should appear in the list of bots. Click the bot name to open it. Check that topics, entities, and flows are present.

Step 3: Reconfigure Authentication and Channels

1. Set up authentication
   In Copilot Studio, open your imported bot. Go to Settings > Authentication. Choose the authentication method you used in Power Virtual Agents. For Microsoft Entra ID authentication, re-enter the app registration details. For manual authentication, re-enter the token endpoint and client credentials.
2. Reconfigure channels
   Go to Settings > Channels. Each channel you used before, such as Microsoft Teams or a custom website, must be reconfigured. Click the channel name and follow the setup steps. You may need to generate new channel-specific credentials.
3. Update environment variables
   If your bot uses environment variables for API endpoints or other dynamic values, go to Settings > Environment Variables. Verify that each variable has the correct value for the new environment. Update them if needed.

Step 4: Test and Publish the Bot

1. Test topics and trigger phrases
   In Copilot Studio, open the Topics tab. Select a topic and test it using the Test bot pane. Type trigger phrases and verify that the correct topic responds. Repeat this for all major topics.
2. Test Power Automate flows
   If your bot uses Power Automate flows, go to Settings > Flows. Check that each flow is enabled and connected to the correct connectors. Run a test from the bot to confirm the flow executes.
3. Publish the bot
   Once testing passes, click Publish in the top-right corner. Choose the channels where you want the bot to be live. Confirm the publish action. The bot is now available on the configured channels.

Common Issues After Migration and How to Fix Them

Bot Topics Appear but Do Not Respond to Trigger Phrases

This happens when the imported solution does not include the trigger phrase mappings in a format that Copilot Studio recognizes. To fix this, open each affected topic, go to the Trigger section, and re-enter the trigger phrases. Then save and test again.

Power Automate Flows Show Errors or Are Missing

The exported solution includes the flow definition, but the connections in the flow may point to the old environment. Open each flow in Power Automate, edit the connections, and re-authenticate them. Then save and turn the flow back on.

Bot Does Not Appear in Copilot Studio After Import

The import may have succeeded, but the bot might be hidden because it was imported as a managed solution. Go to Solutions, find the imported solution, and open it. Look for the Bot component. If it exists, click it to open the bot in Copilot Studio. If the bot still does not appear, you may need to create a new bot and import the solution into that bot container.

Power Virtual Agents vs Copilot Studio: Key Differences After Migration

Item	Power Virtual Agents	Microsoft Copilot Studio
Bot creation interface	Standalone web app or inside Power Platform	Copilot Studio portal with AI authoring copilot
Topic creation	Manual topic creation only	Manual plus generative AI topic suggestions
Authentication export	Not included in solution export	Not included in solution import
Channel configuration	Configured per bot in Power Virtual Agents	Configured per bot in Copilot Studio
Power Automate integration	Flows are included in solution export	Flows are imported but connections must be re-authenticated

After migration, you can use Copilot Studio’s generative AI features to enhance your bot. For example, you can enable the “Boost conversations” toggle to let the bot answer questions from your knowledge bases without writing custom topics. You can also use the Copilot authoring pane to create new topics faster.

To avoid data loss, always export a backup copy of your bot before starting the migration. Keep the original environment intact until the imported bot passes all tests. If you encounter errors during the import, check the Power Platform admin center’s solution history for detailed error messages. These messages often point to missing dependencies or permission issues.