Prerequisites and Planning
Before migrating reports, confirm you have the access and resources described below.
SSRS Environment
Confirm you have the following in place on the SSRS side before you begin:
- Report Server administrative access.
- Connection string details (server, database, credentials, authentication type) for each SSRS shared data source. Confirm with your SSRS administrator how to retrieve these.
Bold Reports® Environment
Confirm you have the following in place on the Bold Reports® side before you begin:
- Bold Reports® server installation (on-premises, cloud, or container deployment via Docker, Kubernetes, or Linux).
- Administrator privileges on the Bold Reports® server.
- Bold Reports® Server URL, Site/Tenant identifier, and a valid Bearer token for the REST API with permission to create items.
PowerShell (Windows)
Automated migration also requires:
- PowerShell (Windows): the tool used to connect to both the SSRS and Bold Reports® servers and run the migration commands. Requires local write permission to the export folder.
Tip: For a smooth automated migration, keep SSRS item names consistent. The migration scripts rely on name matching to bind datasets to data sources and to organize reports into categories.
Choose a Migration Approach
Two migration approaches are available, depending on how many reports you're moving:
| Approach | Best for |
|---|---|
| Manual Migration | Migrating a limited number of reports, proof-of-concept projects, controlled one-by-one validation |
| Automated & Bulk Migration | Large report repositories, preserving category structures at scale, reducing manual effort |
Next: Now that you have the prerequisites in place, choose the approach that best fits your scenario and continue with Manual Migration or Automated & Bulk Migration. To understand why organizations make this move, see why migrate to Bold Reports® in the Overview.