Before a migration, four questions need answers: what exists, what is used, what duplicates what, and whether the new numbers match the old ones. No single tool answers all four for every platform, and some of the most useful are free. Here is what each kind of tool does well, and what it leaves to you.

Free tools from Microsoft

  • The SSRS execution log. The ExecutionLog3 view in the ReportServer database shows which reports ran, when and for whom. It keeps 60 days of history unless someone changed the setting.
  • The ReportingServicesTools PowerShell module. It lists and copies report server content between servers. Useful for moving reports, not for deciding which ones should move.
  • Publishing .rdl files to the Power BI service. It moves SSRS paginated reports into Power BI and reports what could not be converted.
  • FUAM (Fabric Unified Admin Monitoring). A free solution accelerator in Microsoft's fabric-toolbox on GitHub that collects activity, workspace, capacity and scanner metadata into a Fabric lakehouse. It is community supported rather than an official Microsoft product.

Power BI model clean-up

  • Measure Killer, from Brunner BI. Finds unused measures and columns in Power BI models and shows where each one is used. The core edition is free; wider tenant features are paid.
  • Tabular Editor. Edits Power BI and Analysis Services models and checks them against Best Practice Analyzer rules.

These tidy models. They do not tell you that two reports calculate the same KPI in different ways, or which one the business means.

Governance and monitoring platforms

  • Power BI Sentinel. Backup, audit history, lineage, change tracking and documentation for Power BI and Microsoft Fabric.
  • Datalogz. Monitoring across BI tools including Power BI, Tableau and Qlik, covering inventory, usage and cost, with similarity scoring to find near-duplicate reports.

Testing migrated reports

  • QuerySurge BI Tester. Automated tests that compare report data, including between BI vendors and between servers, for teams that want repeatable regression testing.

Automated comparison tells you that two numbers differ. Someone still has to decide whether the difference is a bug or a definition the business changed on purpose.

What no tool decides for you

  • Which version of a KPI is right. That is a business owner's call, made with every version side by side.
  • Which reports retire. Usage is evidence, but an owner still has to agree.
  • Whether a difference matters. Agree tolerances and reasons for expected differences before testing starts.
  • Who signs off each report after the move, and against what.

Where Reperta fits

Reperta works across spreadsheets, report servers, databases and Power BI rather than one platform. It maps what exists and what relies on what, groups the competing versions of each measure, helps owners agree one definition and record the decision, and checks migrated and improved reports against what was agreed. It works alongside the platform tools above.