Traditional reporting systems like SSRS have served enterprises well for years. However, with the rise of interactive dashboards and real-time insights, companies now require more dynamic and visually rich reporting solutions. This is where Power BI Report Server steps in.
This article provides a complete guide to help you understand the migration process, benefits, and a real-world use case where 2000+ reports were successfully migrated.

Real-World Use Case: 2000+ Reports Migration

Large-scale migrations are often viewed as high-risk, time-consuming projects. However, leveraging the right automation tools changes the math entirely.

The Benchmark: In a recent enterprise deployment, we successfully migrated over 2,000 reports in approximately 40 minutes using SSRS Reports Migration Wizard.

Why Organizations are Making the Switch

• Unified UX: Consolidate Power BI reports (.pbix) and paginated reports (.rdl) into a single portal.
• Enhanced Performance: Improved processing engines and scalability.
• Legacy Debt Reduction: Modernizing connection strings and centralizing data sources.
• Interactive Analytics: Moving beyond static tables to drill-through dashboards.

This use case clearly demonstrates that with the right strategy, even large-scale migrations can be executed efficiently.

Strategic Migration Workflow

To efficiently migrate SSRS reports to Power BI Report Server, follow this streamlined process:

Step 1: Select the Source

• Choose the SSRS/Poweer BI Report server or import a .SRMW file
• Ensure the source environment is accessible

Step 2: Select the Target

• Provide connection details for the Power BI Report Server
• Choose destination (same server/different server/folder)
• Validate connectivity

Step 3: Choose Report Items to Migrate

• Select reports, folders, datasets, and data sources
• Use filters for bulk selection

Step 4: Manage Folder Mapping

This step is available when “Rename target folders during migration” is enabled. It is useful for organizing and restructuring reports in the target environment.

• Rename folders during migration
  Example: Finance → Finance_New
• Migrate to a different folder name
  Example: Reports → Prod_Reports
• Consolidate multiple folders into one
  Sales Asia, Sales EU, Sales NA → Sales

Step 5: Update Data Source Connection Strings

• Fetch all data sources used in selected reports
• Review and edit connection strings
• Update credentials manually
• Optionally convert embedded sources to shared sources
• Changes apply only after migration completes

Step 6: Review Changes

• Verify summary of new, updated, and skipped items
• Export summary if needed
• Confirm configurations before execution

Step 7: Finish and Validate

• Execute migration
• Review logs and migration summary
• Validate data accuracy and report performance
• Rerun process if needed

Installation

SSRS Reports Migration Wizard can be installed as an extension to:

1. Visual Studio 2017, Visual Studio 2019, Visual Studio 2022 & Visual Studio 2026.
2. SSMS 18, 19, 20, 21, 22
3. Standalone tool.

Standalone Usage

Don’t use Visual Studio? You can still run the wizard as a standalone tool:

Launch SSRS.Reports.Migration.Wizard.exe.

Download the .vsix from here.

Rename the .vsix to .zip and extract it.

FAQ

Conclusion

To successfully migrate SSRS reports to Power BI Report Server, organizations must adopt a structured, scalable, and automation-driven approach. As demonstrated in the real-world case of migrating 2000+ reports, it is possible to achieve seamless transformation with minimal disruption and post migration efforts.

By upgrading to Power BI Report Server, businesses gain access to modern analytics, interactive dashboards, and a unified reporting platform that drives better decision-making.

Read full customer testimonial on the Visual Studio Marketplace.

Watch a quick demo

The post Migrate SSRS Reports to Power BI Report Server appeared first on AzureOps.

Traditionally, administrators had to download each report manually from the Report Manager portal, or write complex scripts using SSRS SOAP APIs. Both approaches are time-consuming and prone to errors. Fortunately, there is now an easier way to achieve this: using the SSRS Reports Migration Wizard.

What Is the SSRS Reports Migration Wizard?

The SSRS Reports Migration Wizard is a tool from AzureOps designed to help you migrate SSRS content (native mode) between servers or to/from an SRMW export file.
It supports migrating:

• Folders
• Reports
• Shared datasets
• Shared data sources
• Subscriptions
• Roles

The wizard gives you a guided interface to select exactly which objects to migrate, and optionally adjust connection strings along the way.

When to Use Export + Import via SRMW File

Using an export file gives you flexibility:

• You can create a backup snapshot of your reports/datasets/data sources
• You can move content offline — export on one server, then import later on a different server
• It helps in server upgrades, consolidation, or reorganizing your SSRS environments

If you prefer a direct server-to-server migration, that’s also supported by the wizard. But export/import via file is safer and useful, especially when network access or permissions between servers is constrained.

Step-by-Step: Exporting SSRS Items to SRMW File

Here is a step-by-step walkthrough of how to carry out the export. You can follow along with the video, or use these instructions with screenshots in your own environment.

1. Launch the Migration Wizard

• From SQL Server Management Studio (SSMS), open the SSRS Reports Migration Wizard.
• (If installed as an extension, you’ll find it under the Tools menu.)

