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:

1. Navigate to the Plans tab in the main navigation bar.
2. Click the Create New button on the right side of the interface.
3. Enter a Plan Name in the input field. This will be used to identify the plan in future configurations.

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 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 domain-level mappings when migrating users from Qlik Sense Client-Managed to Qlik Cloud.

You may define multiple directory-to-domain mappings. 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 all migrated user records in the plan.

4. Retrieve objects

After the connections and optional settings are configured, click Retrieve all objects. This initiates API calls to fetch content from the source and target environments, including:

• Users
• Apps
• Streams
• Data connections
• NPrinting reports (if applicable)

5. Object retrieval strategies

There are two methods available for retrieving objects in the plan: Bulk Retrieval and Selective Retrieval.

Bulk Retrieval

• Fetches all 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 (e.g., name sw 'Finance').
• Supports iterative, cumulative selection.

Selective retrieval is preferred in large environments with thousands of assets, as it provides more control and minimizes load on the source system.

6. Object configuration

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

• Qlik Sense Client-Managed View
  Shows metadata from the source environment (e.g., App Name, Stream, 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 clicking the Edit button in each row. Fields such as space name, app name, owner, and others will become editable.

Use the Save button to persist changes or Cancel to revert unsaved edits.

7. 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 helpful descriptions and examples to guide configuration.

8. Create and save the plan

After configuration is complete:

1. Click the Create Plan button to save the initial version of the plan.
2. After initial creation, subsequent changes are saved automatically.

9. Verify creation

Upon successful creation of the plan, a success notification will appear. The plan will be listed in the Plans table for future reference or updates.

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