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.
Records, logic and owners
Source to target definitions
Counts, totals and access
Sign-off and rollback plan
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 system | What needs care | Read next |
|---|---|---|
| Power BI | DAX measures and semantic models built for Power BI reports | Power BI migration, Power BI alternatives |
| Power BI on Fabric | Capacity, lakehouse sources and refresh modes | Power BI migration for Fabric, Fabric to Snowflake |
| Tableau | Workbook calculations, level-of-detail logic and extracts | Tableau migration, Tableau vs Power BI, Sigma vs Tableau |
| QlikView and Qlik Sense | Load scripts and associative logic | QlikView migration, Qlik vs Power BI, Qlik vs Tableau |
| Looker | LookML models and explores | Looker migration, Looker alternatives |
| MicroStrategy | Schema objects, metrics and scheduled documents | MicroStrategy migration |
| SSRS and SQL Server 2016 | Paginated reports, subscriptions and SSIS jobs | SQL Server reporting, SQL Server 2016 end of life |
| Crystal Reports | Formatted documents people still print or send | Crystal Reports migration |
| SAP BW | Extractors, queries and authorisations | SAP 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.
| Phase | Initial planning allowance | Exit check |
|---|---|---|
| Assessment | 3 to 5 working days | Owners, access and inventory agreed |
| Sample and mapping | 5 to 10 working days | Sample records and exceptions reviewed |
| Build and parallel validation | 2 to 6 weeks per wave | Counts, totals and permissions accepted |
| Final sync and cutover | 1 to 3 working days per wave | Business 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.
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.
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.
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.
Scope the work
Choose the objects, fields and history to migrate. Record what stays, what changes and the dependencies the migration needs to preserve.
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.
Prepare the destination
Track the target preparation needed before loading data, including its configuration and the relationships your mapped records will use.
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.
Reconcile and sign off
Compare source and target records, relationships and business totals. Review exceptions with the system owners and record acceptance before proceeding.
Cut over
Work through the agreed cutover tasks in Rig. Coordinate the final load and user switch with the people who own the systems.
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.

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
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.