Qlik to Fabric Migration With Set Analysis Rebuilt as DAX, Not Just Apps Redrawn
Moving from Qlik is not a redraw. Your apps hold business logic in Set Analysis expressions, load scripts, a QVD layer and Section Access rules. Our Qlik to Fabric migration inventories that estate, rebuilds the logic as DAX on governed semantic models, moves reporting to Power BI on Microsoft Fabric, and proves the numbers match before you switch Qlik off.
Qlik to Fabric Migration: Rebuilding Logic, Not Redrawing Apps
A Qlik estate is more than its sheets. Behind them sit Set Analysis expressions, variables, load scripts, a QVD layer, an associative data model and Section Access rules. A Qlik to Fabric migration has to carry that logic across, not just recreate the charts.
Power BI works differently from Qlik. Qlik associates every table in one in-memory model, while Power BI is built around a star-schema semantic model with explicit relationships. We resolve synthetic keys and loops, consolidate app-level data models into shared semantic models on Fabric, then rebuild reports on top. Microsoft's migration guidance recommends focusing on the business questions a report answers rather than copying every visual exactly.
We decide per app. Content people use is rebuilt, near-duplicate apps are merged into one report, and apps nobody opens are retired. Whether you run QlikView, Qlik Sense or both, support dates are set by Qlik for each release, so confirm yours with Qlik and we will plan around it.
Six Core Components of Every Qlik to Fabric Migration
From inventory to parity sign-off: everything needed to move Qlik reporting to Power BI on Microsoft Fabric.
We list every QlikView document and Qlik Sense app, QVD, load script, reload task and Section Access rule, then check usage and owners. Each item is marked retire, consolidate or rebuild, with a complexity rating, before any build starts.
We replace app-by-app data models with shared semantic models on a star schema, resolving synthetic keys and circular references, and choose Import, DirectQuery or Direct Lake per subject area based on data size, freshness and where the data already lives.
We translate set modifiers, identifiers, P() and E() sets, Aggr(), rank and running-total expressions and variables into DAX measures, then test results at the original grain. Some logic moves upstream into Fabric transformations instead.
QVD files are Qlik-specific, so we trace what feeds them and rebuild the same data layer as Delta tables in OneLake. Load script logic is re-hosted in Dataflows Gen2 for light shaping, pipelines for orchestration, and notebooks or SQL for heavier transformation.
We rebuild priority apps as Power BI reports, mapping Qlik selections, bookmarks and sheet navigation to slicers, cross-filtering, drill-through and bookmarks. Where Qlik reporting is used, such as scheduled NPrinting output, we plan the Power BI equivalent per report.
We map Section Access to workspaces, apps, roles and row-level security, then run a parity framework with report owner sign-off before cutover and set up usage monitoring afterwards.
Set Analysis to DAX: How We Translate Qlik Expressions
A Qlik set expression defines which records an aggregation sees, independently of the user's selections. A DAX measure responds to the filter context of the report. So the translation is about controlling filter context, and every pattern is tested against the Qlik result. Illustrative patterns only: the right DAX depends on your model.
Sum({<Year={2025}, Region={'EMEA'}>} Sales)CALCULATE ( [Total Sales], 'Calendar'[Year] = 2025, Geography[Region] = "EMEA" )Sum({1} Sales)CALCULATE ( [Total Sales], REMOVEFILTERS () )Sum({<Customer=P({1<Product={'Bike'}>} Customer)>} Sales)CALCULATE ( [Total Sales], FILTER ( ALL ( Customer[Customer] ), CALCULATE ( COUNTROWS ( Sales ), Product[Product] = "Bike" ) > 0 ) )Avg(Aggr(Sum(Sales), Customer))AVERAGEX ( VALUES ( Customer[Customer] ), [Total Sales] )Rank(Sum(Sales)) and RangeSum(Above(Sum(Sales), 0, RowNo()))RANKX ( ALLSELECTED ( Product[Product] ), [Total Sales] ) and visual calculations such as RUNNINGSUM, or DAX window functions$(vSales) and variables holding set expressionsReusable DAX measures, plus what-if or field parameters where users picked the valueNot every Qlik expression has a one-line equivalent. Where an expression is really data preparation, such as a flag computed in the load script, we move it into Fabric so every report reuses it.
Qlik to Fabric Migration: Four Phases to Cutover
A structured plan so your Qlik reporting moves without disruption. Qlik stays live while Power BI is built and validated, so users switch only when their reports are signed off.
We inventory your QlikView and Qlik Sense environment, check usage and owners, and agree what to retire, consolidate or rebuild, with a complexity rating that flags Set Analysis-heavy apps, large QVD chains and Section Access.
Output: inventory and decisionsWe build the first governed semantic model, translate the hardest expressions and rebuild a pilot set of apps. The pilot sets DAX, naming and design standards and proves parity before the main build.
Output: signed-off pilot and standardsWe migrate in waves ordered by business priority and shared QVD layers. Each wave is checked against the Qlik original, and the report owner signs off every report before it moves on.
Output: migrated reports with sign-offWe run Qlik and Power BI side by side, cut over by audience, retire Qlik content when you are ready and hand over documentation, runbooks and training so your team can run the platform.
Output: retired Qlik content and handoverWhat the Timeline Depends On
We do not quote a duration before we have seen your estate. Length is driven by the number of apps still in scope after triage, the share that is Set Analysis-heavy, the size and depth of the QVD layer, the number of load scripts and data sources, and how long you want to run in parallel. We fix the plan in the proposal after discovery and work back from your Qlik renewal or support date where there is one.
Triage complete; destination model design and wave plan approved.
First semantic model live; pilot reports match Qlik; standards agreed.
Each wave validated and signed off by report owners.
Users moved by audience; Qlik content retired, ideally ahead of your licence renewal or support date.
How We Price a Qlik Migration
You see real effort on your own data before committing to the full programme. Price is driven by app count, expression complexity, QVD and load script volume, security requirements and parallel-run length.
We inventory your Qlik estate and give you a triage, a complexity profile and a recommended scope, at no cost.
No commitmentA priced pilot that builds one semantic model and rebuilds a representative set of apps, so the approach and effort are proven on your data.
Fixed scope and feeRemaining waves are quoted by complexity tier once the pilot gives real numbers, as fixed fee per wave or on a time and materials basis, whichever suits you.
Your choice of modelWhy Choose Us for Qlik to Fabric Migration
Six reasons teams trust us to move Qlik reporting to Power BI without losing the numbers their business relies on.
Translating Qlik expressions is where migrations stall. We map each pattern to DAX, test it at the original grain and move upstream anything that is really data preparation.
Qlik apps often carry their own copy of the data model. We consolidate them into shared star-schema semantic models first, so each business metric has one definition.
Long-lived Qlik environments carry apps nobody opens and QVDs nothing reads. We find them first, so you rebuild and test only what the business uses.
We do not switch reporting until totals, Set Analysis results and filtered views match the Qlik original and the report owner signs off.
Section Access rules are mapped to row-level security and tested user by user, so people see the same data in Power BI that they saw in Qlik.
You receive architecture notes, runbooks and a team walkthrough, and we can train your Qlik developers in Power BI, DAX and Fabric data preparation, so your team runs the platform without us.
The starting point: a Qlik environment that has grown for years. Many apps, each with its own data model, a QVD layer nobody has fully mapped, and key figures held in Set Analysis expressions that one developer understands. Finance and sales cannot reconcile their numbers, and a Qlik renewal or support date is approaching.
What we do: triage the environment, retire what nobody opens, build one governed semantic model for the shared subject area, translate the Set Analysis-heavy expressions to DAX measures, map Section Access to row-level security and rebuild the priority apps as Power BI reports. Each report is checked against the Qlik original and signed off by its owner.
What the client team gets: one definition per metric, fewer reports to maintain, documented DAX, and developers trained to extend the model. Qlik is retired in stages once parallel running confirms the numbers hold.
Other services and guides our clients use alongside Qlik to Fabric migration.
Common Questions About Qlik to Fabric Migration
Still deciding? These are the questions teams ask most before they plan their move off Qlik.
Book a Free Call →Start Your Qlik to Fabric Migration Plan
Book a free assessment. We will inventory your Qlik apps, QVDs and load scripts, flag the Set Analysis-heavy content and recommend what to rebuild, consolidate or retire, at no cost.