Migrating Power Page Sites to a New Environment

In this Pragmatic Works training summary, Brian Knight walks viewers through a modern workflow for migrating Power Pages from development into QA and production environments. He introduces the Dataverse Enhanced Data Model and demonstrates how it simplifies deployment, improves application lifecycle management (ALM), and reduces the friction that historically made site migration unreliable.

Why change the migration approach?

Brian explains that traditional migration approaches for Power Pages—using PowerShell pack commands or third-party tools—were often error-prone. Those difficulties frequently pushed teams to develop directly in production to avoid migration headaches. The enhanced data model changes that by pre-installing Power Pages components and templates into environments, making site deployment more predictable and faster.

Key prerequisites and caveats

• The technique shown applies to sites created with the Enhanced Data Model. Existing legacy sites will require a different migration path (Brian notes Microsoft will provide guidance later).
• Turning on the enhanced data model should ideally be done before building the site. Enabling it triggers solution installations and takes ~15–20 minutes.
• Separation of concerns is recommended: keep data objects (tables, forms, views) in a separate solution from the site itself to allow independent deployment schedules.

Step-by-step migration process

1. Enable Enhanced Data Model: In the Power Platform admin center, select the environment and toggle the enhanced data model. Wait for the installer to finish adding the Power Pages core and V2 templates.
2. Create a Solution: In make.powerpages, create or open a solution to hold your site. Brian suggests adding the site to a solution so it becomes solution-aware.
3. Add Existing Site: Use “Add existing site” to include the built Power Page. This imports site assets, configurations, languages, and externalized content—but not the actual table data.
4. Publish and Export: From the site overview, publish changes and export the solution. Choose managed for production and unmanaged for non-production environments based on your release strategy.
5. Import in Target Environment: In the target environment, import the exported ZIP. If the import fails, it’s usually due to missing dependencies (e.g., database tables not deployed)—verify all dependent solutions are present.
6. Reactivate the Site: Imported sites may be inactive. Reactivate and rename appropriately for the production environment. Subsequent imports will not require reactivation.

Practical tips from Brian

• Publish before export: Ensure everything is published to avoid missing saved changes.
• Check dependencies: Major import failures occur when related data solutions aren’t deployed first—deploy data tables/forms in their separate solution ahead of time.
• Use managed vs unmanaged: Prefer managed solutions for production to lock down delivered assets; keep development iterative with unmanaged packages.

Benefits of the enhanced data model

Brian highlights several operational benefits:

• Faster site creation—new environments go from ~45–60 minutes down to roughly 5–10 minutes.
• Simpler ALM and more predictable migrations thanks to pre-installed Power Pages components and templates.
• Improved portal management experience—Power Page Management replaces Portal Management and brings more fluid controls and better browser compatibility.
• Easier repeatable deployments that let teams keep development, QA, and production environments aligned without risky direct edits in production.

Limitations and what’s coming

Brian cautions that this new approach currently works for sites created with the enhanced data model. Microsoft is expected to provide tools or steps to migrate older sites into this model. For now, teams planning new Power Pages should enable the enhanced data model early to take full advantage of these ALM improvements.

For teams already using Power Pages, Brian’s walkthrough provides a practical migration blueprint: enable the enhanced data model, structure solutions to separate data and site assets, export/import carefully checking dependencies, and reactivate sites in the target environment. These steps help reduce migration risks and accelerate delivery.