1/10

11 Nov 2026

Qlik Migration Services: Qlik Cloud, Power BI, or Fabric?

Q: What should government agencies check before migrating from Qlik?

They should confirm the authorization boundary and feature availability of the target environment first, since Qlik Cloud Government, Power BI in GCC, GCC High, and DoD, and Fabric in government clouds each differ. They should also map security rules to their identity provider and preserve records before decommissioning.

Moving off a Qlik estate comes down to three choices: bring QlikView and Qlik Sense content into Qlik Cloud with Qlik's own free migration tool, rebuild it in Power BI, or rebuild it in Microsoft Fabric. QlikView 12.90 reached its end-of-support date on October 31, 2026, while Qlik says it has no plans to end-of-life QlikView, so this is a decision about direction, not an emergency. The first route is a transfer, the other two are rebuilds, and in every case the real work is proving that the numbers still match.

For many organizations, Qlik arrived as a departmental tool and grew into something far more important. Today, a single estate can hold hundreds of apps, each carrying years of business logic and feeding a report that someone senior reads every week. That is why a quiet support date can turn into a boardroom question.

This page lays out the options in plain terms. It covers what changed in 2026, the three roads you can take, where Qlik's own tooling helps and where it stops, and what public sector and government teams should settle first. If you already know you are leaving Qlik, our detailed playbooks for Qlik to Power BI and Qlik to Microsoft Fabric go deeper.

Quick Summary

Qlik has not announced an end of life for QlikView, but individual releases carry support dates, and the oldest are already behind us. Qlik offers a free route into its own cloud, while Power BI and Fabric require a rebuild. The best choice depends on strategy, skills, and licensing, and the effort lies in validating results, not redrawing dashboards.

Key Takeaways

QlikView is not end of life, but releases expire. Version 12.90 lost vendor support on October 31, 2026, and 12.100 is supported through September 30, 2027.
Qlik's own route is free but not complete. Its migration tool moves most content to Qlik Cloud, and some items still need rework.
Power BI and Fabric are rebuilds. Qlik apps cannot simply be opened in Power BI, so the logic is re-authored.
The risk is silent. Numbers that stop matching rarely announce themselves, so validation matters more than visuals.
Public sector teams should choose the environment first. Authorization and feature availability decide what is allowed.

What Changed for Qlik Customers in 2026

The headline is reassuring, but the details are not. Qlik has said it has no plans to end-of-life QlikView or force customers onto Qlik Sense, and it continues to ship updates. But every release has its own support window, and those windows are closing on the older versions:

QlikView 12.80 ended support on October 31, 2025.
QlikView 12.90 ended support on October 31, 2026.
QlikView 12.100 is supported through September 30, 2027.
Qlik Sense Enterprise on Windows, in its May 2026 release, is supported through May 19, 2028.

These dates come from Qlik's published lifecycle pages and shift as new releases ship, so confirm the table for your exact version. The practical meaning is simple: if you run 12.90 or older, you are already outside vendor support, and if you run a current release, you have a clock, not a cliff.

What this means for you: The question is no longer whether to act, but when and in which direction. A support date is useful because it forces that conversation while you still have time to choose well.

Three Roads, One Decision

There are really three directions, plus the option to stay where you are.

Move to Qlik Cloud. This keeps Qlik's engine and your team's skills, and Qlik's own tool does much of the transfer. It suits organizations that like Qlik and mainly want to leave the servers behind.
Rebuild in Power BI. This suits organizations already standardized on Microsoft 365 and Azure that want one fewer analytics platform to license and staff. It is a genuine rebuild, which is why it deserves a careful plan. Our Power BI migration services and Power BI dashboard migration pages describe how that works.
Rebuild in Microsoft Fabric. This makes sense when the real goal is consolidating the data platform, not only the dashboards. It is a larger decision, and our Microsoft Fabric migration services page covers it. And if your direction is the reverse, bringing reporting into Qlik, see our Jaspersoft to Qlik migration article.

