Migrating apps

To migrate apps permanently to the cloud, use the recommended migration process of tagging your apps in the QMC of your Qlik Sense Client-Managed deployment. Tagging lets you track the status of your app migration and filter the app list for various exports through the Migration app. After tagging, a few additional steps are required in preparation for the actual migration. For how to migrate, see: Migrating the apps

Selecting and tagging apps for migration

When you tag your applications for migration, they become visible for tracking through the Migration app. Use tags to organize apps according to their readiness for migration and their migration status. Tagging helps you prioritize which apps to migrate first and which might need review or remediation before they are ready to move to Qlik Cloud. If you have not created migration tags in QMC, see Creating and applying tags.

The following application tags are used by the Migration app:

• App - 05 Migrated via Multi-Cloud

• App - 05 URL Link to Qlik Sense Windows

• App - 10 Selected for Migration Review

• App - 20 Migration Remediation Needed

• App - 30 Ready to Migrate

• App - 40 Migration Complete

• App - 99 Will Not Migrate

Apply tags to applications in the QMC.

You can connect a tag to a resource.

Do the following:

1. Open the QMC: https://<QPS server name>/qmc

2. Select a resource type (for example, Apps) on the QMC start page, or from the Start drop-down menu, to display the overview.

   Tip noteYou can filter a column by using the filtering option:

3. Select the items that you want a tag to connect to.

4. Click Edit in the action bar.
5. Ensure Tags is selected in the Properties section.

6. Click the Tags text box to see a list of available tags.

   Information noteIf the tag is not available, you must first create the tag. You can neither create nor delete tags when you are editing a resource. You create tags in the Tags section, which is available on the start page.
7. To filter the list, start typing the tag name.

8. Select a tag.

   The tag will added in blue under the text box.

9. Click Apply at the bottom of the page to save your changes.

   (x) is added to the label of the tag, where x denotes how many of the resources being edited that use the tag.

You have now connected a tag to the resource.

Reviewing the migration status of an app

In the Migration app, use the Data connections sheet to track the status of your apps. Charts show apps for which data connectivity is ready, partially ready, or not ready. You can also use the Migration app with Qlik Lineage Connectors to understand app dependencies.

App limitations

The following table outlines the basic app sizes allowed with Qlik Cloud depending on your subscription.

Determining app size

You can measure app size in two ways:

• Size in memory the last time the app was reloaded

• Size on disk

Use the following tools to determine the size of an app:

• Qlik Sense Enterprise Client-Managed—Use the Meta Data Analyzer app that is included with all Qlik Sense Client-Managed deployments since the September 2019 release. For more information, see Deployment instructions.

• Qlik Cloud—Use the App Analyzer.

Mitigating issues with app size

If you encounter high memory allocation problems due to large app sizes, there are two main approaches that you can take to mitigate the issues.

• Review and update the data load script as applicable:

  • Remove unused fields and rows from being loaded.

  • Drop tables when no longer needed in the data processing.

  • Implement incremental loads to optimize the volume of data being processed.

  • Use optimized QVD loads.

• Add more capacity to the tenant to allow for heavier workloads. See Large app support.

  • Expanded apps

  • Dedicated capacity

Other limitations and considerations

Cloud deployments do not typically allow access to the file system of your host or server, therefore, use these load script modifications when migrating the load script from an on-premises app to Qlik Cloud.

Exporting extensions

If you have only a few extensions, you can manually export them from Qlik Sense Enterprise Client-Managed and import them to Qlik Cloud. With many extensions, consider using the migration script to export extensions to the Extensions folder.

Do the following:

1. Copy your extension zip files into the .\Data\Extensions folder of the migration tools.

2. Run the following migration script: 4_setextensions.ps1. Successful uploads will move the extension to the Complete folder.

Themes

If you have only a few themes, you can manually export them from Qlik Sense Enterprise Client-Managed and import them to Qlik Cloud. With many themes, consider using the migration script to export themes to the Themes folder of the migration tools.

Do the following:

1. Copy your extension zip files into the .\Data\Extensions folder of the migration tools.

2. Run the following migration script: 5_setthemes.ps1. Successful uploads will move the themes to the Complete folder.

