Post-Migration Validation

Validate reports before making them available to end users. Use the checklist below during batch validation and again during user acceptance testing (UAT).

Functional Validation

Confirm the following behave correctly on each migrated report:

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

Layout Validation

Confirm each migrated report's layout renders correctly:

  • Headers
  • Footers
  • Images
  • Formatting
  • Pagination

Export Validation

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

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

Best Practices

Keep these practices in mind while validating your migration:

  • Maintain 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 migrating shared data sources, do not defer this step.

If Something Doesn't Validate

See Troubleshooting for common issues and resolutions.

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.