Migrating streams to spaces

Map Streams to Spaces 1:1
Streams that contain 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.
Streams that self-serve apps that are built by users or citizen developers generally become shared spaces. See Working in shared spaces.
My Work moves to Personal - No Space migration is needed
Prune unused Streams
Rename and clean-up where necessary
Establish Dev/Test/Prod naming standards:
- In Qlik Sense Enterprise Client-Managed 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, where access might have been governed using security rules within streams in Qlik Sense Client-Managed.

Do the following:

In the Migration App, go to the Streams and Spaces sheet.
In the table Client Managed Streams for Export, filter the streams you want to migrate 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.

The unit of measurement for Qlik Cloud capacity, usage, and limits is represented by binary gigabytes (GB), where 1 GB is 2³⁰ bytes (1,073,741,824). This is also known as a gibibyte (GiB), defined by the International Electrotechnical Commission (IEC). Similarly, 1 TB is 2⁴⁰ bytes (or 1,024 GBs).

Large app support supports app sizes up to 50 GB (in-memory).

Check the Application SaaS Migration Status sheet in the Migration App to determine those apps.
Enable Large app support on one or more Spaces through the Management Console.

Migrating 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 Qlik Sense Enterprise Client-Managed security rules for reference and the Space Permissions tab in the Migration Worksheet for planning help.

For best practices, see Managing your Analytics lifecycle in Qlik Sense Enterprise SaaS.

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.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!

Leave your feedback here