PLAYBOOK · MODERNISATION SERIES12 min read

Qlik to Power BI, done right.

How to move QlikView and Qlik Sense estates to Microsoft Power BI: rebuild the associative model as a semantic model, rewrite set analysis as DAX, and reconcile every KPI before anyone switches.

4
phases, assessment to adoption
100%
of KPIs reconciled before cut-over
10k+
reports migrated to date
EXECUTIVE SUMMARY

Leave the scripts behind, keep the logic.

Moving from Qlik to Power BI is a chance to replace script-heavy apps and QVD sprawl with one governed semantic layer, put security in one place, and get ready for Microsoft Fabric and Copilot.

Part I covers why teams move, how the platforms compare, our four-phase method and the conversion mapping. Part II shows how our specialists rebuild each app: the model, the logic and the validation.

“The goal isn’t a like-for-like copy of the old environment. It’s a modernised, governed platform.”
The short version

Expect a smaller estate after the assessment, set analysis rebuilt as one reusable DAX measure library, and every KPI reconciled against Qlik before anyone switches.

IPart oneThe migration, end to end
01 · WHY MOVE

Why enterprises move from Qlik.

01
Microsoft-native

Power BI lives where your people already work: Teams, SharePoint, Excel and Outlook.

02
One governed semantic layer

Shared semantic models replace per-app load scripts and QVD sprawl, so every report uses the same numbers.

03
Self-service without scripting

Qlik apps lean on load-script and set-analysis specialists. Power BI lets business teams build and change reports themselves.

04
Lower cost per user

Consolidating onto Power BI typically lowers the cost per user, especially for Microsoft 365 organisations.

05
Fabric and Copilot

One platform for data engineering, warehousing and BI, with Copilot built in.

06
A larger talent pool

Power BI and DAX skills are easier to hire for and grow in-house.

Definition

Qlik to Power BI migration converts QlikView and Qlik Sense apps, load scripts, QVD layers, set analysis and section access into Power BI, keeping the business logic while moving onto a governed, Microsoft-native platform.

02 · HOW IT COMPARES

Qlik vs Power BI.

Qlik vs Power BI
QlikPower BI
Best forAssociative explorationMicrosoft-centric enterprises
Data modelAssociative, in-memoryTabular semantic model
Cost per userTypically higherTypically lower
Microsoft integrationLimitedNative
AISeparate add-onsCopilot built in
PlatformQlikView, Qlik Sense, Qlik CloudMicrosoft Fabric
03 · THE FOUR-PHASE METHOD

From assessment to adoption.

Four phases that keep business disruption low and the long-term value of Power BI high. Each builds on the one before.

  1. 01
    Assessment and discovery

    Inventory every report, classify by usage and complexity, retire the unused and produce a phased roadmap.

    • Dashboard and script inventory
    • Usage and complexity scoring
    • Dependency mapping
    • Phased roadmap
    • Effort and risk estimates
  2. 02
    Strategy and planning

    Stand up the target tenant: data architecture, governance, security, cut-over waves and a training plan.

    • Storage-mode selection
    • Workspace and pipeline strategy
    • RLS and governance design
    • Target architecture
    • Cut-over and training plan
  3. 03
    Implementation and optimisation

    Rebuild and optimise dashboards, rewrite logic in DAX and validate side by side against the source.

    • Dashboard rebuild
    • DAX and Power Query rewrite
    • Performance tuning
    • Validated semantic model
    • Side-by-side KPI parity
  4. 04
    Deployment and knowledge transfer

    Deploy, train every role on real data and run hypercare through cut-over and the first weeks of production.

    • Production deployment
    • Role-based training
    • Hypercare support
    • Adoption plan
    • Qlik retirement
Principle

Do the highest-impact dashboards first, so executive and operations teams see the return before the whole portfolio is converted. Running assessment, set-up, rebuild and training in parallel compresses the calendar.

04 · MAPPING, COST AND TIME

Every Qlik concept has a Power BI equivalent.

Every Qlik concept has a Power BI equivalent
Qlikmaps toPower BI
QlikView (.qvw) and Qlik Sense (.qvf) appsPower BI reports (.pbip)
Load scriptsPower Query and Dataflows Gen2
QVD layersLakehouse tables or shared semantic models
Associative data modelStar-schema semantic model
Set analysisDAX with CALCULATE and filter modifiers
Master itemsShared measures and display folders
VariablesDAX measures or what-if parameters
Section accessRow-level security
Selections and alternate statesSlicers, bookmarks and field parameters
StoriesBookmarks and report pages
NPrinting reportsPaginated reports and subscriptions
QMC reload tasksScheduled refresh and pipelines
Our specialists apply this mapping app by app · see Part II

Cost tracks the number of apps, load-script complexity, QVD layers, data sources and validation effort. The first assessment is fixed-fee, so leadership can budget wave by wave.

