Managing projects
Projects in the Qlik Analytics Migration Tool represent a logical grouping of migration jobs that share a common migration context. Each project is bound to a specific migration plan and acts as the execution container for migration steps such as exporting apps, importing users, and publishing content to Qlik Cloud.
Projects allow organizations to structure their migration work in a modular, repeatable manner. Rather than performing a single large migration, it is recommended to define multiple projects aligned to business units, departments, or functional areas. This enables controlled sequencing, testing, and rollback when necessary.
Projects play a central role in the overall migration workflow, and are referenced across multiple phases of migration including creating jobs, monitoring job logs, and associating with specific plans.
Project folder structure
All projects are stored within a consistent directory structure on the local server hosting the Qlik Analytics Migration Tool:
Qlik Analytics Migration Tool\Migration Projects\<PROJECT>
Inside each project folder, the tool creates subfolders and files dynamically based on the migration steps executed by jobs that reference the project. This structure enables:
- Separation of job artifacts across projects
- Simplified management of input and output data
- Traceability of execution history and logs
Examples of project-specific artifacts that may be generated include:
- Exported Qlik Sense or QlikView app files
- JSON files representing user or space mappings
- Migration log outputs
- Undo artifacts for rollback
It is important to avoid modifying or renaming files within the project folders outside of the Qlik Analytics Migration Tool, as this may result in errors during subsequent migration runs.
Next steps
To begin working with projects, see Creating projects.
To remove or update a project, see Deleting projects and Editing projects.
To configure jobs that operate within a project, visit Managing jobs.