Creating plans

Plans in the Qlik Analytics Migration Tool define the configuration for selecting and transforming content during migration. Plans determine which objects, such as apps, streams, users, and connections, are included and how they are mapped to the destination environment in Qlik Cloud.

Multiple plans are expected as part of a migration initiative. Each plan typically serves a specific business stream, department, or migration phase, and is later referenced by one or more Projects to execute migration steps.

This page provides instructions for creating a new plan and configuring its settings and content.

1. Create a new plan

Do the following:

• Navigate to the Plans tab in the main navigation bar.
• Click Create New on the right side of the interface.
• Enter a Plan Name in the input field. The plan name is used to identify the plan in future configurations.
• Click Plan Name. The interface returns to the Plans tab.
• Under Actions, click Edits on the newly created plan to begin configuration.

2. Configure Qlik connections

Plans require a source and target connection.

• Source Connection — A Qlik Sense Client-Managed or QlikView environment
• Target Connection — A Qlik Cloud tenant

Use the dropdowns provided to select the appropriate source and target connections for the plan. These must be created ahead of time. See Managing Connections for details.

3. Optional plan settings

Space Settings

Apply a prefix or suffix to all shared spaces included in the plan. This is useful for naming conventions or distinguishing environments.

For example: DEV_ as a shared spaces prefix will result in a space named Finance becoming DEV_Finance by default.

Space name modifiers

You may apply a prefix or suffix to all shared spaces included in the plan. This is useful for naming conventions or distinguishing environments.

For example: 'DEV_\ as a shared spaces prefix will result in a space named Finance becoming DEV_Finance by default.

User Email Mapping

Use User Email Mapping to apply default directory-to-domain mappings when migrating users from Qlik Sense Client-Managed to Qlik Cloud.

Multiple mappings can be defined. For example:

• Qlik Sense Client-Managed Domain: CORP (users appear as CORP\jane)
• Qlik Cloud Domain: corp.com (users should resolve as jane@corp.com)

These mappings are applied automatically across migrated user records in the plan.

4. Choose a method for retrieving or preparing objects

Plan content can be populated in two ways:

• Retrieve objects in the tool
  Bring objects in directly from the source environment by using one of these strategies:
  

  • Bulk retrieval
    Fetches all supported object types in a single process. Suitable for smaller environments where performance impact is minimal. Includes users, apps, streams, and other supported assets.
  • Selective retrieval
    Retrieves a single object type at a time. Allows filtering before retrieval using query logic, for example name sw 'Finance'. Supports iterative, cumulative selection. Preferred in large environments due to greater control and reduced load on the source system.

• Work with Excel
  Export site metadata to Excel for review and adjustment outside the tool, or generate an Excel file from another system. After updates are applied, import the file into the plan.
  Excel import replaces the contents of the selected asset areas with the data on the corresponding sheets. To augment Excel-imported content with additional data from the source system, perform direct retrieval after the import. Iterative workflows are supported; for example, export the current table to Excel, apply further changes, and import again. See Excel export and import for workflow details.

5. Object configuration

After retrieval or import, objects are displayed in dual-view tables:

• Qlik Sense Client-Managed View
  Shows metadata from the source environment, such as app name, stream, and owner.
• Qlik Cloud View
  Shows the configuration as it will appear post-migration in Qlik Cloud.

Objects can be configured by switching to Cloud View and selecting the Edit action in each row. Fields such as space name, app name, owner, and other properties become editable.

To update object metadata for apps, spaces, users, or other items at scale, use the dual-view table in the plan interface or apply changes using Excel export and import for bulk editing, advanced transformations, or updates generated outside the tool.

6. Tooltips and metadata support

For clarification of any field or column in either view, hover over the column header to display a tooltip. Tooltips provide descriptions and examples to guide configuration.

7. Save the plan

When configuration is complete, click Save Migration Plan.

If there are unsaved changes and navigation away from the plan is attempted, a prompt requests confirmation before closing.

The plan is now ready to be linked to a Project and used in one or more Jobs to execute the migration.