Migration of Power BI Report Server On-Premises from older version a new

[tamiribas]

Hello,

A client is using the Power BI Report Server On-Premises version (January 2022).  They have 100 active reports on the server.

We have installed a new version of Power BI Report Server On-Premises  (May 2025) on a new machine.

We need to migrate all reports, schedules, and subscriptions.

Is there a guide for best practices?

Thank you,m

Tamir

[tamiribas]

Hi,

Thank you for the reply. Is this based on your experience?

Thank you,

Tamir

[Nasif_Azam]

If your question is for me, My answer is:

My first 3 options are based on my work experience and also my failure. So you can rely on those options to find the best practices.

If you found this solution helpful, please consider accepting it and giving it a kudos (Like) it’s greatly appreciated and helps others find the solution more easily.

Best Regards,
Nasif Azam

[Nasif_Azam · Accepted solution]

Hey @tamiribas ,

Migrating Power BI Report Server (PBIRS) from an older version (e.g., January 2022) to a newer one (e.g., May 2025) on a new machine requires a well-structured approach to ensure all reports, schedules, subscriptions, and configuration settings are retained accurately. Below is a guide outlining the best practices and steps to perform the migration safely and effectively.

Migration Strategy for PBIRS (On-Premises)

1. Pre-Migration Preparation

• Backup the PBIRS databases:

  • ReportServer

  • ReportServerTempDB
• Backup the encryption key using the Report Server Configuration Manager.

• Backup the ReportServer config files:

  • rsreportserver.config

  • rssrvpolicy.config

  • web.config (under Report Manager and Web Portal folders)

2. Install the New PBIRS (May 2025) on New Server

• Install the May 2025 version on the new machine.

• Open Report Server Configuration Manager.

  • Choose "Connect to an existing report server database".

  • Point to the backed-up ReportServer and ReportServerTempDB databases.

• Restore the encryption key using the .snk file backed up earlier.

• Ensure Web Portal and Web Service URLs are configured and accessible.

3. Transfer Custom Settings

• Manually compare and merge configurations from the old rsreportserver.config and other files into the new server (only if customized settings are needed).

• Reconfigure email settings, execution logs, and delivery extensions if any.

4. Validate Migration

• Log in to the web portal and check:

  • All 100 reports are present.

  • Data sources are correctly linked and functional.

  • Scheduled refreshes and subscriptions are retained.

• Run test subscriptions to verify delivery mechanisms.

• Check any custom branding or settings applied earlier.

Alternative: Use PBIRS Migration Scripts or PowerShell

If a full DB move isn’t viable (e.g., partial migration or report selection needed), you can:

• Use PowerShell scripts or Report Server Web Service endpoints to extract and redeploy reports.

  • Script options: Export-RsCatalogItems

  • Use RS.exe utility for command-line publishing.

For more information:

• Microsoft Docs – Migrate Report Server

• Microsoft Docs – Backup and Restore Reporting Services

If you found this solution helpful, please consider accepting it and giving it a kudos (Like) it’s greatly appreciated and helps others find the solution more easily.

Best Regards,
Nasif Azam