Migrate SQL Server Reporting Services reports to Power BI

This article targets SQL Server Reporting Services (SSRS) report authors and Power BI administrators. It provides you with guidance to help you migrate your Report Definition Language (RDL) reports to Power BI.


It's only possible to migrate RDL reports. In Power BI, RDL reports are called paginated reports.

Guidance is divided into four stages. We recommend that you first read the entire article prior to migrating your reports.

  1. Before you start
  2. Pre-migration stage
  3. Migration stage
  4. Post-migration stage

You can achieve migration without downtime to your SSRS servers, or disruption to your report users. It's important to understand that no data or reports need to be removed. So, it means you can keep your current environment in place until you're ready for it to be retired.

Before you start

Before you start the migration, you should verify that your environment meets certain prerequisites. We'll describe these prerequisites, and also introduce you to a helpful migration tool.

Preparing for migration

As you prepare to migrate your reports to Power BI, first verify that your organization has a Power BI Premium subscription. This subscription is required to host and run your Power BI paginated reports.

Supported versions

You can migrate SSRS instances running on-premises, or on Virtual Machines hosted by cloud providers, like Azure.

The following list describes the SQL Server versions supported for migration to Power BI:

  • SQL Server 2012
  • SQL Server 2014
  • SQL Server 2016
  • SQL Server 2017
  • SQL Server 2019

Migration from Power BI Report Server is possible, too.

Migration tool

We recommend you use the RDL Migration Tool to help prepare, and migrate your reports. This tool was developed by Microsoft to help customers migrate RDL reports from their SSRS servers to Power BI. It's available on GitHub, and it documents an end-to-end walkthrough of the migration scenario.

The tool automates the following tasks:

  • Checks for unsupported data sources and unsupported report features
  • Converts any shared resources to embedded resources:
    • Shared data sources become embedded data sources
    • Shared datasets become embedded datasets
  • Publishes reports (that pass checks) as paginated reports, to a specified Power BI workspace (on a Premium capacity)

It doesn't modify or remove your existing reports. On completion, the tool outputs a summary of all actions completed—successful or unsuccessful.

Over time, the tool may be improved by Microsoft. The community is encouraged to contribute and help enhance it, too.

Pre-migration stage

After verifying that your organization meets the pre-requisites, you're ready to start the Pre-migration stage. This stage has three phases:

  1. Discover
  2. Assess
  3. Prepare


The goal of the Discover phase is to identify your existing SSRS instances. This process involves scanning the network to identify all SQL Server instances in your organization.

You can use the Microsoft Assessment and Planning Toolkit. Also known as the "MAP Toolkit", it discovers and reports on your SQL Server instances, versions, and installed features. It's a powerful inventory, assessment, and reporting tool that can simplify your migration planning process.


Having discovered your SSRS instances, the goal of the Assess phase is to understand any SSRS reports—or server items—that can't be migrated.

Only RDL reports can be migrated from your SSRS servers to Power BI. Each migrated RDL report will become a Power BI paginated report.

The following SSRS item types, however, can't be migrated to Power BI:

  • Shared data sources 1
  • Shared datasets 1
  • Resources, like image files
  • KPIs (SSRS 2016, or later—Enterprise Edition only)
  • Mobile reports (SSRS 2016, or later—Enterprise Edition only)
  • Report models (deprecated)
  • Report parts (deprecated)

1 The RDL Migration Tool automatically converts shared data sources and shared datasets—providing they're using supported data sources.

If your RDL reports rely on features not yet supported by Power BI paginated reports, you can plan to redevelop them as Power BI reports. Even if your RDL reports can migrate, we recommend you consider modernizing them as Power BI reports, when it makes sense.

If your RDL reports need to retrieve data from on-premises data sources, they cannot use single sign-on (SSO). Currently, all data retrieval from these sources will be done by using the security context of the gateway data source user account. It's not possible for SQL Server Analysis Services (SSAS) to enforce row-level security (RLS) on a per-user basis.

Generally, Power BI paginated reports are optimized for printing, or PDF generation. Power BI reports are optimized for exploration and interactivity. For more information, see When to use paginated reports in Power BI.


