Answered

Migrating Vibe Power App solution

(2) Share

Report

Posted on by WK-18101208-0

Hi All,

Just checking if there is any way to migrate Vibe Power App from one environment to another environment? Is this supported now? I tried to package the app in a solution, exported it into a zip file and imported it into another environment. I can see the plan and tables, but not the app itself. Any idea how to migrate the published app too?

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (9)

Answers (1)

Sort by

Suggested answer

Valantis 6,821 on at

Like
a
(2)

Report
Copy link

Link copied!
Hi @WK-18101208-0,

Unfortunately, Vibe apps (built on vibe.powerapps.com) can't be reliably moved between environments right now due to preview limitations.

What's Not Working:

Vibe apps are stuck in the Vibe experience: using the standard solution export breaks the AI plan connections

After importing, apps either disappear from your Apps list or become disconnected and can't be edited

ALM tools like the CLI and deployment pipelines don't support Vibe-specific components yet

Possible Workarounds:

Recreate the app using the same prompt in your target environment

Export the tables and AI plans separately through solutions, then rebuild the app

Convert your app to a traditional canvas app (but this removes the AI features) for CLI-based migration

Current State:

Vibe is best used as a prototyping tool right now—it's not ready for production scenarios that require moving apps across environments.

Resources:

Microsoft Docs: Create apps with Vibe (check also the Limitations here)

Complete guide to Power Apps Vibe

Let me know if you run into any issues! ;)

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

VGKolar 51 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @WK-18101208-0

As of now, Vibe Power Apps are not fully solution aware. While tables and plans export correctly, the app UI itself remains environment-bound and does not migrate through solutions. This is a current platform limitation for Vibe apps.

At the moment, the only options are to recreate the app in the target environment or rebuild it as a classic Canvas App if cross-environment ALM is required.

Was this reply helpful? Yes No
WK-18101208-0 27 on at

Like
a
(1)

Report
Copy link

Link copied!
Hi @Valantis

Taken from the links you have shared https://learn.microsoft.com/en-us/power-apps/vibe/create-app-data-plan#application-lifecycle-management-alm-capabilities.

Publishing app: When you’re ready to release your app for production, select Publish in the app’s command bar. If your app uses any draft tables, you're prompted to publish those tables as well.

It seems like the document says that we can release the app for production. Unfortunately, I had made many modifications to the app via the AI chat and it is not easy to redo all of them now (it is like a whole week of work) especially for AI since the results are not always guaranteed the same. I have used the standard way to export the solution and import the solution in the taget environment. I can get all the components in the solution, including the plan, app and all the tables, in the classic make.powerapps.com interface. However, when I viewed the solution in the new vibe.powerapps.com interface, I can only see the plan and data, but not the app. In the App tab it shows an error message "Failed to fetch apps" with button to regenerate the app again. When I clicked on the button 'Regenerate app', the system went on to regenerate an app that looks very different from the original one.

My app contains only Dataverse table and no other connections or components. I wonder if there are ways to just let the app runs in a Production environment as I had created the app in a Developer environment. This (moving into a Production environment) is all I need, since I am not able to share the app in a Developer environment with other users (they would need a Power Apps licence) that do not have a Power Apps licence.

Was this reply helpful? Yes No
WK-18101208-0 27 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi Valantis,

My reply above.... Thanks!

Was this reply helpful? Yes No
Verified answer

Valantis 6,821 on at

Like
a
(1)

Report
Copy link

Link copied!
Hi @WK-18101208-0,

I double-checked the Microsoft Vibe (Preview) documentation and validated your tests. Unfortunately, your conclusions are correct:

What the documentation confirms

Apps built in the new Vibe authoring experience can’t be accessed or edited outside that experience.

Exporting an app and redeploying it via standard ALM paths (e.g., solution export/import, PAC CLI) creates a new app and breaks the original plan linkage.

Current ALM guidance supports save/publish/share in the same environment—there is no supported cross-environment migration for Vibe apps.

Vibe is Preview and not intended for production use yet.

Available options:

