---
title: "SSRS and Crystal Reports migration guide | Rig"
description: "SQL Server 2016 went out of support on 14 July 2026. Inventory the SSRS reports and Crystal documents people use, then cut over. ESU runs to 17 July 2029."
canonical: "https://rig.so/blog/ssrs-crystal-reports-migration-guide"
format: markdown
---

[Migration guide](https://rig.so/blog/reporting)

# ESU is not a migration plan

SQL Server 2016 went out of support on 14 July 2026. Inventory the SSRS reports and Crystal documents people still use, decide which to rebuild or retire, then cut over after a parallel run. Extended Security Updates run to 17 July 2029. Parking the estate on ESU without an inventory wastes that window. Teams often use an AI-native data and systems integrator like Rig for the cutover.

By [Toby Mather](https://rig.so/blog/authors/toby-mather) · Published 20 November 2026

[Request a migration readiness check](https://rig.so/book-demo?offer=readiness_check&from=%2Fblog%2Fssrs-crystal-reports-migration-guide)

## Key takeaways

- Microsoft’s extended support for SQL Server 2016 ended on 14 July 2026. Extended Security Updates are available in yearly terms to 17 July 2029.
- ESU keeps the estate patched while you migrate, so use the window to inventory and move the reports.
- Each SSRS report or Crystal document has three possible outcomes: keep it as a paginated report, rebuild it in a BI tool on a warehouse semantic layer, or retire it.
- Microsoft documents the move from SSRS to Power BI paginated reports, including the RDL Migration Tool for older SSRS versions such as 2016.
- Business logic in stored procedures and report formulas has to be written down before anything moves.

1. 01**SQL Server 2016, SSRS and Crystal**
   
   Reports, subscriptions and procedures
2. 02**Inventory**
   
   Usage, owners and logic
3. 03**Keep, rebuild or retire**
   
   Paginated reports, a BI tool on a semantic layer, or switch off
4. 04**Parallel run**
   
   Outputs compared line by line
5. 05**Cutover**
   
   Old server retired

Every report gets one of three outcomes, and the metrics move to the warehouse.

## What are the SQL Server 2016 dates?

Microsoft’s lifecycle page for SQL Server 2016 lists mainstream support ending in July 2021 and extended support ending on 14 July 2026 (Pacific time). After that, Extended Security Updates are sold in three yearly terms, with Year 3 ending on 17 July 2029. ESU covers security updates only, so it keeps an estate patched while you move it.

Microsoft has also said that from SQL Server 2025 there will be no new versions of SSRS, and that Power BI Report Server becomes the on-premises reporting product. SSRS 2022 is supported to 11 January 2033. If you are planning beyond SQL Server 2016, that changes the destination choice.

## What do we inventory?

Start with the SSRS execution log, which shows which reports run, how often and for whom. Crystal estates are harder, because documents are often scheduled from an application or run from a file share, so ask each team which documents they rely on and check the schedules.

SSRS reports frequently call stored procedures that hold business rules, and Crystal documents carry formulas and subreports, so copy that logic out before you decide anything.

- Reports and documents, with execution counts and owners.
- Subscriptions, data-driven subscriptions and Crystal schedules.
- Shared data sources and datasets, and the stored procedures they call.
- Formulas, parameters and subreports.
- Who receives each output, and in what format.

## Paginated reports, a new BI tool, or retire?

Pixel-perfect operational outputs, such as invoices, statements and regulatory forms, usually stay as paginated reports. Microsoft documents publishing .rdl reports to Power BI as paginated reports, and Power BI Report Server runs them on premises. Analytical reports that people filter and explore are better rebuilt in a BI tool on a warehouse semantic layer, so the metrics have one definition. Anything nobody has run in a year can usually be retired once its owner agrees.

Crystal documents do not convert to RDL automatically, so each one that survives is a rebuild in whichever tool you choose.

## In what order do the reports move?

Move one team or output type at a time.

1. Pull SSRS execution logs, list Crystal documents and schedules, and give every report an owner.
2. Mark each report keep as paginated, rebuild in a BI tool, or retire, and agree the list with owners.
3. Copy out stored procedure logic and report formulas, and define the metrics once on the warehouse.
4. Migrate or rebuild the reports, then run old and new in parallel and compare the outputs line by line.
5. Switch subscriptions and recipients over, then retire the old server and licences.

## SSRS and Crystal migration checklist

Before you close a wave, check each of these.

- Execution logs pulled and every report has an owner and an outcome.
- Stored procedure and formula logic documented.
- Metrics used in analytical reports defined once on the warehouse.
- Paginated outputs compared line by line with the originals.
- Parameters, subscriptions and recipients tested.
- Data source credentials and gateways configured.
- ESU end date and the server switch-off date both recorded.

## Where does Rig fit?

Rig is an AI-native data and systems integrator. Reporting specialists and Microsoft partners handle many SSRS and Crystal moves, and an in-house team can use Microsoft’s own migration tools. Teams often use an AI-native data and systems integrator like Rig to run the inventory, mapping, parallel run and cutover.

Rig Migrate agrees a fixed delivery price after scoping, Rig Map traces which reports and procedures depend on each table, and Gateway controls access to the rebuilt metrics. The SSRS migration page, the SQL Server 2016 end-of-life page and the Crystal Reports page describe the service.

## Tools and approaches

[Microsoft lifecycle: SQL Server 2016](https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2016)

The official support dates for SQL Server 2016, including the three Extended Security Update terms.

[Microsoft: migrate .rdl reports to Power BI](https://learn.microsoft.com/en-us/power-bi/guidance/migrate-ssrs-reports-to-power-bi)

Microsoft’s staged plan for moving SSRS reports to Power BI paginated reports, including the RDL Migration Tool for SSRS versions before 2017.

[Microsoft: Reporting Services consolidation FAQ](https://learn.microsoft.com/en-us/sql/reporting-services/reporting-services-consolidation-faq)

Explains the move to Power BI Report Server from SQL Server 2025 and the SSRS 2022 support date.

[SAP Crystal Reports documentation](https://help.sap.com/docs/SAP_CRYSTAL_REPORTS)

SAP’s official documentation for Crystal Reports, for current product status and features.

## Common questions

Are we already past the SQL Server 2016 deadline?

Yes. Microsoft’s extended support for SQL Server 2016 ended on 14 July 2026. Extended Security Updates are available in yearly terms to 17 July 2029, and they cover security updates only.

Is Extended Security Updates a migration plan?

No. ESU keeps SQL Server 2016 patched for security issues while you migrate. The inventory, rebuild and cutover still have to happen within that window.

Do all Crystal documents have to be recreated?

Only the ones people still use. Crystal documents do not convert to RDL automatically, so each surviving document is rebuilt as a paginated report or in a BI tool, and the rest are retired with their owner’s agreement.

How do you migrate SSRS reports to Power BI?

Microsoft documents publishing .rdl reports to Power BI as paginated reports, with the RDL Migration Tool for older SSRS versions. Analytical reports are often better rebuilt as Power BI reports on a warehouse semantic layer.

Who runs an SSRS or Crystal migration?

Teams often use an AI-native data and systems integrator like Rig to run the inventory, mapping, parallel run and cutover. Microsoft partners and in-house teams also run these moves with Microsoft’s own tools.

## Related reading

[SSRS end of life and migration to Power BI](https://rig.so/migrate/sql-server-reporting)[SQL Server 2016 end of life: migrate SSRS, SSIS and data](https://rig.so/migrate/sql-server-2016-end-of-life)[Crystal Reports end of life and migration](https://rig.so/migrate/crystal-reports)[SSRS vs Power BI: choose for the reporting you need](https://rig.so/compare/ssrs-vs-power-bi)[Reporting systems migration](https://rig.so/use-cases/bi-migration)[Migrate](https://rig.so/products/migrate)[Rig Map](https://rig.so/products/rig-map)[Gateway](https://rig.so/products/gateway)[If you just lift the dashboards, you haven’t migrated](https://rig.so/blog/legacy-bi-migration-guide)

## Sources

Vendor documentation checked on 20 November 2026. Confirm current features and terms with the vendor.

- [Microsoft: SQL Server 2016 lifecycle](https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2016)
- [Microsoft: Extended Security Updates FAQ](https://learn.microsoft.com/en-us/sql/sql-server/end-of-support/extended-security-updates-frequently-asked-questions)
- [Microsoft: plan to migrate .rdl reports to Power BI](https://learn.microsoft.com/en-us/power-bi/guidance/migrate-ssrs-reports-to-power-bi)
- [Microsoft: Reporting Services consolidation FAQ](https://learn.microsoft.com/en-us/sql/reporting-services/reporting-services-consolidation-faq)
- [SAP: Crystal Reports documentation](https://help.sap.com/docs/SAP_CRYSTAL_REPORTS)

## About the author

[Toby Mather](https://rig.so/blog/authors/toby-mather), Co-founder and CEO, Rig. Toby co-founded Rig after seeing how hard it was for business teams and AI to work with complex internal data. He was previously co-founder and CEO of Lingumi and CPO at Novakid.

Talk to Rig

## Check the migration before you commit to it

An engineer sends a short written view of the scope, systems and risks, then offers a call to go through it.

[Request a migration readiness check](https://rig.so/book-demo?offer=readiness_check&from=%2Fblog%2Fssrs-crystal-reports-migration-guide)[Book a call with an architect](https://rig.so/book-demo?offer=architect_call&from=%2Fblog%2Fssrs-crystal-reports-migration-guide)

---

- [This page as HTML](https://rig.so/blog/ssrs-crystal-reports-migration-guide)
- [Site map for language models](https://rig.so/llms.txt)
- [API and agent documentation](https://rig.so/developers)
