Legacy BI migration / QlikView
Keep your reporting when you leave QlikView
Changing QlikView starts with knowing what the business depends on. Map the reports and models, rebuild the ones people use and check each report before cutover.
Systems, data and dependencies
System changes, models and reports
Reconcile before switching off
Scope and checks agreed before delivery
Where QlikView actually stands
Qlik has not announced an end of life for QlikView. Each release gets roughly two years of support; the dates below come from Qlik's own pages, with what each one means for you.
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.
Qlik's Analytics Migration Tool goes live
Qlik's own tool for planning a move to Qlik Cloud, with support for QlikView and NPrinting. Every migration route Qlik offers out of QlikView ends in Qlik Cloud.
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.
QlikView to Qlik Sense converter, version 1.3
Converts QlikView sheets, layout, styling, expressions and 25+ object types into Qlik Sense, so converting within Qlik takes less work than it used to.
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.
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 deadline most QlikView teams face next.
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.
Map before you move
Find the reports, models and workflows people use. Separate the business-critical work from the reports and models you can retire.
Agree scope and price
Our engineers use the map to plan the move. Agree the deliverables, validation checks and fixed price before work starts.
Keep your numbers consistent
Rebuild reporting on governed definitions and compare it with the originals. Keep history, permissions and the business context behind the numbers.
Where every QlikView artefact goes
Nothing is machine-translated: people rewrite the logic, informed by usage, and a number-by-number parity check proves the rewrite.
| 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. People rewrite, review and test them; nothing is 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, and to every document. |
What you won't have
QlikView's associative selection model does not come across. Clicking a value and watching the whole document filter, with the excluded values greyed out, is what QlikView users like most. Rig answers questions and drills into dashboards instead, and someone on your team will miss the old way.
Rig does not produce pixel-perfect formatted reports. If you use NPrinting for branded PDF or Excel packs in a fixed layout, scheduled runs with Slack and email actions will not replace every template. Tell us on the call which templates matter, and keep those running.
There is no on-prem or air-gapped option. QlikView runs on your own Windows servers, while Rig runs in our cloud, or in your own cloud account on Enterprise. If the data cannot leave a building with no internet, Rig will not work for you.
We have no automatic converter. Nobody can turn a ten-year-old load script into clean SQL unattended, and we do not claim to. Our team rewrites the logic with you, and the parity check shows whether the rewrite is right.
Qlik's own conversion route may cost less. If your contract lets you move QlikView licences onto Qlik Sense or Qlik Cloud on good terms, that could be the cheapest option for the licence line, so get Qlik's quote before you decide.
What you get that you don't have today
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 you own
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
You stop running QlikView Server and Publisher, patching Windows servers and planning around reload windows. Pipelines and models run on a schedule in the cloud.
Unlimited seats
Every tier has unlimited seats, from $499 a month, so nobody is priced out of opening a dashboard or asking a question.
We do the migration, for free
We rebuild the sources, the load-script logic, the metrics and the dashboards people actually open, and run them beside QlikView until the numbers match.
Dashboards and automations on top
The jobs a QlikView estate runs NPrinting, Publisher and a scheduler for are included, and they use the same certified metrics.
The logic is finally readable
Often only the person who wrote a load script or a set analysis expression knows what it does. dbt models and certified metrics are SQL with plain-English descriptions, versioned in git.
Customer story / An education software group
One data and reporting layer for a merged group, without the technical debt
A Tableau and Fivetran migration, shown for the method: it is not a QlikView project.
After two education software companies merged, the group is bringing both companies’ warehouses, pipelines, BI and CRM data onto one governed data and reporting layer in Snowflake. It is rebuilding only what people use, and retiring tools as it goes.
Read the storyCommon questions
Is QlikView end of life?
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.
When does support for my QlikView version end?
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.
Can we keep running QlikView unsupported?
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, which is reasonable as long as you have decided when to stop.
Should we just take Qlik's offer to convert to Qlik Sense?
Get the quote and compare it with the other options. 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.
What happens to our QVD files?
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.
Can Rig convert our load scripts automatically?
No. Be wary of anyone who says software 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.
What happens to set analysis and our chart expressions?
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.
We use NPrinting. What happens to it?
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.
How long does a QlikView migration take?
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.
How is Rig priced?
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.
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, agreed before you start.
Talk to Rig
What work do you want to improve?
Tell us where your team spends time, loses money or needs better information.
In a 30-minute call, we’ll discuss the data and systems work that could help.