How long will yours take?
Drag to your report count
1050100200+
40 apps
8–12 weeks
typical duration
Two or three waves, highest-impact dashboards first.
How long will yours take?
Number of Qlik appstypical durationApproach
Up to 20 apps4–6 weeksA single wave: assess, rebuild and roll out together.
21 to 50 apps8–12 weeksTwo or three waves, highest-impact dashboards first.
51 to 100 apps12–20 weeksParallel rebuild teams, working wave by wave.
More than 100 apps20+ weeksA programme of waves. We retire unused reports first, which usually shrinks the estate.
A representative 16-week enterprise roll-out
Assessment
Weeks 1–2 · Inventory and prioritise
Foundation
Weeks 3–5 · Gateways, dataflows, models
Rebuild
Weeks 6–11 · Dashboards, DAX, side-by-side parity
Roll-out
Weeks 12–16 · Deploy, train, retire Qlik
IIPART TWO · 05 · HOW WE DELIVERThe DataFactZ difference

Rebuild the intent, not the syntax.

Qlik migrations are expert-led. Associative models and set analysis rarely translate line for line, so our specialists rebuild what each app is for, and spend their judgement where it changes the outcome: the model, ambiguous logic and KPI sign-off.

Intent
not syntax

Set analysis and load scripts are rebuilt as clean DAX and Power Query, not transliterated.

Every KPI
reconciled

Side-by-side checks against the Qlik app before anyone switches.

Unused
retired first

A usage review in the assessment shrinks the estate before the rebuild starts.

01 · INVENTORY
App and script inventory

Catalogues every QlikView and Qlik Sense app, load script, QVD and reload task, scored by usage and complexity.

02 · MODEL
Semantic model design

Turns the associative model and QVD layers into a star-schema semantic model, with synthetic keys and circular references resolved.

03 · TRANSLATE
Logic rewrite

Rewrites set analysis, variables and script transforms as DAX measures and Power Query, in one reusable measure library.

04 · VALIDATE
KPI reconciliation

Compares every KPI against the Qlik app, then hands over with role-based training and hypercare.

What gets migrated
  • QlikView and Qlik Sense apps
  • Load scripts and QVD layers
  • Set analysis and master measures
  • Variables and expressions
  • Section access security
  • Selections, bookmarks and stories
  • NPrinting reports and subscriptions
  • Reload schedules
06 · WHY DATAFACTZ

A Microsoft partner that has done this before.

Fluency in both Qlik and Power BI, and Microsoft-accredited specialists behind every engagement.

Microsoft · Solutions Partner
Data & AI

Microsoft-verified capability in data platform and AI delivery.

Microsoft · Solutions Partner
Digital & App Innovation

Verified for modern app and platform modernisation.

Microsoft · Advanced Specialization
Analytics on Azure

A top-tier Microsoft credential for analytics delivery.

75
Microsoft-certified Power BI, DAX and Fabric experts
45
migrations delivered across industries
10k+
reports migrated to date
98%
client satisfaction
07 · RISK MANAGEMENT

Common challenges, and how we handle them.

DAX translation

Logic can behave differently. We build a reusable DAX pattern library and validate every measure.

Data quality

Sources are often inconsistent. We profile and validate them before the model is built.

Performance

Slow reports erode trust. Star schemas and incremental refresh keep them fast at volume.

Security

Permission mismatches are common. We design RLS early, in the architecture phase.

Common mistakes to avoid
  • Migrating unused apps
  • Copying the associative model as-is
  • Transliterating set analysis line by line
  • Skipping the assessment phase
  • Leaving section access until the end
  • Recreating QVD layers instead of modelling
  • No KPI validation
  • No training for Qlik power users
ANSWERS · FREQUENTLY ASKED

Qlik to Power BI, answered.

01What is Qlik to Power BI migration?

Converting QlikView and Qlik Sense apps, load scripts, set analysis and section access into Power BI reports and semantic models, keeping the business logic while moving onto a Microsoft-native platform.

02Do you migrate both QlikView and Qlik Sense?

Yes. QlikView documents and Qlik Sense apps, on-premises or in Qlik Cloud, follow the same method. QlikView estates usually need more model redesign.

03How is set analysis converted?

Each expression is rewritten as a DAX measure using CALCULATE and filter modifiers. Set analysis rarely maps one to one, so we rebuild the intent and validate the result against the Qlik app.

04Is the migration automated?

Qlik migrations are expert-led. Our PowerMigrate accelerator covers Tableau and Spotfire; for Qlik, specialists rebuild apps wave by wave using the mapping in chapter 04.

05What happens to the associative experience?

Power BI cross-filters every visual on a page, and slicers, bookmarks and field parameters cover most selection workflows. We walk power users through the differences in training.

06How long does a migration take?

It depends on the number of apps, script complexity and data sources. The estimator in chapter 04 gives a first view; the assessment gives you a firm, phased plan.

07How do you validate the reports?

Side-by-side KPI reconciliation against Qlik, user-acceptance testing, and performance and security checks before sign-off.

08What happens to Qlik?

Both platforms run in parallel briefly. Once KPI parity is confirmed and users are trained, Qlik is retired.

09How do we start?

Book a migration assessment. We inventory your apps, scripts and QVD layers, size the complexity and hand you a phased roadmap with effort estimates.

Plan your Qlik migration with specialists.

We inventory your Qlik apps, load scripts and QVD layers, and hand you a prioritised roadmap with effort and cost estimates.