Publishing an RDL file is only one part of an SSRS or Power BI Report Server migration. The existing service also includes folders, shared data sources, shared datasets, credentials, Windows groups, schedules, standard and data-driven subscriptions, file-share delivery, parameters, linked reports, custom assemblies, URLs, printing, exports, execution history, operations, and business deadlines. A successful upload does not prove that the reporting service has been migrated.
Datrick starts with catalog and usage evidence, then selects the right target for each active report. AI can classify RDL features, summarize queries and expressions, cluster similar reports, propose test cases, and draft mapping documentation. Engineers review compatibility, design connections and security, implement exceptions, and validate data and rendering with report owners.
Do you need to retire SSRS or Power BI Report Server without disrupting scheduled documents and operational reports? Begin with an inventory and representative pilot before committing to a factory estimate.
Inventory the service, not only the RDL folder
Collect report-server catalog metadata, RDL definitions, execution logs, subscriptions, schedules, data sources, datasets, folders, security, owners, linked reports, resources, history snapshots, and configuration. Reconcile usage with report owners and business calendars. Classify reports as retire, consolidate, retain temporarily, migrate as paginated, redesign as interactive Power BI, or replace with another service.
| Assessment area | Evidence | Migration decision |
|---|---|---|
| Business use | Owner, audience, frequency, deadline, criticality, output format, delivery channel, usage, and replacement. | Retire, consolidate, paginated migration, interactive redesign, or temporary coexistence. |
| RDL compatibility | Version, data regions, expressions, parameters, drill, images, maps, custom code, assemblies, extensions, and fonts. | Direct publish, revise, custom redevelopment, alternative target, or unsupported exception. |
| Data access | Shared and embedded sources, datasets, credentials, Windows authentication, custom providers, query parameters, and gateways. | Embedded resource, cloud connection, enterprise gateway, source change, credential model, or redesign. |
| Distribution | Standard and data-driven subscriptions, email, file share, PDF, Excel, Word, URL access, applications, and automation. | Power BI subscription, Power Automate, API or application change, controlled manual process, or retained dependency. |
| Security | Folder roles, item permissions, AD groups, data-source security, parameters, sensitive output, recipients, and external access. | Workspace, app, direct access, RLS, gateway identity, recipient control, label, and audit design. |
| Operations | Schedules, failures, execution time, concurrency, caching, snapshots, monitoring, support, backups, and server dependencies. | Capacity, performance, monitoring, SLA, archive, rollback, and decommission requirements. |
Choose paginated or interactive Power BI per outcome
Power BI paginated reports retain the RDL format and are designed for precise pages, printing, PDF, parameterized detail, and document-style distribution. Interactive Power BI reports are better suited to exploration, visual analysis, cross-filtering, and reusable semantic models. Some legacy reports should be retired or replaced by an alert, export, API, or operational application rather than rebuilt.
Do not convert an invoice, regulatory statement, or pixel-sensitive form into an interactive report merely to reduce RDL count. Do not preserve a static management dashboard as paginated when users need exploration. Record the business action, required output, interaction, latency, security, distribution, and accessibility before choosing the target.
Use Microsoft's migration tooling inside a controlled process
Microsoft provides built-in publishing for newer SSRS and Power BI Report Server versions and an RDL Migration Tool for earlier versions. The tool checks unsupported data sources and components, converts shared data sources and datasets into embedded resources, publishes reports that pass checks, and records successes and failures. It does not change or remove source reports.
Run compatibility scans on preserved copies and retain logs. Treat every failed item as a classified exception and every successful item as “published, not yet accepted.” Custom DLL references are not supported in Power BI paginated reports, and supported data sources differ. Shared-resource conversion can increase duplicated configuration, so define connection ownership, credential rotation, parameterization, and environment promotion.
Build a migration factory with exception paths
| Stage | Delivery action | Exit evidence |
|---|---|---|
| Discover and rationalize | Extract catalog, definitions, execution, subscriptions, security, sources, owners, outputs, and business requirements. | Reconciled inventory, disposition, criticality, compatibility class, owner, and wave candidate. |
| Design target | Choose paginated, interactive, replacement, or retire; design workspace, connection, gateway, capacity, security, distribution, and support. | Target mapping, architecture, feature-gap decision, acceptance tests, estimate range, and exception owner. |
| Convert and remediate | Run supported tooling, revise RDL, replace custom code, configure connections, rebuild unsupported distribution, and source-control changes. | Conversion log, reviewed definition, environment configuration, security mapping, and reproducible deployment. |
| Validate | Compare parameters, data, layout, pagination, exports, subscriptions, security, performance, failure behavior, and business deadlines. | Expected versus observed results, tolerance, exception, reviewer, owner approval, and operational readiness. |
| Cut over | Freeze source changes, refresh source and target, switch links and recipients, monitor, support users, and retain rollback. | Cutover checklist, communications, access and output verification, incident path, rollback, and stabilization period. |
| Decommission | Confirm no active dependencies, archive required definitions and evidence, revoke access, remove schedules, and retire infrastructure by approval. | Owner sign-off, archive and recovery record, dependency recheck, cost removal, security closure, and audit trail. |
Validate document behavior and business delivery
Compare parameters, defaults, cascading behavior, query results, totals, grouping, sorting, page breaks, headers, footers, images, fonts, barcodes, charts, hyperlinks, drillthrough, and localization. Render representative PDF, Excel, and Word outputs and compare page count, dimensions, clipping, non-Latin text, print behavior, and downstream processing.
Test data-source credentials, gateways, SSO where supported, timeouts, concurrency, capacity, subscriptions, recipients, attachment size, security personas, and failed-delivery alerts. Validate the business deadline: a report that renders correctly but arrives after a regulatory cutoff has failed acceptance.
Use deterministic comparisons for data and layout signals where possible. AI can identify likely visual differences and summarize failure logs, but a named owner decides whether output is materially equivalent.
Plan coexistence and decommission explicitly
Microsoft notes that migration can proceed without removing source reports or creating immediate downtime. Use this to run controlled coexistence for critical outputs. Freeze or govern changes so source and target do not diverge silently. Define which platform is authoritative during each wave and how emergency fixes are synchronized.
Before decommissioning, inspect execution history, subscriptions, file shares, application URLs, browser bookmarks, scheduled jobs, archives, APIs, service accounts, firewall rules, databases, backups, and support procedures. Retire by approved dependency evidence, not by the fact that all known RDLs were uploaded.
Run a four-to-six-week assessment and pilot
- Define migration drivers, server versions, target tenant and capacity, contract dates, security constraints, stakeholders, and success measures.
- Extract and reconcile catalog, definitions, usage, sources, subscriptions, security, owners, outputs, and infrastructure dependencies.
- Rationalize the estate and classify direct migration, revision, interactive redesign, replacement, retention, and retirement candidates.
- Select representative RDLs covering shared resources, parameters, subscriptions, rendering, security, custom features, and performance.
- Design target workspaces, connections, gateways, security, distribution, deployment, monitoring, and support.
- Run tooling, remediate exceptions, and deliver the pilot through controlled environments.
- Validate data, rendering, exports, subscriptions, security, performance, failure handling, and owner acceptance.
- Deliver the wave plan, estimate range, exception backlog, coexistence and cutover model, decommission controls, and operational runbooks.
Frequently asked questions
Can SSRS reports be migrated to Power BI?
Yes. Supported RDL reports can be published to Power BI as paginated reports. Microsoft provides built-in publishing for newer SSRS and Power BI Report Server versions and an RDL Migration Tool for earlier versions. Unsupported data sources, custom code, report features, subscriptions, security, connections, and distribution patterns still require assessment, redesign, testing, and controlled cutover.
What does the RDL Migration Tool automate?
Microsoft's tool checks for unsupported data sources and components, converts shared data sources and shared datasets into embedded resources, publishes reports that pass validation to a Power BI workspace, and produces a success and failure summary. It does not prove business correctness, recreate every subscription and security pattern, validate rendering, or decommission the source server.
Should an SSRS report become a paginated report or an interactive Power BI report?
Use paginated reports when exact page layout, printing, PDF, detailed tables, parameters, or scheduled document delivery are central. Use interactive Power BI reports when exploration, cross-filtering, visuals, reusable semantic models, and self-service analysis are more important. Some portfolios need both; decide per business outcome rather than applying one target to every RDL.
How do you validate an SSRS to Power BI migration?
Compare parameters, data, totals, grouping, sorting, pagination, headers and footers, fonts, images, PDF and Excel output, security personas, data-source credentials, gateway behavior, subscriptions, performance, and business deadlines. Record source and target versions, expected and observed results, tolerances, exceptions, reviewer, and owner approval.
How long does an SSRS migration assessment take?
A bounded assessment and pilot commonly takes four to six weeks when server access, report catalog metadata, execution history, RDL files, owners, sources, and target tenant decisions are available. Full migration duration depends on active report count, compatibility exceptions, shared resources, custom code, subscriptions, security, data gateways, rendering requirements, and user acceptance.
Official implementation references
- Microsoft guidance for migrating RDL reports to Power BI
- Microsoft RDL Migration Tool guidance
- Microsoft paginated-report data retrieval guidance
- Microsoft supported data sources for Power BI paginated reports
- Microsoft overview of Power BI paginated reports
Start with the active report catalog and a pilot that includes real compatibility exceptions. Datrick can establish the migration baseline, prove the target patterns, and build a controlled path to server retirement.