Migrate Sites from the Standard Data Model to the Enhanced Data Model
Migrate Sites from the Standard Data Model to the Enhanced Data Model
The Enhanced Data Model introduces a modern architecture for Power Pages that improves website performance, provisioning speed, Application Lifecycle Management (ALM), and overall maintainability. Organizations currently using the Standard Data Model can migrate their websites to the Enhanced Data Model using Power Platform CLI.
This migration process helps modernize existing websites and enables organizations to take advantage of solution-based configurations, improved management experiences, and enhanced performance capabilities.
Prerequisites
Before starting the migration process, ensure the following prerequisites are met:
- Power Platform CLI version 1.31.6 or later.
- Dataverse Base Portal Package 9.3.2307.x or later.
- Power Pages Core Package 1.0.2309.63 or later.
- Basic knowledge of Power Platform CLI for Power Pages.
- Background operations enabled for environments in administration mode.
Step 1: Download and Review Existing Site Metadata
Begin by authenticating with your Dataverse environment and generating a customization report to understand the existing website configuration.
Authenticate to Dataverse
pac auth create -u [Dataverse URL]
List Available Websites
pac pages list
Generate Site Customization Report
pac pages migrate-datamodel --webSiteId [WebSiteId-GUID] --siteCustomizationReportPath [PATH]
Review the generated report carefully before proceeding with the migration.
Step 2: Migrate Site Data
Run the migration command and choose the appropriate migration mode depending on your requirements.
pac pages migrate-datamodel --webSiteId [WebSiteId-GUID] --mode [configurationData|configurationDataReferences|all]
| Migration Mode | Description |
|---|---|
| configurationData | Migrates website configuration and metadata. |
| configurationDataReferences | Migrates transactional data references. |
| all | Migrates both configuration and transactional data. |
Step 3: Verify Migration Status
pac pages migrate-datamodel --webSiteId [WebSiteId-GUID] --checkMigrationStatus
Verify that all migration activities have completed successfully before updating the website data model version.
Step 4: Update Data Model Version
pac pages migrate-datamodel --webSiteId [WebSiteId-GUID] --updateDatamodelVersion --portalId [Portal-GUID]
This step completes the migration process and updates the website to use the Enhanced Data Model.
Revert to the Standard Data Model
pac pages migrate-datamodel --webSiteId [WebSiteId-GUID] --revertToStandardDataModel --portalId [Portal-GUID]
If required, you can roll back the migration and restore the website to the Standard Data Model.
Production Migration Recommendations
- Create a full copy of the production environment.
- Perform migration testing in the copied environment.
- Validate all customizations and integrations.
- Import managed solutions into production.
- Migrate nonconfiguration data.
- Update the data model version during a maintenance window.
- Perform post-migration validation.
Update Custom Columns on ADX Tables
Custom columns created on ADX metadata tables must be migrated to custom tables that integrate with the Enhanced Data Model architecture.
- Create a custom Dataverse table.
- Add required custom columns.
- Create relationships with Power Pages components.
- Migrate existing data.
Update Liquid Templates
Replace ADX table references with supported virtual table references or Power Pages objects.
{% assign app_weblinks = entities['adx_weblinks'] %}
Replace with:
{% assign app_weblinks = weblinks %}
Update FetchXML Queries
Update ADX table references to supported Power Pages component tables and virtual tables.
- Replace adx_webrole references.
- Use powerpagecomponent table.
- Use powerpagecomponenttype relationships.
- Validate all FetchXML queries after migration.
Update Workflows and Plugins
Custom workflows and plugins registered on ADX tables must be updated and re-registered against the appropriate Enhanced Data Model tables.
- Update entity references.
- Modify plugin code.
- Update workflow logic.
- Deploy and validate changes.
New Power Pages Admin Center
The redesigned Power Pages Admin Center introduces dedicated pages for Management, Security, Licensing, and Copilot experiences.
- Manage websites and analytics.
- Access licensing information.
- Review security dashboards.
- Switch between classic and modern experiences.
Best Practices
- Always test migration in a non-production environment.
- Create backups before migration.
- Validate Liquid templates and FetchXML queries.
- Review custom relationships and plugins.
- Perform migration during nonbusiness hours.
- Verify security settings after migration.
- Monitor website performance post-migration.
Summary
Migrating websites from the Standard Data Model to the Enhanced Data Model allows organizations to modernize their Power Pages environments, improve performance, simplify Application Lifecycle Management, and leverage the latest Power Pages capabilities. By following a structured migration process and validating customizations thoroughly, organizations can ensure a successful transition to the modern architecture.