Migration

    SSRS end of life, and where the paginated reports go next

    Before rebuilding SQL Server Reporting Services, Rig finds out which reports people still use. It inventories those reports and their business logic, helps you choose the target and checks the rebuilt reporting against the original.

    By Rig · Last updated

    Get a migration plan

    At a glance

    • Rig agrees a fixed delivery price after scoping the data, logic and integrations.
    • Data moves in checked waves, with a parallel run where the systems allow it.
    • History and permission tests are part of acceptance.
    • Your system owners approve the mappings and the cutover.
    01Inventory

    Records, logic and owners

    02Map and rebuild

    Source to target definitions

    03Run in parallel

    Counts, totals and access

    04Accept and switch

    Sign-off and rollback plan

    Each wave ends with an acceptance check. This diagram shows the delivery process.

    Map the data and the logic it carries

    The table is a starting inventory, and the target edition, customisations and API access decide the final mapping. Check each object even when the name matches, because an object with the same name can behave differently in the target.

    SourceTarget or retained outputChecks and known traps
    RDL files and shared datasetsPaginated reports or rebuilt BITest SQL, expressions and pagination.
    Parameters and subscriptionsTarget filters and scheduled deliveryCheck email delivery, credentials and export formats.
    Report server roles and linked reportsTarget access policiesTest each role and linked parameter set.

    Choose the target against the work people do

    Test Power BI, Tableau, Sigma and Omni against the reports you are keeping, and keep the metric logic in warehouse models where you can. Metabase and Apache Superset are open-source options, and your team runs their hosting, upgrades and permissions.

    SSRS end of life: what Microsoft has announced

    Starting with SQL Server 2025, Microsoft is consolidating on-premises reporting under Power BI Report Server, and it will release no new versions of SSRS. SSRS 2022 keeps security updates and support until 11 January 2033. Older SSRS installs follow the lifecycle of their SQL Server version, so a report server on SQL Server 2016 reached the end of extended support on 14 July 2026.

    SSRS to Power BI: paginated reports and dashboards take different routes

    Microsoft says existing RDL reports are fully compatible with Power BI Report Server, and its guidance for the Power BI service publishes each RDL report as a paginated report. Some report server items do not migrate, such as shared data sources, which Microsoft’s tool converts to embedded ones, and mobile reports. Interactive dashboards are a separate rebuild on a Power BI semantic model. Rig inventories which reports still run, which subscriptions still send and who reads them, then moves the paginated reports with their layouts and rebuilds the rest on a governed model.

    Report typeLikely destinationTest before cutover
    Paginated RDL reportsPower BI Report Server or Power BI paginated reportsData sources, parameters, page breaks and PDF output
    Subscriptions and exportsPower BI subscriptions or scheduled deliveryRecipients, formats and timing
    Interactive summariesPower BI reports on a semantic modelTotals, filters and row-level security
    Reports nobody readsRetireConfirm with the owner before switching off

    Running SSRS on SQL Server 2016?

    SQL Server 2016 reached end of support on 14 July 2026, and Extended Security Updates are available until 17 July 2029. Our SQL Server 2016 end of life page covers the SSRS, SSIS and database work together.

    How a migration runs in Rig

    Rig maps the systems and data across your estate, connects the source and target, and maps one schema to the other with previews of real records. Rig engineers agree the objects and history in scope with your team, prepare the destination and rehearse the load before they reconcile the results. Sign-off, cutover and follow-up tasks sit in the same migration workspace.

    Agree a timeline against the actual scope

    The table gives a planning allowance for each phase, and the assessment turns it into a dated plan for the whole project. Large estates need several waves, and application configuration can add time.

    PhaseInitial planning allowanceExit check
    Assessment3 to 5 working daysOwners, access and inventory agreed
    Sample and mapping5 to 10 working daysSample records and exceptions reviewed
    Build and parallel validation2 to 6 weeks per waveCounts, totals and permissions accepted
    Final sync and cutover1 to 3 working days per waveBusiness owner signs off; rollback remains available

    Keep the evidence for each migration wave

    For each wave you receive the source-to-target mappings, a reconciliation report, an exception log and a cutover checklist. The checks cover duplicates, missing relationships, deleted records, time zones and permissions as well as headline totals, and the old system stays available until the agreed retention and rollback checks pass.

    Where Rig may fall short

    A migration that only needs a supported CSV import may be simpler to do yourself. Sub-minute operational replication, a full ERP implementation and specialist application redesign need a separate scope or another provider. Where Rig Ingest moves the data, confirm connector coverage for each source before you commit.

    Inside Rig Migrate

    Run the migration in Rig, from the systems map to cutover

    Rig natively maps systems and data across your IT estate, connects source and target systems, scopes the move and maps one schema to another. The same migration workspace tracks destination preparation, rehearsals, reconciliation, sign-off and the work after cutover, so your team can review the decisions and progress in one place.

    1. Map the IT estate

      Map systems, data and integration flows across the IT estate. See which reports, processes and teams depend on the systems you plan to change.

    2. Set up the migration

      Create the migration in Rig and record the source, destination and work to deliver. Keep the migration tasks and progress together.

    3. Connect and discover

      Connect the source and target systems, then inspect their schemas and available data. Confirm access before deciding how each object will move.

    4. Scope the work

      Choose the objects, fields and history to migrate. Record what stays, what changes and the dependencies the migration needs to preserve.

    5. Map schema to schema

      Map source objects and fields to the target schema. Preview records and review rules to copy, translate, calculate, link, look up and match owners.

    6. Prepare the destination

      Track the target preparation needed before loading data, including its configuration and the relationships your mapped records will use.

    7. Rehearse the load

      Dry run the whole load and rehearse it in the destination environment. Review the results and resolve issues before the production cutover.

    8. Reconcile and sign off

      Compare source and target records, relationships and business totals. Review exceptions with the system owners and record acceptance before proceeding.

    9. Cut over

      Work through the agreed cutover tasks in Rig. Coordinate the final load and user switch with the people who own the systems.

    10. Check after cutover

      Track the checks after the switch, confirm that reporting and processes work, and resolve outstanding issues before retiring the old setup.

    Review reporting definitions before rebuilding

    Keep the metric definitions and relationships behind your reporting available while you rebuild. Compare the target reports against the original calculations and access rules.

    Rig semantic layer showing the metric definitions used in reporting
    Metric definitions in Rig. View the full-size screenshot.

    Reporting migration at Birdie

    Birdie reports rebuilding sales and marketing reporting in less than a day. Its team kept Snowflake and the existing Fivetran pipelines; retirement of the Looker licence is not confirmed.

    Read the migration case study

    Common questions

    Is SSRS end of life?

    Microsoft will release no new versions of SSRS after SSRS 2022, which is supported until 11 January 2033. Starting with SQL Server 2025, Power BI Report Server is the on-premises reporting product, and older SSRS versions follow the end of support date of their SQL Server version.

    Can SSRS reports move to Power BI without a rebuild?

    Paginated RDL reports can move to Power BI Report Server, or to the Power BI service as paginated reports, after testing data sources, parameters and subscriptions. Interactive dashboards need a rebuild on a Power BI semantic model.

    Do we need Software Assurance for Power BI Report Server?

    For SQL Server 2022 and earlier, Power BI Report Server rights apply to Enterprise edition core licences with active Software Assurance. SQL Server 2025 Enterprise and Standard editions include it. Check your licence terms with Microsoft.

    How much does a migration cost?

    Rig maps the work and agrees a fixed delivery price before the migration starts. Source access, custom logic, history and the number of integrations affect the scope. Platform and third-party licence costs are agreed separately.

    Can we keep reporting history?

    Yes, where the source lets you extract it. You decide which history the target system needs and which stays in a governed archive, and Rig reconciles both against the original records.

    How do you check that the data matches?

    Rig compares record counts, identifiers, relationships and business totals for each wave. Every exception goes in a log, and the business owner has to accept the results before cutover.

    Will both systems run during the move?

    Yes, where the systems and licences allow it. Before the parallel run starts, you agree which system is the source of truth, how final changes are handled, the rollback conditions and the point at which users switch.

    Who does the implementation?

    Rig engineers do the work with your system owners, and your team approves the mappings, permissions and acceptance checks. Application configuration and specialist ERP or CPQ work is either written into the scope or assigned to your application partner.

    Is there a guaranteed completion date?

    The assessment produces a dated plan. Access, data quality, target readiness and user acceptance can all move it, so treat any planning range given before the assessment as an estimate.

    Sources and product details

    Vendor information checked on 20 November 2026. Confirm current editions, licence terms and prices with the vendor before buying.

    Talk to Rig

    Plan the move around the work you need to keep

    Tell us where your team spends time, loses money or needs better information.
    In a 30-minute call, we’ll discuss the data and systems work that could help.

    Get a migration planUse the platform with your team, or add our engineers.