16 November 2026

Still using QlikView in 2026?

Share this message

Classic QlikView dashboard with charts and list boxes, overlaid with a diagonal blue banner reading 'Still on QlikView in 2026?'

You probably have your reasons. But are they still good reasons?

Even in 2026, many organizations still use QlikView. Sometimes as their primary BI platform, sometimes for a handful of applications that were never migrated, and sometimes for uses QlikView was never really intended for.

That doesn’t surprise me. QlikView is an excellent product. I’ve worked with it for almost twenty years and co-authored the book QlikView for Developers with Miguel García. I’ve built all kinds of things with it, from business-critical applications to animated Christmas trees. Simply because I could.

So I’ll be the last person to say you should replace QlikView just because something newer is available. I drive a nearly thirty-year-old car every day, so holding on to old technology is hardly unfamiliar to me. But a lot has changed since Qlik Sense was introduced in 2014.

A well-used copy of QlikView 11 for Developers by Miguel García and Barry Harmsen, with colorful bookmarks sticking out between the pages.

If your organization still uses QlikView, is that a conscious decision? Or is it one that was made long ago and has never been questioned since?

The reasons I hear are technical, financial, or organizational, and usually a combination of the three. In practice, there are six situations I encounter regularly.

The most obvious reason. An investment was made at some point, the applications do what they are supposed to do, and nobody is complaining. If you bought the licenses outright, you often only pay maintenance now. That fee is indexed every year, so it keeps going up. Yet many organizations assume, not entirely correctly, that switching to a subscription would cost much more.

Your Qlik partner may also be perfectly happy with the situation. Some partners actively help you think ahead, but I also encounter situations where the relationship barely extends beyond the annual invoice. If no one points out new possibilities, you are unlikely to explore them yourself.

Then there are organizations and users working with QlikView Desktop Personal Edition. They pay nothing at all and can still do quite a lot within the limitations of that edition.

If you are satisfied with what you have, changing for the sake of change is pointless. But being satisfied does not necessarily mean you have the best solution.

When was the last time you took a serious look at what is possible today?

Understandable. When Qlik Sense was released in 2014, it was still far from a full-fledged replacement. It looked modern, but to experienced QlikView developers, it felt like a step backward. The first version didn’t even have a pivot table!

At the time, Qlik presented those limitations under the banner “Gorgeous and Genius” as deliberate design choices. I didn’t find that very convincing even then: missing functionality does not become an advantage just because you call it a best practice.

We’ve come a long way since then. In my view, Qlik Sense has been functionally on par with QlikView for several years, while Qlik Cloud has added many capabilities for collaboration, automation, distribution, and AI. The tooling for migrating QlikView applications has also improved. Not everything transfers one-to-one, but that is different from the functional gaps that existed back then.

If you last looked at Qlik Sense in 2017 or 2018, it’s time to reconsider your assessment.

I see it regularly: organizations that use Qlik Sense, Qlik Cloud, or Power BI but still have a few QlikView applications running. Sometimes, a migration project tackled the easy work but left the complex parts untouched. Sometimes, new work simply started on the new platform, or the QlikView apps were published to Qlik Cloud without being reworked. The Analytics Modernization Program (AMP) allowed you to use QlikView and Qlik Sense side by side under the same licensing model, so there was no financial incentive to migrate those last apps either.

Meanwhile, you are maintaining two technologies, along with the infrastructure and expertise they require. That may be justifiable. But the reasons for leaving those apps in place may no longer exist.

Did you deliberately keep those last QlikView applications, or did they simply never go away?

QlikView’s flexible scripting language lets you retrieve data from all kinds of sources, transform it, and write it back out. A kind of poor man’s integration platform. I have always considered that a questionable use case (I preferred Perl, and later Python, for this kind of glue work), but I understand how it happens.

The problem is that you largely have to handle validation, error handling, logging, and monitoring yourself, so errors can go unnoticed for a long time. And suddenly, the BI team is responsible for keeping business processes running. These days, APIs, dedicated integration tools, or simply Python are usually better choices.

Not everything ever built in QlikView belongs in a BI platform.

QlikView gave developers an enormous amount of freedom. With macros, VBScript, and creative workarounds, some applications have grown into full-blown custom solutions, deeply embedded in business processes.

I wasn’t always a fan of that approach. In 2015, I gave a presentation at Qlik Dev Group NL titled QlikView Macros Are Bad. A little provocative, because macros could certainly be useful. But they were also often used for things that could have been handled better in other ways.

Slide from Barry Harmsen’s 2015 presentation QlikView Macros Are Bad, featuring Fry from Futurama and the text “Macro’s are bad!”.

A migration to Qlik Sense, Qlik Cloud, or Power BI often means redesigning a large part of the solution. That is also a good opportunity to assess whether all that custom functionality is still needed and whether standard functionality is now available for it. Today, integration with business processes can also be implemented differently and more effectively, including within Qlik.

