---
title: "QlikView migration guide | Rig"
description: "Inventory the apps people still open, rebuild metrics and access in a warehouse semantic layer, run in parallel, then cut over. Stay in Qlik or move tools."
canonical: "https://rig.so/blog/qlikview-migration-guide"
format: markdown
---

[Migration guide](https://rig.so/blog/reporting)

# The metrics need a home when QlikView goes away

The QlikView apps people still open set the scope of a migration. Extract their metrics and access rules, rebuild them in a warehouse semantic layer, and cut over after a parallel run. Some teams stay on Qlik Sense or Qlik Cloud, and others move to another BI tool. Rebuild without a shared metric layer and the next tool drifts. Teams often use an AI-native data and systems integrator like Rig for the mapping and cutover.

By [Toby Mather](https://rig.so/blog/authors/toby-mather) · Published 20 November 2026

[Request a migration readiness check](https://rig.so/book-demo?offer=readiness_check&from=%2Fblog%2Fqlikview-migration-guide)

## Key takeaways

- QlikView apps hold their logic in load scripts, variables and chart expressions, and their access rules in section access.
- Staying in Qlik is a real option: Qlik’s Migration Center documents tools that convert QlikView documents for Qlik Sense and Qlik Cloud.
- Leaving for Power BI or another tool means rebuilding the scripts and expressions, so put the metric definitions on the warehouse first.
- Section access rules have to be rebuilt and tested, in the warehouse or the destination tool, before anyone switches off QlikView.
- Check Qlik’s official QlikView product lifecycle page for the current support dates of your version before you set a deadline.

1. 01**QlikView apps**
   
   Scripts, expressions and section access
2. 02**Inventory**
   
   Usage, owners and logic
3. 03**Warehouse semantic layer**
   
   Metrics and access rules
4. 04**Qlik Sense or Qlik Cloud**
   
   If you stay in Qlik
5. 05**Power BI or another tool**
   
   If you leave

QlikView apps move through a warehouse semantic layer, then stay in Qlik or move to another tool.

## QlikView, Qlik Sense and Qlik Cloud: what is the difference?

QlikView is Qlik’s original desktop and server BI product. Qlik Sense is its successor, available client-managed or as Qlik Cloud, Qlik’s hosted service. A move from QlikView to Qlik Sense or Qlik Cloud keeps you in the same engine and the same scripting language. A move to Power BI, Tableau, Sigma or another tool means rebuilding the logic in a different language.

## What do we inventory?

QlikView Server and Publisher logs show which documents people open and which reload tasks run. Qlik’s own migration guidance suggests archiving old, duplicate and unused applications before you start, and we agree, because it cuts the work in every later step.

For each surviving app, copy out the load script, the variables and the chart expressions. QlikView apps often calculate metrics in the script and again in the charts, so the same number may have two definitions inside one document.

- Documents, with usage, owners and reload schedules.
- Load scripts, QVD files and the sources they read.
- Variables and chart expressions that calculate metrics.
- Section access tables and the users and groups they reference.
- Publisher tasks, distributions and NPrinting reports.

## What order should the work go in?

Work through one team or app at a time.

1. Pull usage, archive unused and duplicate documents, and give every surviving app an owner.
2. Copy out scripts, variables, expressions and section access, and write one definition for each metric.
3. Build those metrics and access rules in a semantic layer on the warehouse, and move the data preparation out of the load scripts.
4. Rebuild the apps in Qlik Sense, Qlik Cloud or the destination tool on that layer, then run old and new in parallel and compare totals.
5. Cut over when owners sign off, move distributions and schedules, then retire QlikView Server and Publisher.

## Why put the metrics in the warehouse if we stay in Qlik?

Qlik will not be the only thing reading them. Finance spreadsheets, other BI tools and AI agents all query the same data, and they cannot read a Qlik load script. Defining the metrics once on the warehouse keeps every consumer on the same number, and it makes the next tool decision a front-end choice.

## Is QlikView already out of support?

Support depends on the version you run. Qlik publishes support dates per QlikView release on its official product lifecycle page, and versions drop out of support on a rolling basis as new releases ship. Check your version there, and confirm with your Qlik account team, before you set a deadline.

## QlikView migration checklist

Retire nothing in a wave until these are done.

- Usage pulled, unused documents archived, and every app has an owner.
- Scripts, variables and expressions copied out and reviewed.
- Each surviving metric defined once on the warehouse.
- Section access rebuilt and tested with real users.
- Totals match by period and segment for a full reporting cycle.
- Distributions and NPrinting reports moved or retired.
- QlikView Server and Publisher have a switch-off date.

## Where does Rig fit?

Rig is an AI-native data and systems integrator. A Qlik partner can run a move to Qlik Sense or Qlik Cloud, and a large systems integrator can staff a move to another tool. Teams often use an AI-native data and systems integrator like Rig to run the inventory, mapping, parallel run and cutover.

Rig Map holds the metric definitions on the warehouse, Gateway applies the access rules for people and agents, and Rig Migrate quotes a fixed delivery price once the scope is agreed. The QlikView migration page describes the service.

## Tools and approaches

[Qlik Migration Center](https://help.qlik.com/en-US/migration/Content/Qv2qsMigration/Home.htm)

Qlik’s documentation for moving QlikView documents to Qlik Sense and Qlik Cloud, including its conversion tools and planning guidance.

[Qlik: planning your migration to Qlik Cloud](https://help.qlik.com/en-US/migration/qv-planning-your-migration.htm)

A planning guide that recommends archiving old, duplicate and unused applications first.

[QlikView product lifecycle](https://community.qlik.com/t5/Product-Lifecycle/QlikView-Product-Lifecycle/ta-p/1826339)

The official support dates for each QlikView release, published by Qlik.

[Microsoft Power BI migration guidance](https://learn.microsoft.com/en-us/power-bi/guidance/powerbi-migration-overview)

Microsoft’s staged series for moving from another BI tool to Power BI.

## Common questions

How do you migrate off QlikView?

Pull usage and archive unused documents, copy out scripts, expressions and section access, define each metric once on the warehouse, rebuild the apps in Qlik Sense, Qlik Cloud or another tool on that layer, run both in parallel, then cut over.

Is QlikView already out of support?

It depends on your version. Qlik publishes support dates per QlikView release on its official product lifecycle page, so check your version there and confirm with Qlik before you set a deadline.

Can we stay on Qlik Sense?

Yes. Qlik documents tools for converting QlikView documents for Qlik Sense and Qlik Cloud. Some parts, such as extensions and styling, need rework, and the metrics still benefit from a warehouse definition.

What happens to the metrics when QlikView is retired?

They move to wherever you define them next. Defining them once on the warehouse means Qlik Sense, another BI tool and AI agents all read the same numbers.

Who runs the mapping?

An in-house team can do this with the vendor’s own tools, a systems integrator can staff the programme, or an AI-native data and systems integrator like Rig can run the mapping and cutover.

## Related reading

[Migrate off QlikView: Qlik alternatives and migration](https://rig.so/migrate/qlikview)[Reporting systems migration](https://rig.so/use-cases/bi-migration)[Migrate](https://rig.so/products/migrate)[Rig Map](https://rig.so/products/rig-map)[Gateway](https://rig.so/products/gateway)[Qlik vs Power BI: choose for the reporting you need](https://rig.so/compare/qlik-vs-power-bi)[Qlik alternatives in 2026](https://rig.so/alternatives/qlik)[Skip the metric map and the checklist was a waste of time](https://rig.so/blog/bi-migration-checklist)[If you just lift the dashboards, you haven’t migrated](https://rig.so/blog/legacy-bi-migration-guide)

## Sources

Vendor documentation checked on 20 November 2026. Confirm current features and terms with the vendor.

- [Qlik: Migration Center](https://help.qlik.com/en-US/migration/Content/Qv2qsMigration/Home.htm)
- [Qlik: planning your migration to Qlik Cloud](https://help.qlik.com/en-US/migration/qv-planning-your-migration.htm)
- [Qlik: QlikView product lifecycle](https://community.qlik.com/t5/Product-Lifecycle/QlikView-Product-Lifecycle/ta-p/1826339)
- [Microsoft: Power BI migration overview](https://learn.microsoft.com/en-us/power-bi/guidance/powerbi-migration-overview)

## About the author

[Toby Mather](https://rig.so/blog/authors/toby-mather), Co-founder and CEO, Rig. Toby co-founded Rig after seeing how hard it was for business teams and AI to work with complex internal data. He was previously co-founder and CEO of Lingumi and CPO at Novakid.

Talk to Rig

## Check the migration before you commit to it

An engineer sends a short written view of the scope, systems and risks, then offers a call to go through it.

[Request a migration readiness check](https://rig.so/book-demo?offer=readiness_check&from=%2Fblog%2Fqlikview-migration-guide)[Book a call with an architect](https://rig.so/book-demo?offer=architect_call&from=%2Fblog%2Fqlikview-migration-guide)

---

- [This page as HTML](https://rig.so/blog/qlikview-migration-guide)
- [Site map for language models](https://rig.so/llms.txt)
- [API and agent documentation](https://rig.so/developers)
