Last updated: November 14, 2026
Follow the wizard from top to bottom and change only the settings relevant to your migration. Most standard migrations use these six steps:
- Choose the source.
- Choose the target.
- Select the items to migrate.
- Review connections and optional settings.
- Review the migration summary.
- Run the migration and review the result.
Features such as folder mapping, data source updates, subscriptions, comparison reports, and command-line automation are optional. Use the relevant sections only when your migration requires them.
Choose Source #
- Choose the source type: either an SSRS Report Server or an SRMW file.
- Enter the Report Server URI (for example,
https://localhost/ReportServer). - Select the authentication method:
- Use Current Domain Credentials — Connect using the Windows domain credentials of the account running the wizard.
- Use Specified Domain Credentials — Connect using the domain account and password you enter, such as
domain\username.
- Click Next.
You can select a saved connection profile associated with a report-server URL and username. Selecting a profile restores its authentication choice and username. A password is restored only if you chose to remember it; otherwise, enter it when prompted. Only successfully connected profiles are saved. The Next button waits for the connection attempt to finish and checks the required credentials. If you change the connection settings after connecting, the connected state resets and you must connect again before proceeding.

Choose Target #
- Choose the target type: another SSRS Report Server or an SRMW file.
- Enter the target server URI.
- Provide authentication details as needed.
- Click Next.
You can select a saved connection profile associated with a report-server URL and username. Selecting a profile restores its authentication choice and username. A password is restored only if you chose to remember it; otherwise, enter it when prompted. Only successfully connected profiles are saved. The Next button waits for the connection attempt to finish and checks the required credentials. If you change the connection settings after connecting, the connected state resets and you must connect again before proceeding.

Select SSRS Items to Migrate #
- Browse and select supported SSRS catalog items, including folders, reports, linked reports, resources, datasets, and data sources.
- The tool displays the SSRS folder hierarchy as a tree view.
- The right panel shows object counts by type.
- Subreports are not automatically discovered or selected. Select each subreport explicitly when you want it migrated.

Choose the Migration Options You Need #
Enable only the features relevant to your migration:
- Migrate subscriptions — Include subscriptions. Matching subscriptions already on the target are skipped. Missing shared schedules may be created when shared-schedule migration is supported, selected, and the required permissions are available.
- Migrate roles — Include security roles at folder, report, dataset, and data source level. Corresponding users and groups must be recognized on the target for their role assignments to be applied.
- Migrate parameters and defaults — Include report server-side report parameters and apply their default values when available.
- Rename target folders during migration — Enable the Manage Folder Mapping screen.
Compare Catalog #
Use Compare Catalog on the Select SSRS Items screen to compare either the currently selected catalog items or the full source catalog against the target. The dialog offers the selected-items option first and selects it by default when the tree contains selected items. If nothing is selected, full-catalog comparison is selected.
Choose Comparison Metadata
Select role assignments, subscription counts, and report parameter defaults as comparison metadata. Role comparison is directional for delta selection: source assignments missing on the target can trigger a difference, while extra target assignments are retained and do not trigger a delta by themselves. Subscription comparison is count-only; definitions are not compared. Parameter defaults can be compared when selected. RDL/report definitions are not compared.
- Roles — Compare source role assignments against the target; missing target assignments can trigger a difference.
- Subscriptions — Compare subscription counts only, not subscription definitions.
- Parameter Defaults — Compare report parameter defaults when selected.

Understand Comparison Results
The Catalog comparison results window displays the expected target path, source and target modified dates, selected metadata comparisons, target connection status, and an overall result for each item.
- No detected differences — The catalog item and selected metadata match.
- Differences found — One or more selected comparison attributes differ.
- Target item missing — The expected catalog item does not exist on the target. Source-side metadata counts are shown where available to indicate what migration is expected to create.
- Could not verify — The wizard could not complete the comparison for that item.
Comparison scope: Comparison evaluates catalog item presence and paths together with the selected metadata. It does not compare RDL/report definitions or report content. Modified dates are informational and are not a guarantee of content equality. If an SRMW file is the source, source modified dates come from Windows file timestamps and may differ from the original SSRS dates.
After reviewing the comparison, use the delta-selection button. It displays how many items it will select, updates only the migration-tree selection, and closes the comparison window; it does not start migration. Items with differences or that could not be verified are selected. Matching items remain unselected. Review the resulting selection before continuing.
Manage Folder Mapping #
This step is available only when Rename target folders during migration is enabled. Use it to define how source folders are created in the target environment.

How It Works #
- Each selected root folder is listed with its target folder name.
- The Target Folder column is editable.
- By default, the target folder name matches the source folder name.
Supported Scenarios #
- Rename folders during migration —
Finance→Finance_New - Migrate to a different folder name —
Reports→Prod_Reports - Consolidate multiple folders into one target folder —
Sales Asia,Sales EU,Sales NA→Sales
Folder Rename Behavior #
- Only top-level source folders can be renamed or remapped. Nested folders and catalog items follow their parent folder mapping.
- During migration or SRMW file export, subscription paths and supported internal references are adjusted to follow the mapped folder structure. Nested reports, datasets, data sources, and subscriptions follow their parent folder.
If folder renaming is not enabled, the original folder structure is preserved.
Update Data Source Connections #
Use this step to update data source connection strings during migration, for example when the target uses different connection details or when stored credentials need to be configured.
How It Works #
Click Fetch Data Sources. The wizard scans the selected SSRS items and populates a grid with connections that can be updated.

- Extension — Data provider type, such as SQL, OLEDB, or Oracle.
- Connection String — Current connection string.
- Credential Retrieval — Authentication method: Integrated, Store, None, or Prompt. Store appears in red when the password needs to be updated.
- Embedded DS — Number of reports using the connection as an embedded data source.
- Shared DS — Number of shared data sources using the connection. A count of 0 appears in red.
- Manage — Click Edit to view or modify connection details.
Convert to shared data sources if connection exists attempts to convert embedded data sources to shared data sources during deployment. Conversion occurs only when a matching shared data source exists with the same Extension, ConnectionString, CredentialRetrieval, Windows or database credentials (including WindowsCredentials and ImpersonateUser), and UserName when stored credentials are used.
Click Edit to open Manage Connection Properties. You can review shared data sources and reports using the connection, modify the connection string, specify Windows or database credentials, and add a shared data source when none exists.
- DataSourceName — For example,
SalesDS. - DataSourcePath — For example,
/Shared Data. - Click Save to apply the changes.

Source data-source credentials: SSRS does not expose stored source passwords for migration. Re-enter them in Manage Connection Properties when required. For storage and protection details, see Security & Compliance.
Changes are not committed to the target server until the wizard completes the migration. If no connections are found, the wizard reports that there are no connections available for update.
Manage File Share Subscription Credentials #
If Migrate subscriptions is selected, the wizard scans the source SSRS instance for subscriptions using the File Share delivery method.
File Share subscriptions: Enter the Windows account password required to write to the destination share in this screen. This is separate from the source data-source credentials described above.

- Each row represents a unique Windows account used by file-share subscriptions.
- The shared folder path is shown for reference.
- The Password column must be filled in manually.
- Click the Subscriptions hyperlink to view reports associated with that user.
After credentials are entered, the wizard applies them when creating subscriptions on the target SSRS server. This step applies only to File Share subscriptions; email and other delivery methods can be skipped.
Review and Confirm #

The review screen shows source and target details, per-item New or Update actions, source and target paths, inline item counts, and an option to export the migration item list. Summary totals classify items by whether they exist at their mapped target path; they are not a full comparison of server-side settings.
Understand New and Update Migration Behavior #
The migration summary labels each selected catalog item as New or Update based on whether a corresponding item exists at its mapped target path.
- New: The corresponding item was not found at the destination path and is expected to be created on the target report server.
- Update: A corresponding item already exists at the destination path. The wizard sends the selected source item to the existing target path as an update; the source item’s migrated definition or properties update the corresponding target item. This is an in-place update, not a side-by-side copy.
Important scope note: The New or Update label identifies whether a catalog item exists at its mapped target path; it does not report every server-side setting. The migration workflow does not include a cleanup step for deleting target-only catalog items. Review the target catalog after migration and keep an appropriate backup before making production changes.
Review every item marked Update, confirm the target server and folder mapping, and remove items from the selection or change the mapping if you do not intend to update an existing target item.
Before You Migrate (Checklist) #
- Selected the correct source and target.
- Selected all intended catalog items, including reports, linked reports, resources, data sources, datasets, and subscriptions.
- Optionally updated connection strings and provided required credentials.
- Reviewed the migration summary for New versus Update items.
Script Button #
Before clicking Finish, use Script to generate a ready-to-run command-line script from the current wizard selections.
- Copy to Clipboard — Copies the generated script for use in a terminal, Task Scheduler job, or CI/CD pipeline configuration.
- Save to File — Saves the script as a
.batfile.
The generated script includes the current source, target, selected items, folder mapping, and migration options. If you used the delta-selection button before generating the script, it uses the items currently selected after that delta-selection step. If you change the selection, generate a new script to reflect the updated items.
Security: Follow the Automation security guidance when handling command-line credentials.
See the Automation & Command-Line Reference for full parameter documentation and examples.
Click Finish to start the migration.
Migration Results #

When migration completes, the results window displays overall Success and Error counts and a per-item table with date/time, item path, status, and details. Use status and item-type filters, failed-only view, filtered export, and full-trace details. Open full log provides the separate chronological log.
- Use the status and item-type filters to narrow the results.
- Enable Failed only to show unsuccessful or partially completed items.
- Click Export filtered to export the currently filtered details.
- Click an item’s status or details to open the complete error message and diagnostic trace without truncation.
- Use Open full log for the chronological, line-by-line migration log.
- Click Restart to open a fresh wizard while keeping the completed results window available.
For SOAP HTTP 500 errors, retain the full item trace and use the source/target identification, operation, endpoint, and client-local/UTC timestamps where available to locate the corresponding entry in the matching SSRS Report Server logs. Server log timestamps may use a different time zone. See the Troubleshooting Guide.
Verify Target #
Use Verify target after migration as a separate, on-demand operation to check the items currently selected in the migration tree against the target report server. The Target verification results window checks those items and supported metadata; it does not automatically alter the migration-tree selection. This is distinct from the pre-migration Catalog comparison results flow.
On the target-verification results screen, you can test visible target shared data sources and preview visible target reports on demand. These actions are available in the trial version, appear only in post-migration verification, and require an SSRS report-server target rather than an SRMW-file destination.

On the verification results screen, click Test visible target data sources to test visible target shared data sources on demand. Use the report-preview action to preview visible target reports. These actions are available in the trial version. Connection-test results depend on the provider/driver configuration available to the target report server.
Data-source tests depend on the provider/driver and connectivity available to the target report server. Report preview runs using parameters and credentials SSRS can resolve from saved/default settings. Reports requiring unavailable interactive parameter values or credentials may not run. Preview execution time depends on report/query performance and uses report-server and data-source resources. Preview is a test, not a guarantee that every user workflow or subscription will succeed. These actions are unavailable when the destination is an SRMW file.
Glossary of Terms #
| Term | Meaning | Example |
|---|---|---|
| SRMW File | A migration package created by the SSRS Reports Migration Wizard. It stores metadata about reports, datasets, data sources, subscriptions, and shared references, allowing migration without a live SSRS server. | UATserver.srmw |
| Shared Data Source | A reusable SSRS data connection. Multiple reports and datasets can share it. | AdventureWorks2017 |
| Embedded Data Source | A data connection defined inside a single report or dataset. It can be converted into a shared data source during migration if a matching one exists. | Company Sales report using AdventureWorks connection |
| Dependent Objects | SSRS items such as reports and datasets that use a specific data source. | Company Sales, Customer Internet Sales |
| Connection String | Defines the database server and catalog that SSRS connects to. | Data Source=sqldev.ud3d.com,1113;Initial Catalog=AdventureWorks2017 |
| Credential Retrieval | Defines how SSRS gets credentials: None, Integrated, Store, or Prompt. | Store |
| Windows Credentials | Indicates whether stored credentials are Windows domain credentials such as DOMAIN\User rather than SQL/database credentials. | False (database username and password) |
| Impersonate User | Tells SSRS to impersonate the specified user when connecting to the data source, usually with Windows credentials. | False |
| UseOriginalConnectString | Controls whether the original connection string is retained when migrating/deploying. If True, the original value is used; if False, the updated value is used. | True |
| OriginalConnectStringExpressionBased | Indicates whether the original connection string was an expression instead of a fixed string. | =Parameters!ServerName.Value |
| Subscription | A scheduled task that delivers reports automatically. Standard Subscription uses fixed parameters/credentials; Data-Driven Subscription uses dynamic recipients, parameters, and destinations. | — |
Limitations #
- Subscription migration and successful delivery are separate outcomes. A subscription may be created on the target but fail when it runs if its data-source, file-share, or delivery credentials and dependencies are not valid on the target. Validate each migrated subscription before enabling production schedules.
- For supported report-server modes, see Prerequisites.