Post-Migration Validation

Validate migrated reports in Bold Reports® before you make them available to end users. Use the checklists on this page during batch validation and again during user acceptance testing (UAT).

What should I check for functional validation?

Confirm the following behave correctly on each migrated report:

  • Dataset execution
  • Parameter behavior
  • Report rendering
  • Navigation functionality
  • Drill-through reports
  • Subreports

What should I check for layout validation?

Confirm each migrated report's layout renders correctly:

  • Headers
  • Footers
  • Images
  • Formatting
  • Pagination

Which export formats should I validate?

Confirm successful export to each format your reports are expected to support:

  • PDF
  • Excel
  • Word
  • CSV
  • HTML
  • XML
  • MHTML
  • PowerPoint

What are the best practices for validating a migration?

Keep these practices in mind while you validate your migration:

  • Keep the existing folder naming conventions between SSRS and Bold Reports®.
  • Migrate shared resources (data sources, then datasets) before reports.
  • Validate reports in batches rather than all at once.
  • Test category structures before production deployment.
  • Perform UAT before go-live.
  • Keep SSRS item names consistent to support name matching in the bulk migration scripts.
  • Update data source credentials immediately after you migrate shared data sources. Don't defer this step.

What if a report doesn't validate?

See Troubleshooting for common issues and resolutions.

What should I do after go-live?

Once reports are live, plan for these follow-up tasks:

  • Configure security and permissions: set up users, groups, and access controls on the Bold Reports® server. See Configure security and permissions.
  • Validate report performance: run representative reports under expected load and tune data sources as needed.
  • Configure scheduling and report distribution: use the Bold Reports® scheduler to automate delivery via email or file share.
  • Train report authors and administrators: onboard teams to the new environment and the web-based Report Designer.
  • Establish governance and maintenance procedures: define ownership, change control, and update cadences for reports and shared resources.

Frequently asked questions

When should I validate migrated reports?

Validate migrated reports before you release them to end users: during batch validation and again during user acceptance testing (UAT).

Should I validate all reports at once?

No. Validate reports in batches rather than all at once, and test category structures before production deployment.

See also