Path	Best When	Main Consideration
Stay and upgrade	Qlik skills and licensing are staying	Support dates recur with every release
Move to Qlik Cloud	You want to keep Qlik's engine	Some content needs rework, and licensing is typically capacity-based
Rebuild in Power BI	Microsoft is already your standard	A true rebuild, with logic and validation as the effort
Rebuild in Fabric	You are consolidating the data platform	A larger decision, with feature availability to check

What this means for you: Choose the destination for strategic reasons, such as skills, ecosystem, and cost over time, and not because a tool happens to be free.

Qlik's Own Route: Free Tooling, Real Limits

Qlik deserves credit here. Its Analytics Migration Tool is available through Qlik and certified partners at no charge, and according to Qlik's documentation, it moves content from Qlik Sense client-managed, QlikView, and NPrinting into Qlik Cloud. It carries across apps, users, groups, data connections, and reload tasks, and since version 2.5.0 in October 2026, it migrates task chains too. QlikView documents are converted into Qlik Sense apps, and each step can be validated and rolled back. A companion SaaS Readiness App profiles what you have and points to the most-used apps to move first.

The honest caveat is that no tool migrates everything. Independent write-ups note that extensions and the separation of development, test, and production environments often need rework, and users must be mapped carefully to your identity provider. Qlik's own planning guidance is blunt on this point: it calls the move a modernization effort, not a lift-and-shift, and starts with an audit.

What this means for you: If you intend to stay with Qlik, start with the free tool and a proper inventory. Treat its speed claims as vendor claims, and plan time for the content it does not carry across.

The Rebuild Route: Why Numbers Are the Hard Part

Rebuilding in Power BI or Fabric sounds like redrawing charts, but the charts are the easy part. The hard part is what sits underneath them.

Qlik works differently from Power BI. In Qlik, tables link automatically, and a click on any value filters everything in every direction. Power BI uses explicit relationships and a single filter path. Years of calculations, security rules, and data preparation have been written around Qlik's way of thinking, and a literal translation can produce a report that looks identical and quietly reports different figures. A total drifts, a filter stops reaching a chart, or a blank is counted as a zero.

That is why a careful rebuild starts with a complete inventory of what each app contains, redesigns the data model deliberately, and compares every important figure against Qlik under the same selections before anyone switches over. Our Power BI consulting services page describes the delivery side of that work.

What this means for you: Ask any partner how they prove the numbers match, not only how fast they convert. The answer tells you far more than a demo does. Engineers who want the specifics can jump to the technical section below.

What Public Sector and Government Leaders Should Settle First

This section is planning guidance for public sector and government teams. It is not a statement of DataTerrain's authorization status or past government work. For government, the platform question is often answered by the authorization boundary before any design begins:

Qlik Cloud Government. Qlik states that it is authorized at the FedRAMP Moderate impact level and DoD IL2, and is authorized for StateRAMP, for U.S. federal, state, and local agencies.
Power BI. Microsoft documents Power BI for U.S. government customers in GCC, GCC High, and DoD environments, available through a Microsoft 365 Government plan, with feature availability that differs between them and from the commercial offering.
Fabric. Microsoft's documentation says Fabric for GCC High has been submitted for FedRAMP High authorization and is under assessment, and that available items differ from the commercial service, so confirm each feature you plan to rely on.
Security and identity. Qlik's data-reduction security rules become row-level security in Power BI, and group membership must map to your government identity provider. Our guides to migrating row-level security and data security compliance explain the approach.
Records and timing. Preserve app definitions, scripts, and reload history before decommissioning, since public records and audit rules may require them, and let renewal and approval cycles set the schedule.

Verify current authorization and feature availability directly with each vendor, because both change and depend on the environment.

What this means for you: Decide the environment first. Choosing the wrong one can force a restart.

Looking Ahead: Migration in an AI-Assisted Era

The next two years will make conversion faster and cheaper, which changes where the value sits. Qlik's own converter already turns QlikView documents into Qlik Sense apps inside its migration tool, and commercial tools advertise AI-assisted conversion to Power BI. Power BI includes Copilot and natural-language questions, and Qlik has been previewing new ways to connect AI to analytics. Both vendors are investing in the cloud, so the decision is also about which roadmap you want to be on.

