You will be redirected to:
Qlik Sense SaaS isn't simply the "cloud" equivalent of the "on-premise" version of the famous data visualization platform. To successfully migrate to this version, companies need to audit their existing Qlik environments and support business users in discovering and adopting the SaaS version.
Qlik is among the most widely deployed data visualization platforms worldwide. Across all sectors, businesses rely on Qlik to simplify data access and facilitate operational decision-making through graphical representations highlighting key information. In a context of widespread digital transition, it's no surprise that Qlik actively promotes the SaaS version of its platform. While it offers undeniable advantages and advancements, companies currently using an on-premise deployment of Qlik Sense must ensure that transitioning to the cloud doesn't result in detrimental regressions, both in terms of governance and for end users.
The first striking difference lies in the user interface of Qlik Sense SaaS, which allows each user to customize their homepage by subscribing to the applications, indicators, and charts they typically use. Unlike the on-premise version, the SaaS version also enables the creation of shared spaces that encourage collaboration and the pooling of Qlik work and applications within a team, business unit, or ad hoc groups.
What might unsettle end users accustomed to the stability of on-premise versions is the frequency of updates (UPDs) in the SaaS version. In a continuous improvement logic of its platform, Qlik releases UPDs on average every 5 days, introducing new features that users discover upon logging in. While automatic updates save considerable time for technicians and administrators, they also relinquish control over communication to users. It's impossible for them to test new features before they're made available to everyone and, consequently, to support users in a targeted manner in adopting those relevant to them.
While the automation of updates ensures working continuously on the latest platform version, certain limitations should catch the attention of technical teams and administrators considering migrating to the SaaS version. In particular:
Reduced governance and management capabilities: The SaaS version offers less flexibility than the on-premise version in defining access and assigning roles to users (read, contribute, create/manage spaces). This means that the existing governance framework in the on-premise environment cannot be replicated in the SaaS version.
5 GB memory limitation per Qlik application: Applications consuming more than 5 GB are not supported. This limit can be offset by purchasing additional capacity.
Data exports limited to 100 MB: Files exceeding this size cannot be exported; they need to be split or the logic of the application requiring export needs to be reviewed.
The aforementioned limitations justify conducting a thorough audit of the on-premise Qlik Sense environment to validate the relevance of transitioning to the SaaS version. This audit ensures, first and foremost, that all existing developments, customizations, applications, dashboards, and charts are compatible with the SaaS version and that users will not experience any alteration or regression in their platform usage. Examining each element of the existing setup allows for the identification of critical Qlik applications for different user categories and their compliance with the rules and limits imposed by the SaaS version. It's imperative to conduct this review with the relevant business teams, which helps exclude obsolete/unused applications from the migration scope and focus efforts on applications requiring adaptation, redesign, or the search for an alternative to be operational in the SaaS version. This means:
Important but memory-intensive applications may need to be redesigned, applying best practices to stay within the 5 GB limit if necessary.
Access rights and role management rules will need to be adjusted. For example, unlike in the on-premise version, it's not possible to assign different rights to users within the same shared space. Members of a shared space have the same rights to all objects and applications within that space. Therefore, it's necessary to rethink the previous organization, typically by creating multiple spaces for the same business unit.
Graphical elements based on third-party modules need special attention since the SaaS version does not support all extensions that work in the on-premise version.
By understanding the work required by technical teams to limit regressions detrimental to users, this audit also verifies that the expected savings from the SaaS version will not be diminished or nullified by adaptation expenses or the purchase of additional memory to retain overly heavy applications. Weighing the expected savings against the costs involved may lead a company to reconsider its project to move to the SaaS version. In this case, the audit will have facilitated a reevaluation and beneficial cleanup, contributing to a more rational use of the on-premise version. Regardless, by approaching the transition to the SaaS version as a migration to a new tool rather than a simple version upgrade, the company maximizes the chances of success. Building on the results of the thorough audit of the existing setup, it can construct a rigorous migration plan covering Qlik development, testing, and production environments and involving different user categories. The older, richer, and more complex the existing environments, the more demanding the migration will be, with each retained Qlik application/element requiring regression testing by technicians and with business users.
Beyond the technical aspects, which we've emphasized the importance of, and the financial implications, the migration to the SaaS version of Qlik Sense should be seen as an opportunity to strengthen the company's data culture by elevating the level of data literacy among its employees. Implementing a general training program on the fundamentals of data is the best way to ensure that everyone within the company understands data, knows how to use it, and, most importantly, can extract the information that enriches their work and enhances the relevance of their operational decisions. The power of Qlik, the richness of its visualizations, and the increased collaboration opportunities offered by the SaaS version will create even more value for the company and its users when they have been trained and actively involved in this new stage of digital transformation. The shift to the cloud is just one dimension of this transformation. While it is inevitable in the short or long term for all business applications, it's the ability of all members of the company to use data in a relevant and creative manner that will make the difference in terms of operational efficiency and economic performance of the enterprise.