Recreate the app directly in the target environment using the same prompts

Wait for GA release when ALM capabilities may be expanded

Submit feedback via the Ideas portal requesting cross-environment migration support (this is what Microsoft will tell you to do if you open ticket) :)

There is currently no supported workaround to move Vibe apps across environments with their exact AI-generated logic intact.

I hope this answers some of your questions :)

Was this reply helpful? Yes No
WK-18101208-0 27 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @Valantis

Thanks for your confirmation. Unfortunately, that would mean I have waste a whole week of effort. Sigh...

Was this reply helpful? Yes No
poweruser0205 4 on at

Like
a
(0)

Report
Copy link

Link copied!
In my case, when I followed the steps below, it gave me the App experience when I migrated my solution between environments:

Create a New Solution for my Vibe experiment

Set that solution as Preferred Solution

Start Vibe'ing

Save solution frequently and periodically refresh the solution so that it does not break in the middle

Published the solution when I am ready.

Those steps also allowed Vibe to place all artifacts (including tables, plan, Data Workspace, app, etc.) into the solution that I created in #1.

Exporting that solution from my dev environment and Importing into next environment gave the same app.

I do have one issue after publish and when I access the app i.e. I don't think it is connecting to the dataverse of the environment the app is in. I am seeing the below error. Did anyone run into this error and resolved?

Timed out after 30000ms while making a call to the 'In Memory Data Provider'., Stack: Error at ec (assets/index-T28lB-Cg.js?skoid=3dbc96d3-0d12-427b-a1cf-47940917a6cd&sktid=975f013f-7f24-47e8-a7d3-abc4752bf346&skt=2026-01-22T01%3A00%3A00Z&ske=2026-01-29T01%3A00%3A00Z&sks=b&skv=2025-01-05&sv=2025-01-05&spr=https&st=2026-01-22T01%3A52%3A32Z&se=2026-01-26T16%3A00%3A00Z&sr=c&sp=rl&scid=583ea843-5090-41a9-b909-95b9a11c7d4f&sig=z0m4L7FeMy4919pWPz8Elgzl8a3xPOsXP3%2F5xcjjVtk%3D:453:1100) at async assets/index-T28lB-Cg.js?skoid=3dbc96d3-0d12-427b-a1cf-47940917a6cd&sktid=975f013f-7f24-47e8-a7d3-abc4752bf346&skt=2026-01-22T01%3A00%3A00Z&ske=2026-01-29T01%3A00%3A00Z&sks=b&skv=2025-01-05&sv=2025-01-05&spr=https&st=2026-01-22T01%3A52%3A32Z&se=2026-01-26T16%3A00%3A00Z&sr=c&sp=rl&scid=583ea843-5090-41a9-b909-95b9a11c7d4f&sig=z0m4L7FeMy4919pWPz8Elgzl8a3xPOsXP3%2F5xcjjVtk%3D:520:3424 at async ic (assets/index-T28lB-Cg.js?skoid=3dbc96d3-0d12-427b-a1cf-47940917a6cd&sktid=975f013f-7f24-47e8-a7d3-abc4752bf346&skt=2026-01-22T01%3A00%3A00Z&ske=2026-01-29T01%3A00%3A00Z&sks=b&skv=2025-01-05&sv=2025-01-05&spr=https&st=2026-01-22T01%3A52%3A32Z&se=2026-01-26T16%3A00%3A00Z&sr=c&sp=rl&scid=583ea843-5090-41a9-b909-95b9a11c7d4f&sig=z0m4L7FeMy4919pWPz8Elgzl8a3xPOsXP3%2F5xcjjVtk%3D:490:1399360) at async kr.getAll (assets/index-T28lB-Cg.js?skoid=3dbc96d3-0d12-427b-a1cf-47940917a6cd&sktid=975f013f-7f24-47e8-a7d3-abc4752bf346&skt=2026-01-22T01%3A00%3A00Z&ske=2026-01-29T01%3A00%3A00Z&sks=b&skv=2025-01-05&sv=2025-01-05&spr=https&st=2026-01-22T01%3A52%3A32Z&se=2026-01-26T16%3A00%3A00Z&sr=c&sp=rl&scid=583ea843-5090-41a9-b909-95b9a11c7d4f&sig=z0m4L7FeMy4919pWPz8Elgzl8a3xPOsXP3%2F5xcjjVtk%3D:520:4142) at async queryFn (assets/index-T28lB-Cg.js?skoid=3dbc96d3-0d12-427b-a1cf-47940917a6cd&sktid=975f013f-7f24-47e8-a7d3-abc4752bf346&skt=2026-01-22T01%3A00%3A00Z&ske=2026-01-29T01%3A00%3A00Z&sks=b&skv=2025-01-05&sv=2025-01-05&spr=https&st=2026-01-22T01%3A52%3A32Z&se=2026-01-26T16%3A00%3A00Z&sr=c&sp=rl&scid=583ea843-5090-41a9-b909-95b9a11c7d4f&sig=z0m4L7FeMy4919pWPz8Elgzl8a3xPOsXP3%2F5xcjjVtk%3D:520:4293) Caused by: Error: Timed out after 30000ms while making a call to the 'In Memory Data Provider'. at assets/index-T28lB-Cg.js?skoid=3dbc96d3-0d12-427b-a1cf-47940917a6cd&sktid=975f013f-7f24-47e8-a7d3-abc4752bf346&skt=2026-01-22T01%3A00%3A00Z&ske=2026-01-29T01%3A00%3A00Z&sks=b&skv=2025-01-05&sv=2025-01-05&spr=https&st=2026-01-22T01%3A52%3A32Z&se=2026-01-26T16%3A00%3A00Z&sr=c&sp=rl&scid=583ea843-5090-41a9-b909-95b9a11c7d4f&sig=z0m4L7FeMy4919pWPz8Elgzl8a3xPOsXP3%2F5xcjjVtk%3D:454:119

