Managing jobs
In the Qlik Analytics Migration Tool, jobs are the primary execution units responsible for performing specific migration actions. Each job is associated with a project, and every project is linked to a plan. This structure ensures that migration operations are executed within a defined context, based on curated content and configuration rules established in the plan.
Projects define a recommended order of operations for executing jobs. Each job in a project is assigned a priority that determines its relative order. While not strictly enforced, this ordering is designed to respect dependencies — for example, ensuring that spaces or users are created before applications are imported.
Purpose and role in migration
Jobs enable teams to execute well-scoped, repeatable migration steps based on the selected assets and configuration in the associated plan. These steps are modular and can be executed in various combinations depending on the migration strategy.
Each job consists of one or more migration steps, which correspond to specific functional actions — such as exporting applications, creating spaces, migrating sheets, etc. The selected steps are executed sequentially and can be tailored to the needs of a given phase or type of content.
This structure supports incremental, testable migrations rather than a single large-scale operation. Jobs can be run in sequence, repeated with adjusted scope, or iteratively refined for validation and correction. Execution status, logging, and error handling are all centrally managed, helping teams maintain migration integrity throughout the process.
For additional context
Refer to related sections for strategic and operational understanding: