Troubleshoot Common SSRS Migration Issues

Migrating reports from SSRS to Bold Reports® is generally straightforward, but certain issues can arise during the migration process. This page lists the most common problems, their likely causes, and the steps to resolve them.

What are the common SSRS migration issues and how do I fix them?

Issue Likely cause Resolution
Data source connection failures Credentials are not migrated automatically with shared data sources. Update the username, password, and authentication settings on each data source after import.
Dataset mapping issues A shared dataset is associated with the wrong data source after migration. Verify the dataset-to-data-source mapping and correct it in Bold Reports®.
Report upload failures A dependent resource (data source or dataset) has not been migrated yet. Migrate in order: Shared Data Sources → Shared Datasets → Reports.
Expression errors Typically caused by custom assemblies or external code dependencies rather than the expression syntax itself. Review custom assemblies, referenced DLLs, and external code modules. Standard SSRS expressions remain fully supported without changes.
Bulk import: item already exists (HTTP 409) The migration script re-ran against a data source, dataset, or report that was already created in a prior run. Expected and benign in most cases: the script skips duplicates. Confirm the existing item is correct rather than re-creating it. If it's wrong, delete it from the corresponding Data Sources, Datasets, or Reports page in Bold Reports®, then re-run the import so the script re-creates it.
Bulk import: report lands in wrong category The SSRS folder name does not match an existing Bold Reports® category, or naming is inconsistent. Align SSRS folder names with the intended Bold Reports® categories before re-running the import. The script auto-creates missing categories from folder names.

What should I do if the issue persists?

If the table above didn't resolve your issue, try the following:

Frequently asked questions

Why do data source connections fail after migration?

Credentials are not migrated with shared data sources. Update the username, password, and authentication settings on each migrated data source.

What does HTTP 409 mean during bulk import?

HTTP 409 means the item already exists from a prior run. The script skips duplicates, so this is usually expected. Confirm the existing item is correct.

Why does a report upload fail?

A report upload usually fails because a data source or dataset it depends on has not been migrated yet. Migrate shared data sources, then shared datasets, then reports.

See also