Migration

    Tableau to Power BI, without rebuilding the wrong workbooks

    Rig moves Tableau reporting to Power BI, or to Sigma, Looker or Omni, starting from an inventory of the workbooks people still use. We rebuild the calculations in a governed model, run old and new reports side by side and switch when the numbers match.

    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
    Workbooks and data sourcesTarget models and reportsInventory extracts, published sources and refresh schedules.
    Calculated fields, LOD and table calculationsDAX, SQL or target expressionsRecheck aggregation and filter order.
    Groups, permissions and subscriptionsTarget roles and deliveryRecreate user filters and test exports.

    Tableau to Power BI: rebuild the calculations first

    No file import turns a Tableau workbook into a Power BI report. Rig maps the published data sources and workbook calculations into semantic models and DAX, then tests level-of-detail calculations, filters and extracts before users are asked to accept the replacement.

    When Sigma, Looker or Omni fits better than Power BI

    Power BI suits an organisation that already uses Microsoft reporting and can maintain semantic models and DAX. Sigma gives business users a spreadsheet interface on live warehouse data. Looker keeps metric definitions in LookML, and Omni builds exploration on a shared semantic model. Whichever you pick, keep the metric logic in warehouse models where you can, so the next tool change is smaller.

    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

    Can Tableau workbooks be converted to Power BI automatically?

    Rig does not rely on a file conversion. Published data sources become semantic models, and calculated fields, level-of-detail expressions and table calculations are rewritten in DAX or SQL, then tested against the Tableau results.

    How long does a Tableau to Power BI migration take?

    The assessment takes 3 to 5 working days and produces a dated plan. Each wave of reports then runs in parallel until the owners accept the numbers, so the total depends on how many workbooks are still in use.

    Should we choose Power BI or Sigma after Tableau?

    Power BI fits an organisation that already uses Microsoft reporting and can maintain DAX, and Sigma fits business users who want a spreadsheet interface on live warehouse data. Test one report your business depends on in each before deciding.

    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.