This page provides details of the workloads that will need to manually moved from the user’s current @trust.nhs.uk account to their @NHS.net account.
Self-Migrated Workloads
Power BI dashboards
Power BI migration to the new environment will be a self-migrated process, where users are responsible for moving their own reports, dashboards, datasets, and dataflows. We will provide detailed guidance, documentation, and tools to assist users in exporting, importing, and reconfiguring their content, including security settings and data source connections. This approach allows users to manage their migration at their own pace, while ensuring they can address unique configurations, with support available to resolve any issues during the transition.
Follow steps to migrate Power BI reports and dashboards.
Follow steps to migrate Power BI reports and dashboards.
Power Apps and Power Automate
The migration of Power Apps and Power Automate to the new environment will also follow a self-migrated process, where users are responsible for moving their own apps, flows, and related components. We will provide detailed guidance, documentation, and tools to assist users in exporting and importing their Power Apps and flows, as well as reconfiguring connections, permissions, and data sources. This self-driven migration allows users to tailor the process to their specific needs, with support available to help address any issues and ensure a smooth transition to nhs.net.
Follow steps to migrate Power Apps and Automate.
Follow steps to migrate Power Apps and Automate.
MS Forms
Microsoft Forms will follow a similar self-migrated process to the NHS.net environment. We will provide step by step instructions on how to export and import Microsoft Forms and responses.
Follow steps to migrate MS Forms.
Follow steps to migrate MS Forms.
Bookings and Shifts
Transitioning Booking and Shifts to NHS.net will be a self-migrated process where users are responsible for exporting and importing shift schedules to NHS.net. Before you migrate your Shifts and Bookings to NHS.net you must make sure that the NHS.net domain, teams and team member exist. It is then a three-step process to migrate the bookings and shifts. Prior to switchover day you will need to export the shift schedules for a date range and modify the username(s) of users. After switchover, you will then need to import the relevant schedules to the central tenant.
Follow steps to migrate Booking and Shifts.
Follow steps to migrate Booking and Shifts.
Organisation-led Workloads
Intune
LAs will be required to transition their Intune into NHS.net. Detailed step-by-step instructions and support will be provided to guide you through exporting and importing Intune configurations and settings.
Follow steps to migrate Intune
Follow steps to migrate Intune
Teams Rooms
Teams Rooms will follow a similar LA led process. This will involve re-registering Teams Rooms devices to the NHS.net environment and updating any associated configurations, such as meeting settings, device profiles, and licenses. Guidance will be provided throughout the process, ensuring a smooth transition for all Teams Rooms setups.
Follow steps to migrate Teams Rooms
Follow steps to migrate Teams Rooms
Teams Voice
Teams Voice will follow LA led transition to the NHS.net environment. This includes transitioning phone numbers, call queues, auto attendants, and associated policies to the target environment. Step-by-step instructions will be provided to help you reconfigure settings and ensure that all Teams Voice features, such as call routing and voicemail, are fully functional after migration.
Follow steps to migrate Teams Voice
Follow steps to migrate Teams Voice