Qlik has announced that support for QlikView 11 ends on March 31, 2018. This means that if you are currently using QlikView 11, you should start planning to upgrade to QlikView 12 or migrate to Qlik Sense.
If you’re unsure which route to go, the first thing you should think about is what you are trying to do with your data. There are many reasons to use either product (or both) depending on your use case, so consider your business reasons for using the technology first.
Let’s break down the differences between the two platforms:
Qlik Sense is a modern, web based application for self-service oriented visual analytics.
1. Self-service oriented
2. Enterprise governance and scalability
3. Mobile deployments
4. Open APIs and toolkits
5. Cloud Ready
6. Subscription Pricing
QlikView is a development environment for guided analytics apps and dashboards.
1. Integrated development environment
2. Guided analytics apps and dashboards: QlikView allows for more top-down control of analytics apps, permissions, and data management. Guided analysis paths are customizable and tightly governed.
3. NPrinting: If you’re using the latest version of NPrinting, we have found it works better in QlikView. Note – there is no clean migration path when upgrading to Qlik Sense and the latest version of NPrinting, so you will have to rebuild NPrinting reports.
4. Scripting: It’s important to note that some of the functions, script statements, and prefixes are not supported in Qlik Sense. More details here
Given that the two products are designed for slightly different purposes, they do share a good amount of overlap. Many technological capabilities are common between the products. At their core, both products run on the QIX engine, which supports associative exploration and search within applications. This allows QlikView and Qlik Sense to share data models and load scripts interchangeably. In addition, expressions and expression syntax used in the client are fully compatible between the products.
Regardless if you are migrating or upgrading, either option can become complicated, especially with NPrinting, custom authentication, or anything else custom in the mix (and we have found that most clients do have something custom in their environments). To ensure a smooth transition and accelerate the migration process, we recommend developing a detailed migration strategy and plan. We also suggest starting the process early to ensure there are no bugs. This will give time for Qlik to resolve the bugs or for you to develop workarounds.
You can directly import objects from QlikView applications into Qlik Sense with the QlikView converter, available in Qlik Sense 3.2. When you open a project, converted objects from the original QlikView document are displayed: Visualizations, Dimensions, Measures, and Variables. The tool also identifies parts of the document that could not be converted. More information on using the QlikView Converter
Of course, when migrating to Qlik Sense, it’s not as simple as using the converter and – voila – you are done. You need to keep in mind the differences in functionality and user interfaces between QlikView and Qlik Sense:
Since this is a major release with significant changes to the QIX engine, the first thing you want to do is a full regression test to ensure your apps function as normal. We also encourage you to reload all apps and validate the functionality of macros, extensions, triggers, and connectors (like the REST or web connectors) in the Test environment before moving to Production. Ensure you have a rollback strategy in place.
Preparing for upgrading to QlikView 12:
QlikView 11.20 now has an option to purchase Extended Support (through May 2018) with conditions and an extra cost over and above normal maintenance.
CONTACT US for questions regarding your QlikView end of life strategy.
To thrive with your data, your people, processes, and technology must all be data-focused. This may sound daunting, but we can help you get there. Sign up to meet with one of our analytics experts who will review your data struggles and help map out steps to achieve data-driven decision making.