Showing results for 
Search instead for 
Did you mean: 

Move or Copy a SharePoint list PowerApps Custom Form

It would be nice to be able to create a SharePoint list PowerApps Custom Form in one site or list (e.g. development) and then be able to move it to another site or list (e,g, production). This would help with development and teting of new and updated forms before they are released to the production. This could also help with the reuse of form designs, so a person isn't always recreating the wheel.

Status: Under Review
Regular Visitor

This seems like a no-brainer... why wouldn't you want to copy a list without the customized power app (if it has one)? At least make it optional in the event someone has customized the list's form in PA.

Also allow: copying multiple lists at a time, lists with lookup columns

Not applicable

It will be great if this can be implemented.

Advocate V

Any update on the status for this? The status has not been updated for couple of years. It is waiting by many organizations and even more helpful for organization that has heavy Sharepoint usage.

Frequent Visitor

I cannnot understand why MS doesn't implement this feature.

Regular Visitor

This is very annoying since many years. No ALM for SharePoint integrated PowerApps Forms...

Kudo Kingpin

In the meanwhile, you can use a free Flow & Power Apps Migrator to migrate Power Apps and Power Apps Forms: Let me know if it works for you!

Regular Visitor

Wow, thank you @DenisMolodtsov MS really need to release this functionality. Even for the fact that migrating sites we have to pay for 3rd party is also not good.

For now I will try this. 


I just don't understand what was the idea of creating multiple environment and ease of migrating your powerapps and flows from one Environment to the next but leaving SharePoint list out of that.


Hopefully we can get an answer very soon about this.


I will give you a feedback Denis once I have used it.

Regular Visitor

I have commented here before long ago… and the need remains high. But I also think this is an opportunity beyond just moving SharePoint based forms. SharePoint continues to represent an important piece of the puzzle for knowledge management in M365, for documents, pages and the large volume of list management scenarios that are important to customers but need remain in the realm of citizen developers. These workloads should not be hoovered up into the bull rush to drive more Dynamics licensing. It’s a 60/40 rule where the former represent these use cases, and the complete solution is to bring SharePoint objects into the solution management capabilities of Dataverse. Imagine the power of bundling the tables, with the canvas and model apps, with the portal, with the SharePoint site including lists and forms, with the power bi components, with the Flows, with the other kitchen sink objects one can now place in a solution, and exposing the whole thing through Teams!!!!! All low code, all config, low overhead, total value. Can we imagine the consumption this would drive? The opportunity for monetising solutions for isv’s? There are individuals and organisations trying to string all this together now but none are slick or comprehensive. None are singular in approach. It’s time to close the loop.

Advocate III

This is annoying since years. Makes SharePoint integrated PowerApps Form mostly useless.

Cannot import export. Can not use these Forms in Solutions. No Connections References, no Environment Variables. No Child Flows. No sustainable ALM. 

New Member

Hello @BhutiM , were you successful in using the free Flow & Power Apps Migrator provided by @DenisMolodtsov ?