Qlik to Power BI migration in short
A Qlik to Power BI migration means rebuilding, not converting: Qlik load scripts become Power Query or warehouse SQL, the associative model becomes a star-schema semantic model, Set Analysis becomes DAX, and Section Access becomes row-level security. Done well, it takes an app inventory, a triage that retires what nobody opens, a rebuilt data layer, and a parallel run where the new numbers are signed off against the old ones before anyone switches off Qlik.
The timing question got sharper this month. Qlik's own QlikView Product Lifecycle page lists 31 October 2026 as the end of support for QlikView 12.90, the May 2024 release. Anyone still on 12.90 or older is now running without security fixes or standard support. Qlik has not ended QlikView as a product: version 12.100 is listed with support to 30 September 2027. So the real choice is upgrade QlikView, move to Qlik Sense or Qlik Cloud, or leave for Power BI. This guide is for the teams weighing the third option, and it is honest about when the first two are better.
We are a Power BI consulting team, so we have a view. The sections below are the checks we run before quoting a migration, and they will tell you whether you need us at all.
The numbers behind the decision
Is Power BI actually cheaper than Qlik?
Often, but not automatically. Many migration pages repeat a claim of up to 75% lower licence cost. That depends entirely on how many people view reports and what you already pay Microsoft. Run the maths on published list prices before you trust anyone's percentage, ours included.
| Scenario | Qlik Cloud (list) | Power BI (list) | Which is cheaper |
|---|---|---|---|
| 25 people who all view reports | Standard: $825 x 12 = $9,900 a year | Pro: 25 x $14 x 12 = $4,200 a year | Power BI |
| 160 people who all view reports | Standard: $9,900 a year (unlimited users, if 25 GB is enough) | Pro: 160 x $14 x 12 = $26,880 a year | Qlik Cloud, on licences alone |
| 160 viewers, company already on Microsoft 365 E5 | $9,900 a year | Pro is included in E5, so close to $0 extra for those users | Power BI |
| Data model needs more than 50 GB | Premium $2,750 a month plus capacity packs, or Enterprise by quote | Fabric capacity, priced by size and region | Quote both |
Prices are the vendors' published list prices in November 2026 (Microsoft notes regional variation). Negotiated discounts change every row. Two things this table leaves out matter just as much: the one-off cost of the rebuild, and whether your organisation is already standardising on Microsoft Fabric, Teams and Entra ID. If it is, Power BI fits the identity, security and data platform you are paying for anyway. If you run a self-hosted Qlik Sense Enterprise estate on a perpetual licence with low maintenance fees, the licence case for moving may be weak, and you should say so to whoever is pushing the project.
How Qlik concepts convert to Power BI
Load script and QVDs
Qlik load scripts mix extraction, joins, mapping loads and business rules in one place, and QVD files act as a private staging layer. In Power BI that logic should move upstream: into SQL views, dbt models or a Fabric lakehouse for anything shared, and Power Query only for light shaping. Rewriting script line by line into Power Query is the most common way to end up with slow, fragile refreshes.
Associative model
Qlik associates every field with every other through shared field names, and tolerates synthetic keys and loose tables. Power BI's VertiPaq engine expects facts and dimensions with explicit one-to-many relationships. This is a redesign, not a mapping, and it is where most of the effort and most of the risk sit.
Set Analysis
An expression such as Sum({
Section Access
Section Access reduces data at load against a user table. Power BI row-level security filters at query time through roles, usually driven by a security table joined to a dimension and USERPRINCIPALNAME(). Rebuild it per role and test it by viewing the report as real users before go-live.
NPrinting and extensions
NPrinting distributions map to Power BI paginated reports and subscriptions. Qlik extensions and mashups have no direct equivalent: each needs a certified custom visual, a redesign with native visuals, or an embedded app. Count these early, because they are where estimates go wrong.
A Qlik to Power BI migration plan that holds up
Inventory with usage, not opinions
Export every app, sheet, QVD, reload task, Section Access table and NPrinting job, with last-opened dates and user counts from the Qlik logs. Ask owners what they need only after you know what they use.
Triage every app
Our working rule: apps nobody opened in the last 90 days are archived, not migrated. Apps that duplicate each other are merged. What remains is ranked by business criticality and complexity, which sets the order of the waves.
Rebuild the data layer first
Move extraction and business rules out of load scripts into a warehouse or Fabric lakehouse, with tested transformations. Reports built on a clean layer take days; reports built on copied scripts take weeks and then break.
Build certified semantic models
One star-schema model per subject area, measures written once in DAX, row-level security defined in the model, and descriptions on every measure so self-service users pick the right one.
Rebuild reports, redesigned for Power BI
Do not copy Qlik sheet layouts pixel for pixel. Rebuild around the questions each audience asks, using drill-through, bookmarks and field parameters where Qlik used alternate states and many list boxes.
Reconcile and run in parallel
For each report, pick control totals and a set of spot-check cuts, and compare Qlik and Power BI on the same data snapshot. Differences are explained in writing and signed off by the report owner. Run both for at least one full reporting cycle.
Cut over and switch Qlik off
Move users wave by wave, train them on their own reports, redirect links and subscriptions, and then actually decommission the Qlik apps. A migration that leaves both platforms running has doubled the cost it was meant to cut.
Worked example: a pharma brand team's Qlik reporting
Here is the shape of a pharma brand team's Qlik reporting, described as a pattern rather than a client, because it shows every hard part of a migration in one app. A brand team runs a QlikView app on weekly syndicated prescription data, Veeva CRM call activity and a territory alignment file. Section Access restricts each rep to their territory and each manager to their region. NPrinting emails a PDF to the field every Monday.
In the migration, the weekly prescription files and CRM extracts land in a warehouse, where the prescriber-to-territory mapping and the product hierarchy are maintained once instead of in three load scripts. The semantic model has a prescription fact at prescriber-week grain, a call activity fact, and shared prescriber, product, territory and date dimensions. Section Access becomes dynamic row-level security driven by the alignment table, so a realignment updates security with no code change. The Monday PDF becomes a paginated report subscription per territory. The reconciliation compares total prescriptions by product and week, and calls by territory, between the two systems before sign-off.
The hard parts are always the same: market definitions buried in Set Analysis, territory history when alignments change mid-quarter, and reps who rely on a QlikView selection pattern nobody documented. If this is your estate, our pharma commercial analytics work covers the data model side, and the pharma commercial data warehouse guide explains the layer underneath.
What a Qlik to Power BI migration costs and how long it takes
The cost is driven by three counts: the number of apps after triage, the complexity of the data model and expressions in each, and how much of the load script logic must be rebuilt as a proper data layer. Licence savings, if any, come later.
For published reference points, Bacancy Technology's 2026 Qlik to Power BI guide puts small migrations at $15,000 to $40,000 over 8 to 12 weeks, mid-scale at $50,000 to $150,000 over 3 to 5 months, and large enterprise programmes at $150,000 to $500,000 or more over 6 to 12 months. Treat those as one firm's ranges, not a market survey. The same guide still lists Power BI Pro at $10 a month, which Microsoft raised to $14, a reminder to check every vendor number against the vendor.
How to estimate your own: count apps after triage, then sort each into simple (one fact, few expressions, no Section Access), standard, or complex (several facts, heavy Set Analysis, Section Access, extensions or NPrinting). The complex group drives the budget, so get those scoped first. Our Power BI consultant cost guide covers day rates and engagement models if you are pricing outside help, and automated conversion tools from several vendors can speed up the expression and layout work, though none of them redesign a data model for you.
Common migration mistakes
Migrating every app
Moving apps nobody uses spends the budget on reports that will be retired a year later.
- Triage on usage logs
- Archive, do not migrate
Copying load scripts into Power Query
Business rules stay buried in reports, refreshes get slow, and the next migration is as painful as this one.
- Move logic upstream
- Test transformations
No reconciliation sign-off
Users find a number that differs, stop trusting the new reports and quietly keep the old ones.
- Control totals per KPI
- Written sign-off by owner
Recreating Qlik layouts exactly
Qlik sheets designed around list boxes and selections feel clumsy in Power BI, and users blame the tool.
- Redesign per audience
- Use drill-through and bookmarks
Security tested last
Row-level security tested a week before go-live is how a rep sees another region's numbers.
- RLS in the model from day one
- Test as real users
Never switching Qlik off
Both platforms keep running, both get paid for, and the business case disappears.
- Decommission date agreed upfront
- Licence reduction tracked
When you should not migrate to Power BI
Questions about moving from Qlik to Power BI
Is QlikView end of life in 2026?
Can Qlik apps be converted to Power BI automatically?
How do you convert Set Analysis to DAX?
How long does a Qlik to Power BI migration take?
What happens to QVD files when we move to Power BI?
Do report viewers need a Power BI licence?
Should we move to Qlik Cloud instead of Power BI?
Planning to leave Qlik?
Send us your app count and what the reports are for. We reply with a triage approach, the questions that decide the cost, and whether migrating makes sense for you at all.
Part of our KPI Dashboards and BI hub. Start with our KPI dashboard development.