GeoAnalytics

App links

App remediation

Migrating the apps

User content

You can manually export the user contents of an application (including community, shared, and personal) from Qlik Sense Client-Managed and import them to Qlik Cloud.

Manually export app user shared contents from Qlik Sense Client-Managed

The first step in moving user contents to Qlik Cloud is to export the contents from Qlik Sense Client-Managed. Once you create a duplicate of the app, and make yourself the owner of the App objects for the original app, you can start copying the App objects from the original app to the duplicate. You must be the owner to of the App object to copy and move them between the original and duplicate app.

Do the following:

1. Open the QMC: https://<QPS server name>/qmc

2. Select Apps on the QMC start page or from the Start drop-down menu to display the overview.

3. Select the app that you want to duplicate, click More actions in the action bar, and then select Duplicate in the pop-up menu.

4. Open the duplicated app and verify that the Public Sheets from the original app are available. Leave your web browser tab open for later use.

5. In the QMC, select App objects.

6. Search for your original app (not the duplicated app), by clicking in the table header.

   Clear any previous search criteria if applicable.

7. Edit the App object (of type sheet) to make yourself the owner. Select the app object that you want to edit, and then click Edit in the action bar.

8. Change the Owner of the App object to you. It is recommended that you change each App object individually instead of changing multiple objects at the same time.

   Information noteAs a best practice, it is recommended that you assign some type of identification as part of the App object's name to indicate who the original owner is and the publish location. This makes it easier to assign the contents back to the original user once the app is in Qlik Cloud. Note that due to the types of spaces in Qlik Cloud (Shared and Managed), you may not be able to completely replicate the location/ownership of the contents in Qlik Cloud as they were in Qlik Sense Client-Managed.

   1. Take note of the original App object owner and the location where the object is expected to be (for example, a personal App object or a published one).

   

   2. Open the original app in the Qlik Sense Hub and select the App object to which you assigned yourself ownership.

   3. If the App object is published or approved content, right-click the object and demote it until it is a personal and editable content

   4. Add a note that will identify the previous owner and publication location. Add the information to the App object title or, if available, on the description field.

   

   5. Right-click the Sheet and select Copy.

   6. Go to the duplicated app that you created in step 3. In the App Overview, right-click next to the Create new sheet button and select Paste.

   7. To revert the sheet in the original app to its original owner and location, go to the original app in Qlik Sense Client-Managed. Clear the description contents that you added and re-publish/approve the sheet to the original location. In the QMC, select the corresponding App object, click Edit and then change the owner to the original user.

   8. Repeat step 5 until all App objects (sheets) are duplicated.

9. In the QMC, click Apps and select the duplicated app that you created in step 3. Click, More actions, and then select Export and store the QVF file. Once the app has successfully exported, you are ready to import it to Qlik Cloud.

Manually import Qlik Sense Client-Managed App User Shared Contents to Qlik Cloud

Start by importing your exported Qlik Sense application to your tenant.

Do the following:

1. In the Qlik Cloud hub click + Add new and select Upload App. Locate the QVF file you previously exported in Qlik Sense Client-Managed and click Upload.

2. Open the recently uploaded app, preferably on a dedicated web browser tab.

   Information noteCurrently, it is assumed that the exported app upload was placed in your Personal space, and the final version (user facing) of the application is already adapted (that is the Data Source Connections) and published in its destination space.

3. If the target app is in a shared space:

   1. Open the target app where the user contents will be imported.

   2. Copy the intended contents from the recently uploaded app to the target app as follows

      • In the App Overview of the recently uploaded app, right-click a Sheet to include in the target app and select Copy.

      • In the App Overview of the target app, under My sheets, right-click the blank space and select Paste.

      • Right-click the sheet and select Make public. This makes sheet you copied available to other users.

      Information noteGiven the nature of the Shared Spaces, the concept of Public Sheet vs. Published by me vs. Community sheets is different and there are only either Published or Personal Sheets. For more information refer to the Developing apps collaboratively in shared spaces section of our documentation.

      • Optionally, request users to duplicate their personal sheets, now available in the Public sheets section. If you documented the sheet owner, either on the Sheet title or Description, when exporting the contents, you might recommend that users look for those contents to help distinguish them from the rest of the available sheets. Once the user identifies the sheet, they can right-click it and select Duplicate .

      • Once the user has duplicated the sheet to their personal area, you can delete the sheet you published. Right-click the sheet and select Make private to bring it to the My sheets area, and then right-click it again and select Delete.

