Hub

    If you just lift the dashboards, you haven’t migrated

    A reporting systems migration moves your reports, the metric logic behind them and the people who use them from one BI tool or reporting server to another. Copying every dashboard across carries the old metric problems into the new tool, so Rig starts with the reports people still open and rebuilds each definition once in the warehouse.

    By Rig · Last updated

    Request a migration readiness check

    At a glance

    • List the reports in use and who owns each one.
    • Rebuild each metric once in a warehouse semantic layer.
    • Run the old and new reporting side by side until the numbers agree.
    • Cut over one group of reports at a time, with a rollback plan.
    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.

    Start with the reports people still open

    Rig records report owners, usage, source models, calculations, permissions and delivery schedules, and unused dashboards are retired only after their owners agree. At a merged education software group, Rig traced every Tableau workbook to the tables behind it overnight and found that only about a third were still in use.

    Rebuild each metric once, in the warehouse

    Put the metric definitions in a semantic layer on your warehouse, where the new BI tool and your AI agents both read them. Rig Map holds those definitions with the tables, joins and business meaning around them, and keeps them current as schemas change. If the definitions stay inside one BI tool, the next tool change or the first AI agent has to rebuild them again.

    Run old and new side by side until the numbers agree

    Each rebuilt report is checked against the original before it replaces it, and every difference goes on a list for the business owner to settle. Sometimes the old report was the one that was wrong. At the education software group, the side-by-side checks showed that a raw customer count was several times the real number.

    Cut over one group of reports at a time

    Move a business area at a time, such as finance or sales, once its owner signs off the comparison. Keep the old tool available until the agreed rollback checks pass, then retire the licences for that area.

    Where to go next by source system

    Each source has its own page with its mapping and known traps.

    Source systemWhat needs careRead next
    Power BIDAX measures and semantic models built for Power BI reportsPower BI migration, Power BI alternatives
    Power BI on FabricCapacity, lakehouse sources and refresh modesPower BI migration for Fabric, Fabric to Snowflake
    TableauWorkbook calculations, level-of-detail logic and extractsTableau migration, Tableau vs Power BI, Sigma vs Tableau
    QlikView and Qlik SenseLoad scripts and associative logicQlikView migration, Qlik vs Power BI, Qlik vs Tableau
    LookerLookML models and exploresLooker migration, Looker alternatives
    MicroStrategySchema objects, metrics and scheduled documentsMicroStrategy migration
    SSRS and SQL Server 2016Paginated reports, subscriptions and SSIS jobsSQL Server reporting, SQL Server 2016 end of life
    Crystal ReportsFormatted documents people still print or sendCrystal Reports migration
    SAP BWExtractors, queries and authorisationsSAP BW assessment

    Choose the target before rebuilding the reports

    Rig is an implementation partner and does not sell a BI tool. Power BI, Tableau, Sigma and Omni are all possible destinations, and Metabase or Apache Superset suit teams willing to run open-source BI. Compare them on a representative workload and the total operating cost.

    What this looked like at Birdie

    Birdie’s RevOps lead had spent about three months building the company’s sales and marketing reporting in a legacy BI tool. After the metric definitions moved onto Birdie’s Snowflake as certified metrics, the same person rebuilt virtually all of those reports on Rig in less than a day.

    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.

    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
    Rig semantic layer showing the definitions retained for reports and AI
    Retain metric definitions as part of the reporting migration.

    Common questions

    What is a reporting systems migration?

    It is the move of reports, the metric logic behind them and their users from one BI tool or reporting server to another. Rig treats the metric definitions as the thing being migrated, and the dashboards as the last step.

    Should we move every dashboard?

    No. Move the reports people still open, once their owners agree, and retire the rest. A usage inventory shows which is which before anyone starts rebuilding.

    Where should the metric definitions live after the move?

    In a semantic layer on your warehouse, which the BI tool and your AI agents both read. A Power BI semantic model is built for Power BI reports, so agents should query certified metrics through Gateway, each with its own role.

    Which BI tool should we move to?

    Rig does not sell a BI tool. Compare Power BI, Tableau, Sigma, Omni or an open-source option against a representative workload and the total operating cost, then rebuild.

    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.

    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.

    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

    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.

    Request a migration readiness checkUse the platform with your team, or add our engineers.