End of Life for QlikView 11: Upgrade or Migrate?

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.

Upgrade or Migrate?

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.  

  • Who are your users and how will they use the tool?  
  • What self-service capabilities are needed?  
  • How are you going to handle data governance?  
  • How much “power” do you want users to have in terms of data analysis and creating their own visualizations?

What’s the Difference? 

Let’s break down the differences between the two platforms:

Qlik Sense

Qlik Sense is a modern, web based application for self-service oriented visual analytics.

1.  Self-service oriented

  • Qlik Sense has UI features that make it easier for users to create and publish their own analyses.
  • With Qlik Sense’s drag-and-drop user interface, it’s very easy to drag new data sets right into a Qlik Sense application or tap into multiple data sources.

2.  Enterprise governance and scalability

  • Qlik Sense offers a Master Library that serves as a governed repository for approved calculations, dimensions, and charts.
  • IT gets value by having a governed logical layer and users get a single version of the truth to minimize questionable data or analyses.

3.  Mobile deployments

  • While mobility is not exclusive to Qlik Sense, Sense’s responsive design allows for a fully optimized experience for users. There’s no difference between the full desktop and mobile experience - a single application can be viewed on any device without additional licensing or development.  

4.  Open APIs and toolkits

  • One of the great things about Qlik Sense is that you can extend it to meet your needs and create custom visualizations and mashups by using APIs and extensions. 

5.  Cloud Ready

  • Start building apps in the cloud on day one.

6.  Subscription Pricing

QlikView

QlikView is a development environment for guided analytics apps and dashboards.

1.  Integrated development environment

  • QlikView puts more control of the user experience in the hands of the Qlik developer without knowledge or understanding of modern web development frameworks.
  • If your UI is complex with significant use of input fields, triggers, conditional visibility, dynamic table headers, or macros, then Qlik Sense may not meet your needs.

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.

Ok, I’ve made my decision, now where do I start?

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.

Tips: Migrating to Qlik Sense

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:

  • It is very important to identify existing features in your Qlikview applications that are not available in Qlik Sense, like input fields, triggers/actions, conditional shows, macros etc. We recommend creating a proof of concept of all the functionalities that can be shown in Qlik Sense using workarounds/extensions. Do not migrate to Qlik Sense without completing a gap analysis of the two products.
  • The responsive design in Qlik Sense means you will have less “real estate” to work with as you develop visualizations. 
  • Qlik Sense does not have the same object layering capabilities as QlikView.
  • Best practices are slightly different between the two products. There are many best practices for Qlik Sense from Qlik users on the Qlik community. 

Tips: Upgrading to QlikView 12

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:

  • In QlikView 12, file functions respect directory functions, making them consistent with the other functions. Unless changes are made, QlikView 11 Script will no longer work in QlikView 12.
  • QlikView 12 removes per qvw control of the script EXECUTE Statement. In QlikView 12 Server, the default is to disallow all EXECUTE statements. Any EXECUTE statement will fail unless you turn on the global setting to allow.
  • Because the upgrade from QlikView 11 to QlikView 12 does an uninstall, you must re-specify your server profile.
  • Qlik does not recommend installing QlikView 11.20 Desktop with QlikView 12 installed. Two versions of the software existing simultaneously on the machine may cause issues.
  • Due to the changes in the QIX engine, there are performance differences between QlikView 11.20 and QlikView 12. During Publisher reloads, some tasks are slower and others faster. If you experience an overall performance degrade, Qlik offers a patch that can be downloaded from the Qlik Support Portal.

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. 

Analytics8's photo
Analytics and big data. It's what we do.

 

Contact Us

National Office Telephone | Mon-Fri 8:30am-5:30pm CT