Migration workflow overview
This page outlines the standard workflow for using the Qlik Analytics Migration Tool to migrate content from Qlik Sense Client-Managed or QlikView to Qlik Cloud.
For an overview of the interface and available tabs in the Qlik Analytics Migration Tool, see Navigating the Qlik Analytics Migration Tool.
This is not a single-step, linear migration process. Migrations are typically iterative and should be planned in phases. Multiple migration plans may be created to reflect different business units, logical groupings, or stages of rollout. Each plan may be linked to one or more projects, and each project may include multiple scoped jobs.
This overview provides a high-level summary of the migration flow. Each step links to a dedicated page with detailed configuration guidance and best practices.
1. Create Qlik connections
Connections must be established between source and target environments to enable content migration.
- Define source connections from Qlik Sense Client-Managed or QlikView
- Define a target connection to Qlik Cloud
- Validate and save all connections
Learn how to create and manage connections
2. Define a migration plan
Migration plans define the content to be migrated and the rules for how it is handled.
- Select the migration type (Qlik Sense or QlikView)
- Apply filters to control object selection
- Configure user and space mappings between environments
Multiple plans can be created to support parallel migrations across lines of business, geographic regions, or deployment stages.
Learn how to create and configure a migration plan
3. Create and link a project to a migration plan
Projects provide the execution context for a migration plan and act as containers for the jobs that carry out the plan's scope. You can create a custom project and optionally enable Create standard jobs to automatically populate it with common migration jobs in a logical order. These jobs are based on the linked plan and can be modified, removed, or supplemented with additional jobs as needed. Projects are typically aligned with a specific migration scope or phase.
Each project requires a linked migration plan:
- Select the appropriate plan within the project settings
- Update existing projects if the linked plan changes
- Linking enables job creation and access to migration steps
Learn how to create and manage projects
4. Create jobs
Jobs perform individual migration steps based on the project's linked plan.
- Create one or more jobs under each project
- Select migration steps (for example: Export Users, Import Apps)
- Assign relevant objects to each job
Jobs are often split by stream, business function, or object type for clarity and repeatability.
Learn how to create and configure jobs
5. Organize jobs by scope
Dividing migrations into smaller, logically scoped jobs improves traceability and control.
- Group jobs by department, line of business, or content category
- Use consistent naming conventions to reflect each job's purpose
Learn how to structure jobs effectively
6. Follow recommended step order
Migration steps may depend on others and are typically executed in a preferred sequence. Although the Qlik Analytics Migration Tool does not enforce ordering, following the recommended flow reduces the risk of errors or missing dependencies.
Typical execution order:
- Create spaces
- Export apps
- Import apps
- Publish apps
- Assign permissions or reload schedules
Review migration step dependencies
7. Run jobs and monitor progress
Jobs can be executed from the Jobs tab in the Qlik Analytics Migration Tool. Logs provide real-time visibility into execution and troubleshooting.
- Start jobs manually through the interface
- Review logs for status, warnings, and errors
Learn how to run and monitor jobs
8. Undo and refine as needed
In cases where a job must be rolled back or adjusted, the Undo Migration function in the Qlik Analytics Migration Tool allows for reversal of specific steps.
- Use undo steps to remove migrated content
- Modify the plan or job and rerun as needed