›› Free Data Maturity Scorecard — Discover your analytics score in 3 minutes MY SCORECARD →
›› Free Fabric Capacity Estimator — Model your CU consumption before you upgrade ESTIMATE CAPACITY →
Cloud Data Platform Migration

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.

App, QVD and load script inventory first, so unused content is retired, not rebuilt
Set Analysis and Aggr() expressions translated to DAX and tested
Section Access rules mapped to row-level security
Documented handover and training for your Qlik developers
Migration at a Glance
6
Qlik expression families (set modifiers, {1}, P() and E(), Aggr(), rank, variables) mapped to DAX patterns
3
Fabric semantic model modes: Import, DirectQuery and Direct Lake
4
Phases: discover, pilot, migrate in waves, cut over
Free
Qlik estate assessment to scope the work
Technologies QlikView Qlik Sense QVD Files Load Scripts Section Access Microsoft Fabric OneLake Power BI DAX Dataflows Gen2 Microsoft Entra ID
What We Cover

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.

Challenges We Solve
"Nobody knows which of our QlikView documents are still in use, or who owns them.
"Our key numbers live in Set Analysis expressions that only one person understands.
"Our QVD layer feeds dozens of apps and we cannot tell what depends on what.
"Section Access controls who sees what, and we cannot lose that in a move.
What We Deliver

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.

01
Qlik Estate Discovery & Triage

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.

App, QVD and load script inventory
Usage and owner audit
Retire, merge or rebuild decisions
02
Semantic Model Design on Fabric

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.

Associative model to star schema
Storage mode decision per model
One definition of revenue, margin and so on
03
Set Analysis & Expression Translation to DAX

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.

Set Analysis to CALCULATE patterns
Aggr() to iterator measures
Variables to measures and parameters
04
QVD & Load Script Migration to Fabric

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.

QVD dependency and lineage map
Load scripts to Dataflows, pipelines, notebooks or SQL
Refresh schedules and credential setup
05
Power BI Report Rebuild

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.

Report layouts focused on business questions
Drill-through and navigation design
Subscriptions and paginated reports where needed
06
Security, Governance & Parity Validation

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.

Section Access to row-level security
Workspace and app access design
Totals, grain and selection parity checks
Where Most Migrations Go Wrong

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.

Qlik patternSet modifierSum({<Year={2025}, Region={'EMEA'}>} Sales)
Typical Power BI approachCALCULATE ( [Total Sales], 'Calendar'[Year] = 2025, Geography[Region] = "EMEA" )
What we checkThat the modifier replaces the user's selection in that field, as a CALCULATE column filter does, while other selections still apply.
Qlik patternIgnore selectionsSum({1} Sales)
Typical Power BI approachCALCULATE ( [Total Sales], REMOVEFILTERS () )
What we checkWhich filters Qlik ignored (selections, the chart dimension or both), so we remove only those.
Qlik patternPossible and excluded valuesSum({<Customer=P({1<Product={'Bike'}>} Customer)>} Sales)
Typical Power BI approachCALCULATE ( [Total Sales], FILTER ( ALL ( Customer[Customer] ), CALCULATE ( COUNTROWS ( Sales ), Product[Product] = "Bike" ) > 0 ) )
What we checkWhich selections the inner set respects, and whether the result should follow current slicers.
Qlik patternAggr()Avg(Aggr(Sum(Sales), Customer))
Typical Power BI approachAVERAGEX ( VALUES ( Customer[Customer] ), [Total Sales] )
What we checkThat the Aggr() dimension list matches the iterated columns, and how blanks and zeros are treated.
Qlik patternRank and running totalsRank(Sum(Sales)) and RangeSum(Above(Sum(Sales), 0, RowNo()))
Typical Power BI approachRANKX ( ALLSELECTED ( Product[Product] ), [Total Sales] ) and visual calculations such as RUNNINGSUM, or DAX window functions
What we checkSort order, ties and where the calculation belongs: in the visual or in the shared model.
Qlik patternVariables$(vSales) and variables holding set expressions
Typical Power BI approachReusable DAX measures, plus what-if or field parameters where users picked the value
What we checkThat nested variable expansions are resolved first, so every report reuses one definition.

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

