Qlik Elite Channel Partner · Upgrade & Migration Services

QlikView Migration: Assess First, Then Decide What’s Worth Moving

QlikView migration isn’t a “move everything” exercise. Of the dozens of apps most enterprises have accumulated, only a fraction are actually still in use. Our approach starts with an inventory and triage, rebuilds only what still carries value, and keeps a rollback path at every step.
Book a Free Assessment See Our Qlik Service Scope
24 months
Vendor support window per release
6–16 weeks
Typical project timeline
Reversible
Phased cutover
EN · 繁中 · 粵語
Hong Kong time zone support

What Is QlikView Migration

QlikView migration is the process of moving existing QlikView applications to Qlik Sense or Qlik Cloud Analytics. Because the two platforms structure applications differently, this isn’t a simple version upgrade — apps need to be rebuilt, though script logic and data models can usually be carried over largely intact.

The real workload isn’t the technical conversion — it’s the triage: which apps are still in active use, which can be retired outright, and which are worth rebuilding from scratch while you’re at it. Get that step right, and the project is often far smaller than clients initially expect.

Beyond QlikView-to-Qlik-Sense, we also handle on-premises-to-cloud migration, migration between cloud platforms, Qlik NPrinting environment migration, and Qlik Sense version upgrades. See the full scope on our services overview.

QlikView Migration: How Urgent Is It, Really

Let’s start with something you may not have heard elsewhere: Qlik has not announced end-of-life for QlikView, and the vendor has stated there are currently no plans for a final release. So we won’t be telling you “QlikView is being discontinued, migrate now” — because that’s not true.

The real pressure comes from two places. First, since version 12.60, the vendor provides only twenty-four months of technical support per initial release. Second, some legacy components are being phased out — for example, QlikView OCX and QlikView Source Control will no longer be maintained or supported starting with the September 2026 release.

So whether this is urgent for you isn’t a matter of rumor — it depends on which row of the table below your current version falls into.

VersionRelease DateSupport EndsYour Status
12.100Sept 202530 Sept 2027Supported
12.90May 2024Oct 2026Window closing
12.80May 202323 May 2025Unsupported
12.70May 202210 May 2024Unsupported
12.60 and earlierMay 2021 and earlierMay 2023 and earlierUnsupported

Lifecycle dates are as published by the vendor; refer to the official Qlik QlikView lifecycle page for the authoritative version. This table is for quick reference only.

🟢

Still Supported: Plan at Your Own Pace

No need to rush. Start with an application inventory, work out what’s actually still in use, and build migration into your budget over the next one to two years. The inventory itself doesn’t take long, but it gives every later decision something to stand on.

🟡

Window Closing: Time to Start the Inventory

Once support ends, you’re on your own if something breaks. This is the point to start the inventory and a pilot rebuild — validate the approach works, then decide whether to upgrade to a newer QlikView release to buy time, or move straight to Qlik Sense.

🔴

Unsupported: Risk Is Accumulating

An OS or database upgrade can break things at any point, and the vendor won’t help when it does. Even if you’re not ready to migrate immediately, we’d recommend an environment health check first, just so you know where the exposure is.

QlikView Migration: How We Do It

Five phases. By the end of the first two, you’ll have a complete application inventory and a workload estimate — that’s a good point to decide whether to continue, and there’s no cost to stopping there.
1
Application Inventory
Catalog every QlikView app, script, data source, and actual usage pattern. Most clients discover at this stage that more than half their apps haven’t been opened in a long time
▼
2
Triage & Prioritization
Sort into rebuild, simplify-and-rebuild, and retire. The workload cut at this stage is usually far larger than anything technical optimization saves later
▼
3
Pilot Rebuild
Pick one or two representative apps to rebuild first, validating how much script logic carries over, the data model, and performance — and calibrating the overall estimate
▼
4
Parallel Validation
Old and new environments run side by side, numbers compared app by app. The old system doesn’t get switched off until the business confirms the new figures match
▼
5
Cutover & Handover
Cut over in batches, each with a clear rollback trigger. Your team is trained to make changes themselves; we move into a backend support role

Figure 1 — The five phases of a migration project

Phase four is the one most likely to get squeezed — and the one that shouldn’t be. Skip parallel validation and cut straight over, and if something goes wrong you have no baseline to compare against and no way back. Our approach is to keep the old environment running until the business signs off, and that commitment goes into the proposal in writing.

