Applications
Last updated: 2026-11-03The Applications section of the Migration Steps includes all operations related to Qlik Sense applications. This excludes QlikView applications, which are handled separately in the QlikView migration steps, and reload tasks, which are handled in the Tasks migration steps.
Sheets travel with their application through the Export Applications and Import Applications steps. There is no separate step for sheets.
Retrieval method in Qlik Cloud
To ensure precise mapping and targeting of applications throughout the migration process, Qlik Analytics Migration Tool employs a consistent identification approach within Qlik Cloud:
- Upon execution of the Import Applications step, each application's description is automatically updated to include a structured JSON object. This object contains both the original Qlik Sense Client-Managed app description and the original Qlik Sense Client-Managed app ID.
- This mechanism enables consistent application tracking across the tenant and ensures that subsequent migration steps — such as reloads, script updates, or publishing — reference the correct application.
Application types and retrieval behavior
- Personal applications:
If an application has no shared space assignment, it is considered personal. These apps are retrieved by locating them within the personal space of the designated Qlik Cloud owner. If the owner does not exist in the tenant, the system searches across all personal spaces for a matching application. - Non-personal (shared or managed) applications:
These are retrieved by matching the app description within the specified space. This ensures accurate differentiation between published and unpublished versions of the same application, as both variants may share identical descriptions.
Behavior during migration
The following behavior applies to application migration steps:
- Community and private sheets are retained when an application is published.
- If a personal app is reassigned to another owner for a reload or a script update, it is handed back to its owner, even when the step fails or is canceled.
- If a large import times out, the Qlik Analytics Migration Tool polls Qlik Cloud and adopts the app that Qlik Cloud is still creating, instead of importing the app a second time.
Note
The retrieval strategy enables reliable execution of all application-related migration steps — such as script updates, reloading, validation, and ownership reassignment — across multiple jobs and plans in complex environments.
Steps in this category
The Add Reload Schedules to Applications (legacy) step is hidden when you build a new job and is kept only so existing jobs keep working. To migrate reload tasks, use the Tasks migration steps.