Migrating to spaces
The QlikView to SaaS Migration App provides various tables from which user, entitlement, space, and application information can be exported and used with the scripts provided in the Qlik Migration Tools.
Spaces overview
Spaces are sections of the Qlik Cloud Analytics hub used to collaboratively develop apps and control access to apps.
-
Personal spaces
Your personal space is your own private work area. You cannot share apps from your personal space and other users cannot collaborate with you.
-
Shared spaces
Shared spaces are used to develop apps collaboratively and share them with other users in the space. A team might have a shared space for the private development and consumption of their own apps.
-
Managed spaces
Managed spaces are used for providing governed access to apps with strict access control both for the app and the app data. In a managed space, only the space owner and target app consumers can open the apps. No other users can open the apps in the managed space unless they have been given permission.
Information noteManaged spaces are not available in Qlik Sense Business or Qlik Cloud Analytics Standard.Apps in managed spaces are developed in personal or shared spaces and published to the managed space.
For more information, see Working in spaces.
Migrating your QlikView content to spaces
-
Define your spaces:
-
Option 1: based on your Apps authorizations in the QlikView to SaaS Migration App (on the Migration Tools tab, under Export Apps).
QlikView to SaaS Migration App, Migration Tools tab, Export Apps
-
Option 2: based on your mounted folders if you defined them by entity, activity, and so on in the QlikView to SaaS Migration App (on the Migration Tools tab, under Export Spaces).
QlikView to SaaS Migration App, Migration Tools tab, Export Spaces
-
-
Apps that are built by developers and governed by a BI or IT organization should generally become managed spaces in Qlik Cloud. See Working in managed spaces.
-
Self-serve apps that are built by users or citizen developers generally become shared spaces. See Working in shared spaces.
-
Personal work done in QlikView Desktop would now move to Personal space
-
Establish Dev/Test/Prod naming standards:
-
In QlikView you have "Sales" in the Dev server, Test server, and Prod server.
-
In Qlik Cloud this becomes DEV_Sales, TEST_Sales, and Sales.
-
For best practices, see Managing your Analytics lifecycle in Qlik Sense Enterprise SaaS and Systems Development Lifecycle (SDLC) with Qlik Cloud - Part 1.
-
-
Use fine grained access control in Qlik Cloud to govern access to individual applications.
Do the following:
-
Define your spaces:
-
Option 1: Create a csv file based on the space definition and save it as spaces.csv.
-
Option 2: Export the content the table Identified Potential Spaces and save it as spaces.csv.
-
-
Run the CLI script 2_setspaces.ps1.
Large app support
Large app support enables you to work with larger apps by giving you access to additional memory. You assign large app capacity to spaces in Qlik Cloud. Data files can be up to 100 GB, but some data types might result in capacity constraints also with smaller files.
Large app support supports app sizes up to 50 GB (in-memory).
-
Check the Qlik Sense scoring tab in the Governance Dashboard, or alternatively the Assess Qlik Cloud section of the Migration Tools tab.
QlikView to SaaS Migration App, Migration Tools tab, Assess Qlik Cloud
-
Enable Large app support on one or more Spaces through the Management Console.
See: Large app support.
Space permissions
To determine the space permissions required in Qlik Cloud, map out your organization by function, project, or business unit. Within those functions, map out roles. Use the spaces.csv file and the Space Permissions tab in the Migration Worksheet for planning help.
Do the following before users log in for the first time if you need to assign space permissions (by users or groups).
-
Manually create spaceuserassignments.csv or spacegroupassignments.csv, or both.
-
Run the CLI script 3_setspaceassignments_users.ps1 or 3_setspaceassignments_groups.ps1, or both.