Was this reply helpful? Yes No
korebreach 28 on at

Like
a
(0)

Report
Copy link

Link copied!

@poweruser0205 . Yes, after setting your preferred solution, building in Vibe, saving (frequently), publishing, exporting the solution, and importing to another environment, your plan AND app will be in the new environment. However, the plan and app are no longer linked. If all you need to do is run your app from that new environment, you're ok. However, if you want to continue Vibe-coding that app in the new environment, you'll find that the app isn't listed in Vibe... only the plan is.

This might not be a problem in some cases (if you're just running the app from the new environment). If you want to keep Vibe-ing on your app: If something goes wrong in your original environment (which, let's face it... Vibe in preview is extremely fragile), and your app/plan get unlinked there, you're in a no-win situation. You can't use a solution copy (the plan/app are disconnected there). You can't use the new environment (the plan/app are disconnected there also).

This is exactly what happened to me. Vibe chat told me to do something to fix a data issue. I came back with, "I have some concern about doing that because what if something goes wrong." "It's fine. It's the supported way to do it". "OK"... <poof>. App now won't load. Refreshed. Vibe won't find my app anymore. OK. Gotta restore from that solution backup. Nope. OK. Gotta roll-back the whole environment from a restore. "No valid targets for restore" in the Admin Center.

"So Vibe... Tell me I'm screwed without telling me I'm screwed".

Was this reply helpful? Yes No
WK-18101208-0 27 on at

Like
a
(0)

Report
Copy link

Link copied!

@korebreach,

That's a pity. I tried to migrate to a production environment. It worked, but only the schemas of the tables from DATAVERSE were migrated to the new environment, not the data unfortunately. Using data export/import won't work this way as the record unique ID would be different and will break the parent-child relationships between the tables as imported records will have different record ID. Well, I have to re-create all the master data again if I want to continue to use the app in the production environment. One way is to make the changes in the DEV environment and only import that app in the PROD environment. If there are any changes in the tables in the DATAVERSE, you would need to repeat the changes manually in the PROD tables. Long way to go for Vibe Power Apps...

Was this reply helpful? Yes No