Legacy BI migration

    Move off legacy BI and keep only the reports people use

    Rig scans which reports your teams actually open, rebuilds those on governed definitions in your warehouse, and checks each one against the original before the old tool goes.

    Get a migration quote

    Every BI renewal is a chance to stop paying for reports nobody opens

    QlikView, MicroStrategy and SQL Server reporting all have support dates, and Tableau, Looker and Power BI Premium come up for renewal every year. The usual answer is another BI tool, priced per dashboard, with every old report carried across whether anyone reads it or not.

    1. 14 Jul 2026

      Microsoft ended extended support for

      SQL Server 2016 with SSRS and SSIS

      With Rig

      Rig rebuilds the reports people still run on governed data and checks them against SSRS, so you move them once.

    2. 31 Oct 2026

      Qlik ends support for

      QlikView 12.90

      With Rig

      Rig finds the QlikView apps people still open and rebuilds those on your warehouse before the date.

    3. 31 Dec 2026

      Strategy ends mainstream support for

      MicroStrategy on-premises

      With Rig

      Rig Map shows which dossiers and reports still run, and Rig rebuilds and checks those before support lapses.

    4. At your renewal

      Microsoft is retiring

      Power BI Premium capacity

      With Rig

      Before you sign for Fabric, the usage scan shows which reports anyone opens.

    What happens to the BI estate

    Each report is rebuilt on governed data, merged with its near-copies, or retired.

    • Hundreds of dashboards

      The reports people use

      A usage scan shows which reports anyone opens and what each one reads. In one merged group, 108 of 322 Tableau workbooks were still in use.

    • Logic inside the BI tool

      Certified metrics

      Measures and calculated fields become governed definitions in your warehouse, imported directly where a semantic layer already exists.

    • Numbers that differ by tool

      One checked number

      Each rebuilt report is checked against the original. Where the old figure was wrong, the difference goes to the business to agree.

    What replaces the dashboards

    The rebuilt reports run as data apps on governed data, and people can change, trace and act on them.

    • Static dashboards

      Data apps

      An app can be a dashboard. It can also hold a list of cases people work through, with flags, notes and saved views that it remembers.

    • A ticket for every change

      A change in Claude

      Ask Claude for a new view or metric and the app updates in a couple of minutes, on the same governed data.

    • Numbers nobody can explain

      The Inspector

      Open the Inspector on any number to see the query that produced it, the tables it read and the metric it used.

    • Reports that only display

      Workflows and automations

      Apps run on a schedule, post to Slack and feed automations that act on the result.

    • Exports passed around

      Apps published to the team

      Publish an app and colleagues can view, run or remix it, each with their own permissions.

    • One view for everyone

      Access by role and row

      Role and row-level access decide what each viewer sees, so one commission app shows every rep only their own deals.

    How the work runs

    1. Scan what people open

      A usage scan of your BI tool shows which reports are opened, by whom, and which tables and models sit behind each one.

    2. Agree the scope and price

      Our engineers use the scan to agree the reports to rebuild, the checks each must pass and a fixed price, before work starts.

    3. Rebuild and check

      Rig rebuilds the agreed reports in your warehouse and lists every difference from the original with its cause.

    4. Switch off when reports match

      You switch off the old tool once the rebuilt reports match, and the definitions stay on Rig for apps and AI.

    Choose your current setup

    QlikViewTableauMicroStrategySQL Server reportingLookerPower BI and FabricWarehouse semantic layers

    Where to start

    Common questions

    Do we have to move to another BI tool?

    No. Reports are rebuilt as apps on your own warehouse, and teams read them in Rig, Slack or Claude.

    Can you import our existing metrics?

    Yes. Where definitions live in LookML or another semantic layer, Rig imports each one with its SQL, joins and description. Where they only exist inside dashboards, the rebuild is how they get written down.

    What if the old report was wrong?

    The side-by-side check shows it. Each difference is listed with its cause, and the business agrees the true number before the old report goes. In one merged group, a per-school training figure had been inflated about 131 times by a join that multiplied rows.

    How is the price set?

    The usage scan counts the reports people use, and the fixed price is set from that count before work starts.

    How long does it take?

    That depends on how many reports people use. One RevOps team rebuilt virtually all of its sales and marketing reporting in under a day, and a merged group had its first three business areas about 85 to 90% rebuilt after two days on site.

    We are moving to Fabric anyway. Is this still useful?

    Yes. You keep fewer reports, and the ones you keep move with checked numbers.

    SOC 2 Type 2EU and US hostingRole-based accessYour warehouse or ours

    Talk to Rig

    What work do you want to improve?

    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 quoteUse the platform with your team, or add our engineers.