Before you start: Make sure the migration machine can reach both the source and target report servers and that your account has the permissions required for the migration features you plan to use. The wizard supports SSRS Native mode and Power BI Report Server; SharePoint mode is not supported.
Last updated: November 14, 2026
System Requirements #
- Windows: Windows 10 or later recommended, or Windows Server.
- .NET Framework: 4.7.2 or later.
- Report-server access: Connectivity to both the source and target SSRS / Power BI Report Server.
- Subscriptions: SQL Server Agent must be running on the SQL Server instance hosting the target ReportServer database when migrating and executing scheduled subscriptions.
Network and Report Server URL #
The migration machine must be able to reach the configured report-server web-service endpoint. Your environment may use HTTP or HTTPS and a custom port.
- Example web-service URL:
http://<server-name>/ReportServer - Example portal URL:
http://<server-name>/Reports - Make sure firewalls or proxies allow access to the configured endpoints.
Find the Report Server Web Service URL #
On the machine where SSRS is installed, open Report Server Configuration Manager, connect to the SSRS instance, and select Web Service URL. Copy the configured URL shown there.

If you do not have access to Configuration Manager, try opening http://<server-name>/reportserver in a browser. For HTTPS environments, use the configured https:// URL.
The URL can also be checked in RSReportServer.config under the Reporting Services installation directory by looking for the <UrlRoot> setting, when present.
Required Permissions #
The permissions required depend on the migration task. SSRS site-level system roles and item-level catalog roles are separate. A system role does not grant access to catalog folders. The account needs the required effective item-level role on the exact parent folder of each item; check inheritance and folder-specific security overrides.
| Migration task | Source | Target |
|---|---|---|
| Reports, folders, datasets, data sources | Browser | Publisher; update access may be required when an existing item is overwritten |
| Standard or data-driven subscriptions | Browser + System User | Content Manager |
| Shared schedules | System User with required schedule permissions | System Administrator |
| Roles and permissions | System Administrator | System Administrator |
| Linked reports | Browser on the parent report folder | Publisher |
| Full migration | Content Manager + System Administrator | Content Manager + System Administrator |
If access is restricted to specific folders, check the effective item-level role on the exact parent folder. If inheritance is disabled, inspect relevant folder permissions individually. When an existing target dataset may be overwritten, the account may also need update permission. A System Administrator site role alone does not grant catalog-folder permissions.
Shared Schedule Permissions and Optional Migration #
Shared schedules are system-level SSRS objects and require permissions beyond ordinary folder access. The source account needs System User with the permissions required to read the shared schedules. The target account needs System Administrator to create shared schedules. Confirm that these permissions are granted on the respective report servers before enabling shared-schedule migration.
Where the wizard offers the option to continue without shared-schedule migration, you can leave shared schedules out and proceed with the other supported migration tasks. Do not assume that shared schedules will be created on the target when this option is not selected or the required permissions are unavailable. Review and configure the required schedules on the target separately.
Target Data-Source Connection-Test Requirements #
The verification results screen can test visible target data sources on demand when the migration target is an SSRS report server. Connection tests depend on the database provider and driver configuration available to the target report server. Install and configure the provider/driver required by each data source on the target report-server environment, and confirm that the target can reach the database endpoint with the configured authentication method.
A successful connection test confirms connectivity for that test; it does not guarantee that every report query, stored procedure, or subscription will execute successfully. Target verification and target data-source testing are not available when the migration target is an SRMW file.
Authentication and Account Access #
- Use an account that is trusted and authorized by the report-server environment.
- Make sure the account is valid and its password has not expired.
- Test access by opening the Report Server URL directly in a browser from the migration machine.
- For cross-domain migrations, confirm that the account is trusted and authorized on the relevant report server.
Grant Access When Required #
If the migration account does not have the required permissions, grant access from the SSRS Web Portal.
Item-Level Permissions #
- Open
http://<server-name>/Reports. - Open the Home folder or the folder you need to migrate.
- Select Manage → Security.
- Add the required group or user and assign the appropriate item-level role.
Site-Level Permissions #
- Open the SSRS Web Portal and select Site Settings → Security.
- Add the required group or user.
- Assign System User for supported subscription and shared-schedule operations, or System Administrator when the migration requires system-level administration such as role migration.
Tip: If you encounter a permission-related error, first compare the migration task with the permissions table above. For a specific error, see the Troubleshooting Guide.