QlikView to Power BI migration
A full legacy BI estate moved to Power BI with inventory, dependency mapping, and a rebuild on a governed model, with no information blackout.
- Reports migrated
- 1,247
- of 1,312 after rationalization
- Parity validated
- 98.6%
- checked number by number
- Current wave
- 6 of 8
- phased cutover, no blackout
- Cumulative effort
- 4,180 h
- Our team + client squad
Illustrative figures · fictitious client · under NDA
The challenge
A large report estate on legacy BI was expensive to license and hard to trust, and the business needed to move to Power BI without losing years of logic or leaving users without reports mid-migration.
What we built
We inventoried every report, mapped dependencies, and rebuilt the estate in Power BI over a governed semantic model, migrating in waves so each business unit kept working the whole way through.
- A full inventory and dependency map of the legacy estate before moving a single report.
- A governed Power BI semantic model so KPIs carry one definition.
- A phased, wave-by-wave cutover with parity validation at each step.
Outcomes
- Reports rebuilt on a governed model instead of copied one for one.
- Migration in waves with no information blackout.
- Lower licensing cost on the Microsoft stack.
The dashboard we delivered
Reports migrated per month
Cumulative by wave, against contracted target
Reports by business unit
Click to drill down the hierarchy
Reports in scope
One row per report rebuilt in Power BI
Illustrative dashboard with the structure delivered on the project. Client names and figures are fictitious and under NDA.
Want a dashboard like this on your data?
Tell us your scenario and get a diagnosis and a proposal with an investment range within a few business days.
Start a project