2. Start the Export Process

• Click Next to begin.
• Enter the source SSRS web service URL (e.g. http://yourservername/reportserver) along with domain credentials.
• Click Connect to load the contents of that SSRS instance.

3. Select the Export File Target

• On the next screen, choose the SRMW file option as your export target.
• Browse to the folder where you want the export file to be saved.
• Specify a file name (for example, MySSRSExport.srmw).
• Click Next to continue.

4. Choose SSRS Items to Export

• You’ll see a tree view of all SSRS objects: folders, reports, datasets, data sources.
• Check the boxes next to the items you want to export.
• After your selection, click Next.

5. (Optional) Update Data Source Connection Strings

• On the next screen, you can update the connection strings and credentials for data sources.
• These settings will be baked into the SRMW file and used when you later import the content.
• If you don’t need to change anything, you can skip this.
• When ready, click Next (or Finish, depending on wizard layout).

6. Review & Confirm

• The wizard will show a summary of what will be exported.
• Confirm your selections and click Finish (or Export) to start the process.

7. Complete Export & Verify

• The wizard runs, exporting all chosen items into your SRMW file.
• When it completes, open File Explorer and navigate to the export folder you chose.
• You’ll see the .srmw file.
• (Optionally) You can unzip or inspect its contents to verify that your reports, datasets, and sources are included in the proper folder structure.

What’s Inside the SRMW File & How It Helps

The SRMW file is essentially a packaged archive that contains:

• Report definition files (RDLs)
• Dataset definitions
• Data source metadata (connection strings, credentials)
• The folder hierarchy (to preserve navigation/organization)
• Standard subscriptions definition, etc.

When you later run the wizard’s Import mode, the tool reads this file and recreates the selected SSRS items into the target server.

Using this intermediate file gives you:

• A portable, versionable package
• A safety buffer (you can inspect or edit before import)
• The ability to stage/migrate content in controlled stages

Pro tips:
1. Test first with a limited set of reports to ensure everything works as expected.
2. Double-check your data sources — mismatches or missing credentials are common issues.
3. Use clear naming conventions for your export file (with timestamp) so you know which export is which.
4. Keep a backup of your export file in a safe location.
5. Make sure the target SSRS server is compatible in terms of version and features.
6. Check permissions: the account you use must have sufficient rights on the source SSRS items.
7. Learn how to migrate SSRS report server items from one report server to another.

The post Download all SSRS Reports from Report Server appeared first on AzureOps.

In this case study, we examine how Leidos, USA , completed an AWS SSRS migration involving more than 80+ SSRS reports, despite having no connectivity between the source SSRS server and the AWS environment.

Background: AWS SSRS Migration with Network Isolation

Leidos was modernizing its infrastructure by moving workloads from an on-premises data center to AWS. Their legacy SSRS server (Windows Server 2016) was scheduled for decommissioning.

Over the years, the server had accumulated:

• 80+ SSRS reports
• Deep folder hierarchies
• Shared data sources

Due to security policies, the on-prem SSRS environment and AWS were completely disconnected, making a traditional SSRS migration approach impossible.

This made the project a textbook example of a disconnected SSRS migration.

Key Challenges in Disconnected SSRS Migration

• No direct network access between on-prem SSRS and AWS
• Inability to use live source-to-target SSRS migration
• Risk of missing reports, folders, or shared data sources
• Manual redeployment not feasible for large SSRS estates
• Need for a safe backup before decommissioning

Solution: File-Based SSRS Migration to AWS

To address these challenges, Leidos used SSRS Reports Migration Wizard in Standalone Mode, leveraging its offline / file-based SSRS migration capability.

This approach is ideal for:

• AWS SSRS migration
• Air-gapped or disconnected SSRS environments
• Secure enterprise networks

AWS SSRS Migration Process (Step-by-Step)

Step 1: Export SSRS Reports from On-Prem Server

On the source SSRS server, the tool:

• Automatically discovered reports, folders, and shared data sources, subscriptions, roles etc.
• Displayed the full SSRS hierarchy for validation
• Exported all selected items into a single migration file

During export:

• Individual .rdl files were generated for each SSRS report
• Folder structure and metadata were preserved

This created a complete offline SSRS backup, a key requirement in regulated environments.

Step 2: Transfer Migration File to AWS (Disconnected Network)

Since the environments were disconnected:

• The migration file was securely transferred using approved methods
• No firewall changes or temporary network access were required

This step highlights the core benefit of disconnected SSRS migration to AWS.

Step 3: Import SSRS Reports into AWS Environment

On the AWS-hosted SSRS server:

• The migration file was imported
• Folder hierarchy and shared resources were recreated
• Data source connections were updated for AWS databases

After import, all SSRS reports were available for validation.

AWS SSRS Migration Results

• 80+ SSRS reports successfully migrated to AWS
• No network connectivity required between environments
• Folder hierarchy and report dependencies preserved
• Minimal downtime
• No manual report recreation

The migration was completed smoothly despite being a fully disconnected SSRS migration.

Additional Benefit: SSRS Backup and Disaster Recovery

An unexpected advantage of the file-based approach was backup:

“The tool creates .rdl files for each report… making it an easy way to back up SSRS reports, data sources, and folders.”

This makes the solution useful not only for AWS SSRS migration, but also for:

• SSRS backup
• Disaster recovery
• Compliance and audit scenarios

Why This Approach Works for AWS SSRS Migration

• Designed for disconnected and air-gapped networks
• Supports offline SSRS migration to AWS
• Preserves full SSRS hierarchy
• Generates reusable .rdl files
• Suitable for enterprise security requirements

Read full customer testimonial on the Visual Studio Marketplace.

Watch a quick demo

The post SSRS Migration Case Study: Migrating SSRS Reports in a Disconnected Environment appeared first on AzureOps.

What Is SSRS Reports Migration Wizard?

SSRS Reports Migration Wizard is a tool that enables you to:

• Migrate reports, shared datasets, and shared data sources
• Copy subscriptions (standard and data-driven)
• Review and update connection strings and credentials
• Migrate between servers, folders, or environments
• Export and import SSRS items using a lightweight .SRMW file format
• Perform offline review and validation before actual migration

The wizard is available as a Visual Studio extension and as a standalone tool.

Prerequisites:
Before Migrating SQL Server Reports
1. You have access to both source and target SSRS servers.
2. Your user account has:
-at least Browser role on the source–
-at least Publisher role on the target
If you’re unsure how to grant access, follow the instructions in the Granting Access Guide.

Use Cases

• Migrating from dev to test/prod environments
• Consolidating multiple SSRS servers
• Backing up and archiving SSRS artifacts
• Migrating from the old SSRS report server to the new server.
• Migrate SSRS reports to Power BI report server.

Step-by-Step SSRS Report Migration Process

Follow the below steps to achieve SSRS report migration from one server to another.

Step 1: Select the Source

Choose your source SSRS server or a .SRMW file created from a previous export.

Step 2: Select the Target

Provide connection details for the destination SSRS server. You can migrate to a different server, or a different folder on the same server.

Step 3: Choose Report Items to Migrate

Select specific folders, reports, datasets, and data sources using a tree view. Filters and checkboxes make large-scale selection easy.

Step 4: Manage Folder Mapping

This step is available only when Rename target folders during migration is enabled. Use this screen to define how source folders should be created in the target environment.

Step 5: Update Data Source Connection Strings – Migrating SSRS Data Sources

SSRS Reports Migration Wizard includes an optional step to update data source connection strings during the migration process. This is particularly useful when migrating reports and datasets from a source server to a target server that uses different connection details.

Fetch Data Sources

On this screen, click the Fetch Data Sources button. The wizard will scan the selected SSRS items (from the previous screen) and populate a grid with all connections that can be updated.

Each row represents a unique connection used by your reports or shared data sources.

View and Manage Connections

The grid displays the Extension, Connection String, and Credential Retrieval method for each data source. Click the Edit link in the Manage column, which allows you to modify the connection.

Convert to shared data sources if connection exists – If this option is selected, the wizard will attempt to convert embedded data sources in reports to shared data sources during deployment, provided a shared data source with the same connection details is available in the selected SSRS items for deployment.

Update Properties

When you click Edit, a new dialog box appears (labeled “Manage Connection Properties”). Here you can:

• Review the Shared Data Source(s) using this connection and Report(s) using this connection as an embedded data source.
• Modify the Connection String.
• Specify Credentials (e.g., Windows credentials or a user name and password) under “Log into the data source”.
• Click Save to apply the changes.

Important Notes

• The wizard cannot retrieve passwords from embedded or shared data sources on the source report server. The wizard will guide you to convert them ot shared data sources and provide credentials.
• The Dependent Objects shown in the grid are those that have a connection embedded within them. These objects are directly using this connection.
• The changes you make are not committed to the target server until the wizard completes the migration.
• If no connections are found for the selected items, a message box will inform you that there are no connections available for update.

Step 6: Review Changes

The wizard shows a migration summary with new, changed, or skipped items. You can export this list or proceed with the migration.

Step 7: Finish and Validate

Once migration is complete, a final summary screen shows migrated item counts and logs. You can rerun this process anytime.

Installation

SSRS Reports Migration Wizard can be installed as an extension to:

1. Visual Studio 2017, Visual Studio 2019, Visual Studio 2022 & Visual Studio 2026.
2. SSMS 18, 19, 20, 21, 22
3. Standalone tool.

Standalone Usage

Don’t use Visual Studio? You can still run the wizard as a standalone tool:

1. Download the .vsix from here.
2. Rename the .vsix to .zip and extract it.
3. Launch SSRS.Reports.Migration.Wizard.exe.

Pro tips:
1. Learn how to export all SSRS objects from the report server using SSRS Reports Migration Wizard.
2. Learn how to migrate SSRS Reports to Power BI Report Server.

The post How to Migrate SSRS Reports from One Server to Another (Step-by-Step) appeared first on AzureOps.