Source server must be native mode using Windows authentication. (We are working on support for SharePoint integrated mode and other authentication schemes.)

Permissions and roles from source server are not backed up o Configuration in source server is not backed up.

Reports and other artifacts in deeply nested subfolders may not be backed up. This is due to Windows OS restriction on the maximum length for the full path of the backup files and folders. (We are working towards a solution.)

Linked reports are not support in SharePoint mode, hence not backed up.

Database connection to source server catalog is made using Windows Integrated credentials of the user running the tool.

Target server

Target server must be SharePoint integrated mode. (We are working on support for native mode.)

The web application must be using Windows classic authentication mode. (We are working on support for other authentication schemes.)

Target server must be correctly configured. Target document library and folder must be created. For SSRS 2012, service application must be created and configured.

The owner of Reporting artifacts after migration is set to the user who performed migration. (We are working towards a solution.)

Subscription owners are set after they are migrated. If the owner does not have CreateAlerts/ManagedAlerts permission, the operation will fail.

Report parts are not linked correctly to the Report. (We are working towards a solution.) o Database connection to target server catalog is made using Windows Integrated credentials of the user running the tool.

For a walkthrough of RSMigrationTool (command-line) and RSMigrationUE (GUI tool), list of content types migrated, and information about supported migration scenarios, see the following article.

For a sample Reporting Services RSS Script that copies content items from one SSRS report server to another, and supports both SharePoint mode and Native mode report servers, see the following article. The article also has a description of the sample that includes supported scenarios, required permissions, parameter descriptions, examples, and more.

1. Command-line tool (RSMigrationTool.exe):RSMigrationTool.exe [-n <native_report_server_url>] -i <native_report_server_instance> [-h] -f <migration_metadata_files_folder> [-p <password>]
-n Native report server url (e.g. http://<server>/reportserver). Optional if native instance name is specified. You should specify this option if WMI does not return the correct url.
-i Name of the native report server instance. Migration tool will use WMI to connect to the remote instance. If the connection cannot be made, native report server url must be specified, and passwords and history snapshots will not be backed up.
-h Report history will be exported. Please note that migrating report history requires direct modification to data in report server catalog and is not publicly supported. Backing up the catalog before migration and verifying correctness of the reports after migration are strongly recommended.
-f A folder where the files are to be stored. The folder will be created if it doesn't exist.
-p Password that will be used to encrypt password in data source and subscription definitions. If this option is not specified, passwords will not be backed up.

2. GUI tool (RSMigrationUI.exe):
You can either type in the parameters in the textboxes, or define your input in an xml file and click "Load Configuration". A sample configuration xml file is provided (MigrationSettingsSample.xml).