Why move from QlikView to Qlik Sense?

Qlik Sense was released in 2014 and was positioned as being the next generation of data visualization and discovery. Over the last two and a half years it has matured and is now in the position to be an Enterprise level product and has integrated a number of QlikView's core functionality. Neueda are now being asked regularly by our customers why we should move from QlikView to Qlik Sense. 


Why move from QlikView to Qlik Sense?

1.       Mobile friendly – HTML5 client means that all applications render to your screen size, regardless of the device

2.       Straightforward licence model based on tokens (no server costs)

a.       1 Token gives a user access to all applications

b.       Or 1 token can be divided into 10 hourly sessions which refresh on a monthly basis (ideal for infrequent users)

3.       Provide a greater level of self-service but in a controlled form, nominated super users have the ability to create charts and tables and publish to the main applications

4.       Create great looking visualizations with minimal effort

5.       Ability to integrate with Javascript, D3 libraries and more to create custom visualisations

6.       Smart search functionality means that users can simply search multiple fields in the dataset and see the results

7.       Data connections are all centralised to the Management Console so that connections to databases, folders, websites etc are controlled and reusable


Do I lose all the effort that has gone into my QlikView implementation?

No, 80% of work in QlikView development is around the data model and this is transferable to Qlik Sense with minimal effort. Front end charts need to be recreated however with a number of new features, such as centralised dimensions and measures, centralised data connections and out of the box smart visualisations this is a more efficient process.


This sounds too good to be true!

Whilst there are clearly a number of benefits to moving to Qlik Sense there are a few things to consider:

·         Qlik Sense is more visual and chart orientated rather than being full of tables, so if your QlikView implementation has a significant amount of tables it might be worth analysing whether they are required and if so, designing a tab which is tailored for these

·         Qlik Sense doesn't support as many action objects that QlikView does. Whilst this might be seen as a drawback the lack of objects like this means it is easier to develop, support and use


How do we move from QlikView to Qlik Sense?

Moving from QlikView to Qlik Sense is a good time to reflect on your implementation to date, you should consider questions such as :

·         Is the structure what you envisioned when you originally started your Business Intelligence (B.I.) journey?

·         Is the tool being used appropriately?

The next is to set up the Qlik Sense server and configure the extraction and transformations stages of your ETL process, which are largely reusable from your QlikView implementation.

A further migration task is creating the new Qlik Sense front end for users. This exercise would ideally involve sitting down with a nominated business user (could be a different user per business area if appropriate) and creating the relevant charts and tables using the QlikView application as a basis but also the knowledge of the user. By doing this alongside the business user they will be able to see the process for creating charts (which is click and drag) so that they can understand the effort involved .


Do I need to be trained to use Qlik Sense?

As with all B.I. tools there are generally a number of different user types and this is no different with Qlik Sense. There are essentially 3 different user types for Qlik Sense, each with a different training need:

·         Admin / Developer – This role involves creating the ETL process as well as managing the server (assigning licences, giving users the correct access to applications)

·         Business Super User – For the first time with Qlik there is a specific role for super users who would understand the data and be able to create new charts / tables. These particular users would be able to publish new charts into the existing Qlik Sense application

·         End User – These users essentially consume what is available for them, can use existing charts in the application and export if required


Training needs

·         Admin / Developer – As mentioned previously the scripting architecture of Qlik Sense is largely the same as Qlik Sense so there would be no additional training needed. The main area of training would be for the server configuration which is different than QlikView.

·         Business Super User – Training would be focused on creating charts and then the ability to publish them, due to the ease of creating charts and tables this is fairly intuitive and does not require a significant amount of time

·         End User – Training would revolve around usability of the application, including how to use the Qlik Sense smart search functionality. But like QlikView the best training is for users to explore the application for themselves