As conversion becomes routine, trust becomes the differentiator. Leaders judge a migration by whether they believe the numbers. The organizations that do this well treat validation as a first-class deliverable. They also design for change, with modular models, version control, automated tests, and a catalog that records ownership.

What this means for you: Plan for better tooling to arrive during your project. Build your process so each wave can use it without starting over.

A Practical Way to Start

You do not need to decide everything at once. A sensible first ninety days looks like this:

Inventory the estate. Count apps, scripts, extensions, reports, users, and security rules, and note which apps people use.
Retire what nobody uses. Every unused app is effort you do not have to spend. Our BI modernization checklist and enterprise BI migration services page cover this step in more detail.
Choose the destination. Decide with strategy, skills, and licensing in view, and confirm the environment if you are in government.
Pilot one representative app. Measure the effort, and reconcile every figure before scaling.
Validate before you switch. Run old and new side by side, and keep Qlik available for rollback until the results are signed off. Our reports conversion service supports that work.

For Your Technical Team: Translation Details

For the engineers, these are the main places Qlik logic changes meaning in Power BI:

Associations. Qlik's automatic links become explicit relationships, so synthetic keys, circular references, and link tables must be redesigned.
Set analysis. Expressions like Sum({<Year={2025}>} Sales) become CALCULATE patterns with filter modifiers, and a literal translation can override selections differently.
Aggr(). Qlik builds a virtual table, and DAX needs iterators over SUMMARIZE or VALUES, so totals must be checked separately from rows.
NULLs. Qlik excludes them, while DAX treats BLANK as equal to zero in comparisons.
Load scripts and QVD layers. This logic moves to Power Query, dataflows, or a warehouse, as with our legacy scripts service, and our automated ETL testing approach covers reconciliation.
Security and alternate states. Section Access becomes row-level security, OMIT rules become object-level security, and alternate states need disconnected tables.

An illustrative example, not a client engagement, with a note to verify against your own model:

-- Qlik
Sum({<Year={2025}>} Sales)

-- DAX
Sales 2025 = CALCULATE(SUM(Sales[Amount]), 'Date'[Year] = 2025)

Frequently Asked Questions

What are Qlik migration services?

They help organizations move QlikView and Qlik Sense content to a new home, either into Qlik Cloud using Qlik's own tooling, or onto Power BI or Microsoft Fabric as a rebuild. The work covers assessment, conversion, security mapping, validation, and cutover.

Is QlikView end of life?

No end-of-life has been announced, and Qlik says it has no plans to end-of-life QlikView or force migration to Qlik Sense. But individual releases expire: 12.90 ended support on October 31, 2026, and 12.100 is supported through September 30, 2027.

What is the Qlik Analytics Migration Tool?

It is Qlik's tool for moving Qlik Sense client-managed, QlikView, and NPrinting content to Qlik Cloud. It migrates apps, users, data connections, and reload tasks, supports validation and rollback, and is available through Qlik and certified partners at no charge, though some content still needs rework.

Can Qlik apps be converted to Power BI automatically?

Partly. Tools can extract app definitions and translate many expressions and layouts, but the data model, calculations, and security need expert redesign, and you should validate every key figure under identical selections before cutover.

What should government agencies check before migrating from Qlik?

They should first confirm the target environment's authorization boundary and feature availability, since Qlik Cloud Government, Power BI in GCC, GCC High, DoD, and Fabric in government clouds each differ. They should also map security rules to their identity provider and preserve records before decommissioning.

Scope Your Qlik Migration with DataTerrain

The costly mistake is choosing a destination because a tool is free or a dashboard looks easy, then finding out later that the numbers no longer match. DataTerrain brings 17+ years and 400+ clients in BI and reporting modernization, with automated inventory, conversion support, and validation of key figures against the results you already trust.

Talk to our migration team