SSRS to .NET Core: Your 3 Migration Options Compared

The ReportViewer Problem

The Microsoft ReportViewer control has fundamental limitations that block modern .NET adoption:

Microsoft's strategic direction is clear: they want enterprises on Power BI. The on-premises SSRS product receives minimal investment while Power BI gets continuous feature updates.

The simplest option is to change nothing. This only makes sense if your reports aren't business-critical, you have no plans to modernize to .NET 8+, and your application has a defined end-of-life.

The upside is zero migration effort. The downside is accumulating technical debt, no path to containerization, and eventual obsolescence when Microsoft ends support.

Microsoft's official migration path uses the same RDL/RDLC format. This makes sense if you're already invested in the Microsoft 365/Azure ecosystem, have a small number of report consumers, and data residency in Microsoft's cloud is acceptable.

Pricing Model

Power BI Paginated Reports requires either Power BI Premium Per User (PPU) at $24/user/month ($288/year per user), or Microsoft Fabric capacity starting at approximately $5,000/month for F64.

The third option is replacing ReportViewer with a cross-platform .NET library that renders RDLC reports natively on any platform. This makes sense when you need Linux, Docker, or Kubernetes support, you're migrating to .NET 8+, data must stay within your infrastructure, and you want predictable non-per-user pricing.

The Hidden Trap: Most Libraries Require Rewrites

Most third-party reporting libraries (FastReport, Stimulsoft, DevExpress, Telerik) use proprietary report formats. Migrating means rewriting every single report from scratch. For an organization with 50+ RDLC files built over years, that's weeks or months of work — and the risk of introducing bugs in battle-tested reports.

Evaluation Checklist

Self-Hosted Options Compared

Typical Migration Timeline

A typical migration scenario for a mid-market company with 80 RDLC reports built over years, migrating from Windows Server / .NET Framework 4.8 to Kubernetes:

Key Validation Steps

• Report inventory — Document all reports, their complexity, and usage frequency
• Compatibility testing — Render each report and compare output to existing ReportViewer output
• Performance benchmarking — Measure render times for high-volume reports
• Export validation — Verify PDF, Excel, and Word exports match expected output
• Integration testing — Test parameter passing, data source binding, and subreports

Common Issues to Check

• Custom fonts — Ensure they're available on Linux (fonts-liberation package in Docker)
• Image paths — May need adjustment for new file system
• Expression compatibility — Test complex expressions thoroughly
• Subreport references — Verify paths resolve correctly

5-Year Cost Comparison

For a company with $5M annual revenue and 75 report users:

SSRS2 Pricing

Revenue-based annual licensing. Unlimited developers, unlimited applications, unlimited report renders.

Quick Start: 5 Lines of Code

using Ssrs2.Reporting;

var report = new LocalReport();
report.ReportPath = "Invoice.rdlc";
report.DataSources.Add(new ReportDataSource("InvoiceData", invoiceList));
byte[] pdf = report.Render("PDF");
File.WriteAllBytes("invoice.pdf", pdf);
// Works on Linux, macOS, Windows, Docker — same code everywhere

Install: dotnet add package SSRS2.NETCore

Docker Deployment

FROM mcr.microsoft.com/dotnet/aspnet:10.0 AS base
RUN apt-get update && apt-get install -y fonts-liberation && rm -rf /var/lib/apt/lists/*

FROM mcr.microsoft.com/dotnet/sdk:10.0 AS build
COPY . /src
RUN dotnet publish /src -c Release -o /app

FROM base
COPY --from=build /app .
ENTRYPOINT ["dotnet", "MyReportApp.dll"]
# RDLC reports render natively on Linux — no GDI+, no libgdiplus

Frequently Asked Questions

Conclusion

SSRS and the ReportViewer control served the .NET ecosystem well for two decades. But the platform has moved on. You have three paths forward:

1. Stay on SSRS — Acceptable for legacy applications with a defined sunset
2. Power BI Paginated Reports — Works if you're small, cloud-first, and Microsoft-committed
3. Self-hosted library — The practical choice for modern .NET applications at scale

The good news: you don't have to rewrite your reports. Your RDLC files are portable. The right migration tool lets you keep your existing reports and run them anywhere.