Power Platform Guidance | Migration to nhs.net

Power Platform Guidance | Migration to nhs.net

As part of the migration to nhs.net, any of your Power BI files, Power Apps and Power Automate Flows you would like to continue to access will need to be self-migrated. To understand how to do this and when, please use the information below.

Power BI

To migrate your Power BI reports and dashboards, you will need to carry out the following steps. For further guidance on how to carry out these steps, please consult our Power BI self-migrate pack

Personal Workspaces Only

If you have a personal workspace only and would like to migrate your personal reports/dashboards, below shows the following actions you need to carry out.

Ahead of your nhs.net Power BI licenses being provisioned (this license provisioning date will be communicated to you):

• Determine PBI reports/dashboards for Migration: Only reports/dashboards which you use should be migrated.
• Understand your Data Sources & Flows to determine how to update them post-migration.
• Export your Power BI reports from legacy NHSD Power BI.

 Once your nhs.net Power BI license have been provisioned, before switchover:

• Import your Power BI reports into your nhs.net Power BI.

After switchover:

• Update data sources and flows of your imported reports.

Shared Workspaces

To migrate your Power Apps and Flows, you will need to carry out the following steps. For further guidance on how to carry out these steps, please see the Power Apps/Automate self-migrate pack (to be added).

Ahead of your nhs.net Power BI licenses being provisioned (this license provisioning date will be communicated to you) :

• Record Workspace Information in your legacy NHSD Power BI including permissions.
• Determine PBI reports/dashboards for Migration: Only reports/dashboards which you use should be migrated.
• Understand your file permissions to replicate this in nhs.net.
• Understand your Data Sources & Flows to determine how to update them post-migration.
• Export your Power BI reports from your legacy NHSD Power BI.

Once your nhs.net Power BI license have been provisioned, before switchover:

• Recreate your shared workspaces in your nhs.net Power BI and update the workspace permissions.
• Import your Power BI reports into your nhs.net Power BI workspaces.

After switchover:

• Update File permissions where required.
• Update data sources and flows of your imported reports.

Power Apps & Flows

To migrate your Power Apps and Flows, you will need to carry out the following steps. For further guidance on how to carry out these steps, please see the Power Apps/Automate self-migrate pack here.

Ahead of your nhs.net licenses being provisioned(this license provisioning date will be communicated to you:

• Determine Power Apps and Flows for Migration: Determine the type of apps/flows and decide which ones should be migrated.
• Understand your Power App & Flows Components: Including any connections, custom connectors and gateways so you can update the apps/flows post-migration.
• Understand if your data sources are stored in Teams, or in SharePoint.
• Check for Custom Dataverse Tables that would have to be migrated to nhs.net and export these tables.
• Export your Power Apps & Flows from your legacy NHSD environment.

Once your nhs.net license has been provisioned, before switchover:

• Recreate your Power App & Flow Components: Recreate any connections, custom connectors and gateways.
• Import your Custom Dataverse Tables into the Power Platform environment in nhs.net.
• Import your Power Apps/Flows into the Power Platform environment in nhs.net.

After switchover, complete the following activities:

• Utilise any Power App & Flow Checkers to update any required connections to migrated files.

 Click here to return to the Migration Overview page.