4. If the target App is in a Managed space:

   1. Open the app on which the published app in the Managed Space is based.

   2. Copy the intended contents from the recently uploaded app to the target app as follows:

      • In the App Overview of the recently uploaded app, right-click a Sheet to include in the target app and select Copy.

      • In the App Overview of the target app, under My sheets, right-click the blank space and select Paste.

      • Right-click the sheet and select Make public. This makes sheet you copied available to other users.

5. Once all relevant sheets are copied, go to the Hub and re-publish the app. Click next to the app and select Publish. Make sure you override the correct Published copy when prompted.

6. Request user(s) to duplicate their personal and community sheets, now available in the Public sheets section of the published app in the managed space. If you documented the sheet owner, either on the Sheet title or Description, when exporting the contents, you might recommend that users look for those contents to help distinguish them from the rest of the available sheets. Once the user identifies the sheet, they can right-click it and select Duplicate .

7. If some of the sheets will reside in the Community area of the app, ask the user to publish the sheet(s) by right-clicking the Sheet and selecting Publish.

8. Once the user(s) has duplicated the sheets to their personal area (and published the community ones if applicable), you can delete the sheets you published in step (c). In the app to which you have been adding contents, right-click the correct sheets, select Make private to bring it to the My sheets area, and then right-click the sheet and select Delete.

9. Once all relevant sheets are deleted, go to the Hub and re-publish the app. Click next to the app and select Publish. Make sure you override the correct Published copy when prompted.

Task chaining and reloads

Self-service Reloads and Task Chaining

In Qlik Cloud, some task reloads can be managed by end users within their shared spaces. This can be done:

• In the Hub. See Reloading app data in the cloud hub.

• With Qlik Application Automation task chaining. See Task chaining.

Centrally Managed Reloads and Task Chaining

Centrally managed reloads are the reload tasks that are managed by IT administrators. When migrating to Qlik Cloud, there are three options that can be used depending on the complexity of the tasks.

Option 1 - Qlik Application Automation

Use Qlik Application Automationto reproduce the task chains that were used in your Qlik Sense Client-Managedenvironment. See Task chaining.

Option 2 - Third-party scheduler and qlik-cli

When task chains become very complex, you can use a third-party scheduler and qlik-cli, a Command Line Interface for automating administrative functions using commands and scripts in Qlik Cloud. In the Qlik Cloud migration toolset, you will find a PowerShell script that you can call with a third-party scheduler and reload the sequence of applications. Use reloadqlikcloudapp.ps1 and pass the appid as the parameter.

Third-party scheduler and qlik-qli

See Setting up the Qlik Cloud migration tools to download the toolset.

Option 3 - Qlik Sense Client-ManagedScheduler with External Program Tasks

Use the External program task functionality in Qlik Sense Client-ManagedScheduler to call the PowerShell script reloadqlikcloudapp.ps1 found in the Qlik Cloud migration toolset and pass the appid as the parameter.

Scheduler with External Program Tasks

See Creating and editing external program tasks.

Additional utility scripts

The following scripts are included in the migration toolset.

• ReloadQlikCloudApp.ps1

  • Reloads an app in Qlik Cloud

  • Usage: reloadqlikcloudapp.ps1 -appid <guid>

• UploadQlikCloudDataFile.ps1

  • Uploads a supported file format to a given space

  • Usage: uploadqlikclouddatafile.ps1 <spacename> <filename>

• UploadQlikCloudDataFolder.ps1

  • Uploads a folder and subdirectories of supported files to a given space

  • Usage: uploadqlikclouddatafolder.ps1 <spacename> <foldername>

Tip noteTIP

For all scripts, make sure to set the working directory of the QlikMigrationPlaybook within the .ps1 file