How much of that custom functionality do you actually still need today?

I recently encountered it again: software vendors, such as providers of industry-specific ERP systems, that once chose QlikView as the reporting environment for their software package. Their customers never consciously chose it and sometimes do not even know that their reports run on QlikView.

For the vendor, maintaining the status quo is understandable: a substantial investment has been made, and customers are not asking for anything else. But those customers may want to combine data with other sources, create their own reports, or use new analytics capabilities.

Ask your vendor what their plans are for QlikView.

Beyond functionality and costs, there are three things to consider when making your decision.

Expertise. Even at Bitmetric, where QlikView was at the core of our work for many years, that expertise has become much scarcer. Most colleagues work with Qlik Sense, Qlik Cloud, Power BI, and Microsoft Fabric. At many organizations, QlikView expertise rests with one or two experienced developers. That works fine until they leave. How easy will it then be to find someone who can maintain a complex QlikView environment?

I know this from my own car: the Audi dealer can no longer do much with it, so I take it to a specialist. And even that specialist is finding it increasingly difficult to source parts.

Infrastructure. There are undoubtedly still QlikView environments running on Windows Server 2012 or 2016. Windows Server 2012 is completely out of support, including extended security updates. Support for 2016 ends on January 12, 2027. Recent QlikView versions run well on newer Windows versions, but if you need to renew your infrastructure anyway, that is a logical time to review your BI platform as well.

QlikView itself. Qlik still releases new versions of QlikView: version 12.110 was released in late September 2026. Each release receives approximately two years of support. Support for 12.90 (May 2024) ended on October 31, 2026. So QlikView is not dead, but anyone who wants to stay with it must also continue upgrading. If you are still on an older version, you are already running without support. (See: QlikView Product Lifecycle)

A solution may work perfectly well today while becoming increasingly expensive to keep running.

Unlike oil, drinking water, clean air, or PlayStation 5s when GTA 6 launches, reasons are plentiful. If we ever invent an engine that runs on reasons, the energy problem will be solved.

But having a reason is not the same as having a good reason.

I keep my old Audi because I enjoy it, perhaps against my better judgment. Hobbies are allowed to cost money. For your BI platform, I’d want a better reason.

In QlikView’s heyday, Qlik Sense did not yet exist, and Power BI began as Project Gemini, a collection of Excel add-ins. As a QlikView developer, you did not lose any sleep over that. Since then, Qlik Sense has matured, Power BI has grown into an alternative you should seriously consider, and Microsoft Fabric lets you organize integration, storage, and analytics on a single platform. Users also expect more: self-service, collaboration, mobile access, and, increasingly, the ability to ask questions of their data in natural language.

I completely understand why organizations still use QlikView. Even so, I think there are few truly good reasons in 2026 to continue running it for the next several years.

The exception is when there is a clear end point. Do you know that an application will be retired in two years, for example because your ERP system is being replaced? Then a migration makes little sense. But if you will depend on your BI environment for the next five to ten years, that is a different story.

A migration can be costly and complex. That is a good reason to plan carefully, but not a good reason to postpone the decision indefinitely.

I understand why you still use QlikView. But would you choose it again today?

Want to know where your situation stands? Start with these five questions:

  1. Which version of QlikView are you running, and how long will it be supported? Anything older than 12.100 is now out of support.
  2. How many applications are there, and which ones are actually used? It often turns out that a substantial number are rarely opened anymore. And even the applications that are still used often contain many tabs that no one looks at anymore.
  3. Who can maintain the most important applications if your QlikView specialist leaves tomorrow?
  4. Is QlikView running on a version of Windows Server that is still supported?
  5. Which applications perform tasks that do not really belong in a BI platform? Think of interfaces, exports to other systems, and resource-intensive macros.

Can’t answer one or more of these questions right away? That is an answer in itself.

I’m genuinely curious why your organization is still using QlikView in 2026. Perhaps you recognize your situation in one of the six scenarios, or maybe you have a completely different reason.

At Bitmetric, we work with Qlik Sense, Qlik Cloud, Power BI, and Microsoft Fabric, and still with QlikView. You may find that continuing with QlikView for the time being is perfectly reasonable. It may be time to plan a migration. Or it may make more sense to replace part of your environment.

Barry and Eric from Bitmetric

Discuss your QlikView environment with Barry

Are you still using QlikView? I’d like to hear about your situation and discuss whether it is still the right choice. Ask me a question, call me, or schedule a 30-minute call now.

We reply within one business day

+31 297 445 036

Available on weekdays between 8:00 AM and 6:00 PM (Amsterdam time)

Barry Harmsen, founder of Bitmetric and co-author of QlikView for Developers.

Guide Migration Qlik QlikView

How can we help?

Whether something’s still unclear or you’re ready to take the next step, Barry and Eric are happy to talk it through. Email us, call us, or book a meeting at a time that works for you.