Support for QlikView 12.90 ends 31 October. What's your next move?
Qlik still ships QlikView, most recently on 29 September 2026. It stopped selling perpetual licences in 2021, supports each release for roughly two years, and is building its road off QlikView towards Qlik Cloud. Here are the real dates, your three options and what each costs, including the one where your data and logic end up in a warehouse you own, rebuilt by us for free.
Where does QlikView actually stand?
Short version: QlikView is not end of life, and Qlik has not announced that it will be. It is also not where Qlik is investing. Each release gets roughly two years of support, after which Qlik asks you to upgrade. Here is every date that matters, from Qlik's own pages, and what each one means for you.
- 1 Apr 2021
No more perpetual licences
Qlik stopped selling perpetual licences for QlikView to new and existing customers. You can keep renewing maintenance on the licences you own, but adding users means a subscription.
- 24 Jul 2025
Qlik's Analytics Migration Tool goes live
Qlik's own tool for planning a move to Qlik Cloud, with support for QlikView and NPrinting. Qlik is building the road off QlikView, and it leads to Qlik Cloud.
- 31 Oct 2025
Support ends for 12.80 (May 2023)
If you are on 12.80 or anything older, you are already outside support. Qlik's lifecycle page says support will require you to upgrade.
- 8 Apr 2026
QlikView to Qlik Sense converter, version 1.3
Converts QlikView sheets, layout, styling, expressions and 25+ object types into Qlik Sense. Converting is easier than it was, which is worth knowing before you compare options.
- 29 Sep 2026
QlikView September 2026 released
QlikView is still being maintained. This release drops Windows 10, deprecates Source Control and the Workbench, and says the IE plugin goes in a September 2027 release. Its end of support date is not yet published.
- 31 Oct 2026
Support ends for 12.90 (May 2024)
If you are on 12.90, upgrade by the end of October 2026 or run unsupported. This is the date most QlikView teams are actually up against.
- 30 Sep 2027
Support ends for 12.100 (September 2025)
Even the release before the newest one has about a year left. Each recent release has had roughly two years of support, so staying supported means upgrading about once a year.
Qlik has not announced an end of life for QlikView as a product, or an end of support date for QlikView as a whole. Version end of support is not product end of life. What Qlik has said: its modernisation programme FAQ (2020) promises to "continue to support current QlikView customers into the future", and in May 2026 a Qlik Support engineer wrote on Qlik's community that QlikView and NPrinting "will be maintained for many years but most resources are being put into Qlik Cloud". Maintained, not growing. Anyone who tells you QlikView is end of life is wrong, and anyone who promises it a long future is guessing.
What are my options, and what does each cost?
Not a calculator, on purpose. QlikView licence prices are not public, so any number we put against your current bill would be invented. What is public: Qlik Cloud's list prices, the terms Qlik set out for converting QlikView customers, and Rig's tiers. These are the options a QlikView customer actually has.
| Option | What you pay | What you get | The catch |
|---|---|---|---|
| Stay on QlikView | Your current annual maintenance. No new perpetual licences are sold, so growing means a subscription | The apps you have, unchanged, on releases Qlik supports for roughly two years each | Upgrade about once a year to stay supported, Windows servers to run, and a product Qlik is maintaining rather than growing |
| Convert through Qlik's modernisation programme | In Qlik's 2020 programme FAQ: annual QlikView maintenance plus 30%, minimum three-year term on subscription, across the whole estate. Ask Qlik for current terms | Qlik Sense Enterprise for the same users, and you keep QlikView | A three-year commitment, and the apps still have to be converted and checked in Qlik Sense |
| Move to Qlik Cloud Analytics | Starter $300 a month (10 users, 10 GB); Standard $825; Premium $2,750; Enterprise quoted. Billed annually | Qlik's SaaS, the same engine and script language, and Qlik's converter and migration tools to get there | Priced on data capacity from Standard up, so the bill follows how much data you load. QlikView apps uploaded as they are can be viewed but not reloaded |
| Move to a warehouse and Rig | Start $499 ($899 on your own warehouse); Grow $2,999; Scale $4,999 a month. Unlimited seats on every tier | Your data in a warehouse you own, dbt models, certified metrics, dashboards and governed AI access | A real rebuild: load scripts and expressions are rewritten, not converted. No associative engine |
Qlik Cloud Analytics prices from qlik.com/us/pricing, billed annually, checked 2 October 2026. Starter includes 10 users; Standard and above include unlimited users and are sized on data capacity. Programme terms are from Qlik's own customer FAQ, dated 2020, which says the offer may be withdrawn at Qlik's discretion, so ask Qlik for today's terms. QlikView licence prices are not published. Rig tiers are the public ones on the pricing page. The rebuild itself is free, done by us and run beside QlikView until the numbers match.
Staying put has a cost too
No new features, a support clock that runs down release by release, and Windows servers someone has to keep patched. The licence line may be paid off. The risk line is not.
Converting is the shorter path
Qlik's converter moves sheets, layout and expressions into Qlik Sense, and you keep the engine and the script language. It is still a project, and the logic stays in Qlik's language on a new contract.
The script is the real asset
Whichever way you go, the value is in the load scripts and expressions: years of business rules. Where they end up, and who can read them afterwards, matters more than the licence line.
What teams have built on Rig
Three published case studies. None of them is a QlikView migration, so we are not going to dress them up as one. Birdie is the closest: a team that left an older BI stack and now builds its own reporting. They show what happens once the data is in a warehouse and the metrics are certified.
Reporting that took three months in the old Looker stack now ships in a day, built by the teams themselves, with 15+ dashboards and agents in weekly use.
Read the case studyA 4,000-table warehouse opened to fraud, ops, support and marketing through one governed context layer. 16 weeks from a fraud-team pilot to org-wide rollout.
Read the case study40+ sources in one warehouse, then every core metric certified against the spreadsheets the team already trusted.
Read the case studyDo I lose my data, my history or my logic?
No, but it is worth being precise, because QlikView keeps things in places a warehouse does not. Data sits in memory inside each .qvw and in QVD files on a file share. The logic sits in load scripts and chart expressions. Permissions sit in section access, inside each document. Each of those has a home on the other side.
| In QlikView | On Rig | How it gets there |
|---|---|---|
| QVD files | Warehouse tables | Reloaded from the original sources where they still exist. Where a QVD is the only copy of some history, QlikView's own STORE statement writes it out as a text file, and that lands in the warehouse as a table. |
| Load scripts | dbt models | The extract, the joins, the ApplyMap lookups and the business rules buried in the script become SQL models in a git repository you own. Rewritten, reviewed and tested, not machine-translated. |
| Chart expressions and set analysis | Certified metrics | Sum({<Year={2025}>} Sales) becomes a named metric with its SQL, filters and description attached, certified once and used by every dashboard, agent and question. |
| .qvw apps and sheets | Dashboards and data apps | Rebuilt on the certified metrics, starting with the apps people actually open. Most estates have more apps than readers. |
| Section access | Row, column and role-level access | The reduction rules move out of each app and into the data layer, so they apply to every dashboard, query and AI agent, not just to one document. |
Keep the QlikView server and its files until the parity check is signed off. Nothing on the QlikView side is deleted by the move, and the old apps stay as a reference you can open for as long as you keep them.
How painful is the move, and who does the work?
Our team does the rebuild, and it costs you nothing. What we need from you is access to the QlikView server and source systems, and someone who can tell us which numbers the business actually runs on.
- 1
Inventory
Every .qvw, every QVD, every reload task and which source each one reads. Then usage: which apps people open, and which have not been opened in a year. Most of the saving is found here, before anything is rebuilt.
- 2
Parallel build
Sources land in the warehouse, load-script logic is rewritten as dbt models, and the expressions that matter become certified metrics. QlikView keeps running throughout. Nothing in production changes.
- 3
Number-by-number parity check
Each certified metric is compared against the QlikView figure for the same filters and period, until they agree. Where they do not, we find out which one was wrong, and it is not always the new one. You see the diff, not a promise.
- 4
Cutover
Users move app by app, starting with the most used. You switch QlikView off when the last app you care about has moved, and not before.
Will I have everything I have today?
Not everything, and the differences are in the next section. Here is the honest mapping, QlikView on the left.
| Capability | QlikView | Rig |
|---|---|---|
| Exploration | The associative model: click a value and everything related and unrelated lights up across every sheet | Ask in plain English, or drill a dashboard. Powerful, but not the green, white and grey selection model |
| Calculations | Chart expressions and set analysis, defined per object or as master items | Certified metrics in SQL, defined once and reused everywhere, with the definition visible to anyone |
| Data preparation | Load script, QVDs, often a QVD generator layer feeding other apps | Ingestion on dlt into your warehouse, transformations in dbt Core |
| Where data lives | In memory inside each .qvw, and in QVD files on a file share | Your own Snowflake, BigQuery, Databricks or Redshift. Or Rig hosts one |
| Security | Section access, written into each document's script | Row, column and role-level access on the data itself, plus PII detection |
| Scheduled reporting | NPrinting for formatted reports; Publisher for reloads and distribution | Scheduled and triggered runs, with Slack, email and CRM actions. Not pixel-perfect report layouts |
| Deployment | On your own Windows servers (QlikView Server and Publisher) | Rig cloud, or inside your own cloud account on Enterprise. No on-prem servers |
| AI access | None in QlikView | Rig agents, plus one governed MCP endpoint for Claude, ChatGPT or Cursor |
What won't I have?
Five things, stated plainly, because you would find them in week two anyway.
The associative experience. Clicking a value and watching the whole document filter, with the excluded values greyed out, is the thing QlikView users love most. Rig answers questions and drills dashboards, but it does not reproduce that selection model, and someone will miss it.
Pixel-perfect, formatted reports. If you run NPrinting to produce branded PDF or Excel packs to a fixed layout, Rig's scheduled runs with Slack and email actions are not a like-for-like replacement for every template. Keep the ones that matter and tell us which on the call.
On-prem and air-gapped. QlikView runs on your own Windows servers. Rig runs in our cloud, or in your own cloud account on Enterprise. If the data cannot leave a building with no internet, Rig is not the answer.
No automatic converter. Nobody should promise you a tool that turns a ten-year-old load script into clean SQL unattended, and we do not. Our team rewrites the logic with you, and the parity check is how we prove it was rewritten correctly.
Qlik's own conversion route. If you are entitled to move your QlikView licences onto Qlik Sense or Qlik Cloud on favourable terms, that may be the cheapest path on paper for the licence line, and you should get Qlik's quote before you decide.
What do I get that I don't have today?
QlikView puts the data, the logic and the screen in one file. That made it fast to build and hard to share. Pulling them apart is where most of the gain is.
One definition of every number
In QlikView the same KPI is often written into five apps five slightly different ways. On Rig it is one certified metric with its SQL attached, and every dashboard and question uses it.
Your data in a warehouse, not in a document
Data moves out of .qvw files and QVDs on a file share into a warehouse you own and any tool can read. No more reload chains where one document has to finish before the next can start.
Governed AI access, built in
Point Claude, ChatGPT or Cursor at one MCP endpoint, with row and column permissions, cost-checked SQL and a full audit log. QlikView has no equivalent.
No servers to keep alive
No QlikView Server, no Publisher, no Windows patching, no reload windows. Pipelines and models run on a schedule in the cloud.
Unlimited seats
On every tier, from $499 a month. Nobody is priced out of opening a dashboard or asking a question.
We do the migration, for free
Sources, load-script logic, metrics and the dashboards people actually open, rebuilt by us and run beside QlikView until the numbers match. No charge for the build.
Dashboards and automations on top
The things a QlikView estate needs NPrinting, Publisher and a scheduler for. Included, and generated from the same certified metrics.
The logic is finally readable
Load script and set analysis live in the heads of the people who wrote them. dbt models and certified metrics are SQL and plain-English descriptions, versioned in git.
Why not just convert to Qlik Sense or Qlik Cloud?
Often you should. If your team loves the associative model, the load scripts are in good shape and the people who wrote them are still around, converting is the shortest path, and Qlik has built tools for exactly this. Here is a fair comparison.
| Qlik Sense or Qlik Cloud | Warehouse and Rig | |
|---|---|---|
| Effort to move | Lower. Same engine and script syntax, and Qlik's converter carries sheets, layout and expressions across | Higher. Load scripts become dbt models and expressions become metrics, rewritten by people and checked number by number |
| Associative exploration | Kept. It is the same engine | Not kept. Plain-English questions and dashboards instead |
| Where the data lives | In Qlik apps and QVDs, or in Qlik Cloud's data capacity | In your own warehouse, readable by any tool |
| Where the logic lives | Qlik load script and set analysis, run by Qlik's engine | SQL in dbt and certified metrics, in a git repository you own |
| Pricing | Qlik Cloud from $300 a month for 10 users, then capacity-based from $825. Or the modernisation programme's maintenance uplift | Public tiers from $499 a month, unlimited seats on every tier |
| Formatted reports | NPrinting, which still supports QlikView connections, and reporting in Qlik Cloud | Scheduled runs with Slack and email actions. Not pixel-perfect templates |
| AI | AI features inside Qlik Cloud | Rig agents, plus one governed MCP endpoint for Claude, ChatGPT or Cursor |
| On-prem | Qlik Sense Enterprise on Windows is still supported | No. Rig cloud, or your own cloud account on Enterprise |
The question underneath is where you want your business logic to live for the next ten years. Converting keeps it in Qlik's script language on Qlik's engine. Moving to a warehouse puts it in SQL that any tool, any analyst and any AI agent can read.
What if Rig shuts down?
A fair question to ask a younger company, especially when the reason you are here is a vendor deciding where its product goes next. The answer is structural. You own the warehouse. The transformations are dbt Core. The ingestion is dlt. Both are open source, both run without us, and neither is a format only we can read.
Compare that with where you are today: business logic in load scripts that only the QlikView engine runs, and history in QVD files that only Qlik products read natively. If we disappeared tomorrow, your pipelines are Python modules and your models are SQL files in a repository you control, writing into a warehouse you pay for directly. What you would lose is the context layer and the interface, not the data and not the logic.
Everything else
No. Qlik has not announced an end of life for QlikView, and it released a new version on 29 September 2026. What ends is support for each individual release, roughly two years after it ships: 12.80 (May 2023) went out of support on 31 October 2025, and 12.90 (May 2024) goes out of support on 31 October 2026. Qlik stopped selling perpetual licences in April 2021, and a Qlik Support engineer wrote in May 2026 that QlikView will be maintained for many years while most resources go into Qlik Cloud.
From Qlik's lifecycle page: 12.100 (September 2025) on 30 September 2027; 12.90 (May 2024) on 31 October 2026; 12.80 (May 2023) ended 31 October 2025; 12.70 (May 2022) ended 10 May 2024; 12.60 (May 2021) ended 25 May 2023. The September 2026 release does not have a published end date yet. Once your version is past its date, Qlik asks you to upgrade before it will help.
The software keeps working. What you lose is Qlik's help when something breaks, and fixes for problems found later. The servers underneath matter too: the September 2026 release no longer supports Windows 10. Plenty of teams run an old version for a while. It is a risk you take on knowingly, not a plan.
Get the quote, and compare it honestly. If your team relies on the associative model and the load scripts are in good shape, converting is the shortest path, and Qlik's converter now carries sheets, layout and expressions across. Qlik's 2020 programme FAQ priced it as your annual QlikView maintenance plus 30%, over at least three years, across the whole estate; terms may have changed. Move to a warehouse instead if you want the data and the logic outside Qlik.
Nothing, until you decide. Where the original sources still exist, we reload from them into the warehouse. Where a QVD holds history nobody else has, QlikView's own STORE statement can write it out as a text file, which then lands in the warehouse as a table. Keep the QVDs until the parity check is signed off.
No, and be wary of anyone who says they can do it unattended. Our team rewrites the script logic as dbt models with you, informed by an inventory of what is actually used, and the number-by-number parity check proves the rewrite is right. The result is SQL in a repository you own.
The ones the business relies on become certified metrics: a name, a description and the SQL behind it, defined once and used by every dashboard, question and AI agent. That is usually where a QlikView estate shrinks most, because the same KPI is often written into several apps slightly differently.
NPrinting's May 2026 release still supports QlikView connections, so it can keep running while you move. On Rig, recurring reports run on a schedule and go out through Slack or email. If you depend on tightly formatted PDF or Excel templates, tell us which ones on the call, because that is where Rig is weakest.
It depends on how many apps people actually open, which is why the inventory comes first. A handful of apps on a few sources moves in weeks. A large estate with a QVD generator layer and hundreds of documents is phased app by app. You get a plan with a fate for every app before anything is rebuilt.
A monthly platform fee plus credits for the work Rig does, from $499 a month, with unlimited seats on every tier and nothing charged per row. The tiers and the calculator are on the pricing page. The rebuild itself is free: we do it, and it runs beside QlikView until the numbers match.
Start with your QlikView app list
Twenty minutes. Bring a list of your .qvw apps, roughly who opens them, and the version you are on. We'll tell you which ones we would rebuild first, which we would not bother with, and what Rig would cost once you are live. If the honest answer is Qlik's own conversion route, we'll say so.
Twenty-minute call and a first look at your app list
Inventory of every app, QVD and reload task, with who actually opens them
A rebuild plan with a fate for every app, then we start building, free
Rig against the other tools people weigh it with
Per-row pricing against a flat fee, with a calculator
Foundry and the Ontology, in plain terms
Ingestion that comes with the context layer
Where the context layer sits against the rest
QlikView release and support dates checked 2 October 2026 against Qlik's product lifecycle pages and release notes on community.qlik.com, Qlik Cloud prices against qlik.com/us/pricing. Qlik changes these; if something here has moved, tell us and we'll fix it. QlikView, Qlik Sense, Qlik Cloud and NPrinting are Qlik's names, used here only to describe their products. Rig prices are the public tiers on rig.so/pricing. Customer figures are from Rig's published case studies.