The goal of the Prepare phase involves getting everything ready. It covers setting up the Power BI environment, planning how you'll secure and publish your reports, and ideas for redeveloping SSRS items that won't migrate.

  1. Ensure the Paginated Reports workload is enabled for your Power BI Premium capacity, and that it has sufficient memory.
  2. Verify support for your report data sources, and set up a Power BI Gateway to allow connectivity with any on-premises data sources.
  3. Become familiar with Power BI security, and plan how you'll reproduce your SSRS folders and permissions with Power BI new workspaces.
  4. Become familiar with Power BI sharing, and plan how you'll distribute content by publishing Power BI apps.
  5. Consider using shared Power BI datasets in place of your SSRS shared data sources.
  6. Use Power BI Desktop to develop mobile-optimized reports, possibly using the Power KPI custom visual in place of your SSRS mobile reports and KPIs.
  7. Reevaluate the use of the UserID built-in field in your reports. If you rely on the UserID to secure report data, then understand that for paginated reports (when hosted in the Power BI service) it returns the User Principal Name (UPN). So, instead of returning the NT account name, for example AW\mblythe, the built-in field will return something like m.blythe@adventureworks.com. You will need to revise your dataset definitions, and possibly the source data. Once revised and published, we recommend you thoroughly test your reports to ensure data permissions work as expected.
  8. Reevaluate the use of the ExecutionTime built-in field in your reports. For paginated reports (when hosted in the Power BI service), the built-in field returns the date/time in Coordinated Universal Time (or UTC). It could impact on report parameter default values, and report execution time labels (typically added to report footers).
  9. If your data source is SQL Server (on-premises), verify that reports aren't using map visualizations. The map visualization depends on SQL Server spatial data types, and these aren't supported by the gateway. For more information, see Data retrieval guidance for paginated reports (SQL Server complex data types).
  10. Ensure your report authors have Power BI Report Builder installed, and that later releases can be easily distributed throughout your organization.

Migration stage

After preparing your Power BI environment and reports, you're ready for the Migration stage.

There are two migration options: manual and automated. Manual migration is suited to a small number of reports, or reports requiring modification before migration. Automated migration is suited to the migration of a large number of reports.

Manual migration

Anyone with permission to access to the SSRS instance and the Power BI workspace can manually migrate reports to Power BI. Here are the steps to follow:

  1. Open the SSRS portal that contains the reports you want to migrate.
  2. Download each report definition, saving the .rdl files locally.
  3. Open the latest version of Power BI Report Builder, and connect to the Power BI service using your Azure AD credentials.
  4. Open each report in Power BI Report Builder, and then:
    1. Verify all data sources and datasets are embedded in the report definition, and that they're supported data sources.
    2. Preview the report to ensure it renders correctly.
    3. Select Publish, then select Power BI service.
    4. Select the workspace where you want to save the report.
    5. Verify that the report saves. If certain features in your report design aren't yet supported, the save action will fail. You'll be notified of the reasons. You'll then need to revise your report design, and try saving again.

Automated migration

There are two options for automated migration. You can use:

  • The RDL Migration Tool
  • The publicly available APIs for SSRS and Power BI

The RDL Migration Tool has already been described in this article.

You can also use the publicly available SSRS and Power BI APIs to automate the migration of your content. While the RDL Migration Tool already uses these APIs, you can develop a custom tool suited to your exact requirements.

For more information about the APIs, see:

Post-migration stage

After you've successfully completed the migration, you're ready for the Post-migration stage. This stage involves working through a series of post-migration tasks to ensure everything is functioning correctly and efficiently.

Configure data sources

Once reports have been migrated to Power BI, you'll need to ensure their data sources are correctly set up. It can involve assigning to gateway data sources, and securely storing data source credentials. These actions aren't done by the RDL Migration Tool.

Review report performance

We highly recommended you complete the following actions to ensure the best possible report user experience:

  1. Test the reports in each browser supported by Power BI to confirm the report renders correctly.
  2. Run tests to compare report rending times in SSRS and Power BI. Check that Power BI reports render in an acceptable time.
  3. If Power BI reports fail to render because of insufficient memory, allocate additional resources to the Power BI Premium capacity.
  4. For long-rendering reports, consider having Power BI deliver them to your report users as email subscriptions with report attachments.
  5. For Power BI reports based on Power BI datasets, review model designs to ensure they're fully optimized.

Reconcile issues

The Post-migration phase is crucial for reconciling any issues, and that you address any performance concerns. Adding the paginated reports workload to a capacity can contribute to slow performance—for paginated reports and other content stored in the capacity.

For more information about these issues, including specific steps to understand and mitigate them, see the following articles:

Next steps

For more information about this article, check out the following resources:

Power BI partners are available to help your organization succeed with the migration process. To engage a Power BI partner, visit the Power BI partner portal.