Not Just QlikView to Qlik Sense
Migration comes in several forms. The methodology is similar across all of them, but the risk points differ. We handle all four of the following.
🔀 QlikView → Qlik Sense
Apps need rebuilding, but scripts and data models largely carry over. The focus is triage and parallel validation.
☁️ On-Premises → Cloud
Qlik Sense on-premises to Qlik Cloud Analytics. The focus is data source connectivity, the permission model, and redesigning network egress.
🌐 Cloud-to-Cloud Migration
Migration between cloud providers. The focus is version and licensing constraints, and service continuity during cutover.
📬 Qlik NPrinting Migration
Reporting environments are often overlooked. Connection settings, report templates, distribution rules, and recipient lists all need to be validated.
⬆️ Qlik Sense Version Upgrades
Relatively straightforward, but extensions and custom connectors can break post-upgrade — a compatibility check beforehand is essential.
🧯 Taking Over an Unmaintained Environment
Former consultant is gone, no one internally can read the scripts. We start with a health check and documentation, then discuss whether migration makes sense.

Six Questions to Answer Before You Start

If you can’t answer these six before kicking off a migration, you’ll be redoing work later in the project. Try answering them yourself first and see how many you can get through.
📋

How many apps are actually in use

Not how many files sit on the server — how many are actually still being opened. The two numbers are often several times apart.

Can’t answer → start with an inventory, not a technical plan
👥

Who uses them, and how often

Daily users, monthly users, once-a-year users all need different handling. Some apps are better converted to a scheduled report than rebuilt at all.

Can’t answer → pull a month of access logs first
🧾

Who understands the scripts today

Is the original author still around? If not, migration is also a chance to document the logic properly — don’t waste it.

No one does → budget script review time into the inventory phase
🔌

Are the data sources changing too

If the ERP or database is also being replaced, it’s best to sequence the two projects rather than run them together — doing both at once makes it impossible to trace which change caused what.

Yes → settle the sequencing before scheduling either
📄

Do your licenses cover it

Qlik Sense and QlikView use different licensing models — user counts and usage patterns need recalculating. Skip this and the budget will run over.

Not sure → include a licensing review in the inventory phase
🕐

Are there blackout periods

Month-end, quarter-end, and year-end close are usually off-limits. Mark out cutover windows early, or a last-minute delay gets forced on you.

Yes → block those periods out before scheduling

For official product line and version details, see the Qlik website. We’re happy to walk through these six questions with you in a free consultation — no need to prepare anything in advance.

Frequently Asked Questions

Timeline, cost, risk, and how we take over an existing environment — here are the five questions clients ask us most.
A typical project runs six to sixteen weeks, depending on how many apps need rebuilding and how complex the data sources are. We quote a fixed price against scope and deliverables — not open-ended time-and-materials billing. In practice, we recommend starting with the inventory and triage phases; once those are done, you’ll have an app list and a workload estimate, and that’s when the quote becomes accurate. The inventory phase can also be commissioned on its own, with no obligation to continue.
Not directly — the two platforms structure applications differently, so apps need to be rebuilt. Script logic and data models, however, usually carry over largely intact, which is where most of the workload savings come from. Visual layout and interaction design typically need to be reworked, since Qlik Sense’s interaction model differs from QlikView’s — porting the old interface over as-is usually makes it worse to use, not better.
Yes. We keep the old environment running until the business confirms the new figures match, and cutover happens in batches, each with a clear rollback trigger written into the proposal. That’s also why we don’t recommend compressing the parallel validation phase — without a baseline to compare against, there’s nothing to roll back to.
Yes, this is a fairly common situation. We typically start with a health check of the environment and applications, list out the risk items and areas for improvement, fill in any missing documentation along the way, and then discuss how to move forward. It’s also fine to engage us for just the health check and ongoing support, without touching the existing architecture at all.
Yes. In some cases, upgrading to a newer QlikView release to buy another couple of years, or converting a handful of apps to scheduled reports, costs far less than a full migration. We’d rather turn down a project than deliver a new environment nobody uses. The inventory report lays out the cost and risk of each option — the decision is yours to make.
Qlik®, Qlik Sense®, Qlik Cloud Analytics®, Qlik NPrinting®, and QlikView® are trademarks or registered trademarks of QlikTech International AB. ATP International is an authorized Qlik partner and is not a division or subsidiary of Qlik. Version lifecycle dates referenced on this page are as published by the vendor and are subject to change per vendor policy.
Start With an Assessment Before You Decide
Tell us which version you’re currently running and roughly how many apps you have, and we can give you a preliminary read. The first consultation is free.
Book a Free Assessment Email Us
Qlik Service ScopeLicensing, deployment, dashboards, and local support Services OverviewQlik implementation, data warehousing, and AI development About ATP InternationalCompany background, dual-city team, and partner credentials Contact UsInquiry form and email