How We Work

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.

01
Discover and Triage

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 decisions
02
Model and Pilot

We 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 standards
03
Migrate in Waves and Validate

We 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-off
04
Parallel Run, Cutover and Handover

We 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 handover
Timeline

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

Milestone 1
Inventory and decisions agreed

Triage complete; destination model design and wave plan approved.

Milestone 2
Pilot signed off

First semantic model live; pilot reports match Qlik; standards agreed.

Milestone 3
Waves complete

Each wave validated and signed off by report owners.

Milestone 4
Cutover and Qlik retirement

Users moved by audience; Qlik content retired, ideally ahead of your licence renewal or support date.

Pricing Model

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.

Step 1
Free assessment

We inventory your Qlik estate and give you a triage, a complexity profile and a recommended scope, at no cost.

No commitment
Step 2
Fixed-scope pilot

A 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 fee
Step 3
Priced per wave

Remaining 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 model
Why Numlytics

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

Set Analysis to DAX Expertise

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.

Models Before Reports

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.

Inventory Before Migration

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.

Parity You Can Audit

We do not switch reporting until totals, Set Analysis results and filtered views match the Qlik original and the report owner signs off.

Security Carried Across

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.

Handover and Training

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.

CASE STUDY: A TYPICAL ENGAGEMENT

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.

FAQ

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 →
Qlik sets support dates for each QlikView release, and those dates can change, so we do not state them here. Confirm your version's date with Qlik. Whether to stay, move to Qlik Sense or move to Power BI on Microsoft Fabric is then a business decision about cost, skills and where your data platform is heading, and our free assessment sizes the Fabric option for you.
Third-party tools claim to automate parts of the conversion, and we are happy to evaluate them with you. Microsoft's migration guidance states that a conversion to Power BI cannot be completely automated from end to end. We treat automated output as a starting draft and test every rebuilt report against the Qlik original. Microsoft also advises focusing on the business questions a report answers instead of copying every visual.
There is no automatic one-to-one conversion. A set modifier such as a year or region filter usually becomes a CALCULATE measure with a column filter, {1} becomes REMOVEFILTERS scoped to what Qlik ignored, Aggr() often becomes an iterator such as AVERAGEX over the relevant column, and variables become reusable measures or parameters. The key difference is that DAX measures respond to report filter context, so we test each translation at the original grain.
We review each one. QVD files are specific to Qlik, so we trace which load scripts produce them and which apps read them, then rebuild that data layer as Delta tables in OneLake, sourced from the original systems where possible. Load script logic is re-hosted in Dataflows Gen2, pipelines, notebooks or SQL depending on complexity. Where several apps held near-identical data models, we consolidate them into one shared semantic model.
We map each Section Access rule to row-level security. In a Power BI semantic model that means roles with filters, tested user by user against the Qlik behaviour. For Direct Lake models, Microsoft documents that row-level and column-level security can also be defined in OneLake security on Delta tables, and we choose the approach that fits your model and your Microsoft Entra ID groups.
You can start with Power BI semantic models on your existing data sources. Fabric adds OneLake, Direct Lake, Dataflows Gen2, pipelines and notebooks, and Microsoft documents that semantic models in Fabric can use Import, DirectQuery or Direct Lake mode. We recommend the destination that fits your data size, freshness needs and licensing, and compare options before you commit.
Timing and cost depend on the number of apps in scope after triage, how many are Set Analysis-heavy, the size of the QVD layer and how long you run in parallel. We start with a free assessment, then a fixed-scope pilot, and quote the remaining waves from real pilot numbers. Qlik stays live during the build and parallel run, users move by audience once their reports are signed off, and we provide handover documentation and optional corporate Power BI training.
Get Started

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.