We developed and published a Beta version of Reporting Services Migration Tool. This has been an ask from many customers. The tool is the first step to address these asks. It is really a backup and restore tool for SSRS. It has cool features like migrating stored credentials (including passwords) and report history snapshots. Currently it has a few limitations in functionality, which we will address over time. Users should take a look at the release notes. I am copying part of it here. Most notably the tool currently only supports migration from native to SharePoint integrated mode server. Feedback and bug report is welcome :).
Please post your feedback on Reporting Services MSDN forum:
- You can use RSMigrationTool or RSMigrationUI to backup your native report server.
- To restore or migrate the native server, run the Migration.ps1 from a PowerShell console.
- Source and target server must be SQL Server Reporting Services 2008 R2 or later.
- Source server
o Source server must be native mode using Windows authentication. (We are working on support for SharePoint integrated mode and other authentication schemes.)
o Permissions and roles from source server are not backed up
o Configuration in source server is not backed up.
o 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.)
o Linked reports are not support in SharePoint mode, hence not backed up.
o Database connection to source server catalog is made using Windows Integrated credentials of the user running the tool.
- Target server
o Target server must be SharePoint integrated mode. (We are working on support for native mode.)
o The web application must be using Windows classic authentication mode. (We are working on support for other authentication schemes.)
o Target server must be correctly configured. Target document library and folder must be created. For SSRS 2012, service application must be created and configured.
o The owner of Reporting artifacts after migration is set to the user who performed migration. (We are working towards a solution.)
o Subscription owners are set after they are migrated. If the owner does not have CreateAlerts/ManagedAlerts permission, the operation will fail.
o 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.