Skip to main content Skip to complementary content

Exporting to Excel

Exporting a migration plan to Excel creates a template for reviewing, editing, and updating plan details outside of the tool. Exported templates provide a structured format with headers, field descriptions, and dropdowns to maintain data consistency.

Export options

Three export template types are available. Each serves a different purpose depending on the workflow.

  • Clean template
    Generates an empty template with headers, with the option to include sample rows. Often used to understand the required format, syntax, and structure of the template. Sample rows illustrate how data can be populated, which is useful when preparing to load plan data from another source system and ensuring it matches the expected input syntax.
  • From connections
    Retrieves metadata from selected source connections and exports it to a template. If no connection is available, no sheets are included. Provides an unfiltered extract of metadata from the source environment, which can then be refined or transformed before import.
  • Current table
    Exports the objects currently visible in the migration plan table to a template. Can be applied to specific tabs such as Apps, Users, Shared spaces, or Managed spaces. Useful for pre-filtering assets in the tool and then adjusting them in Excel. Also valuable in iterative workflows; for a process overview, see Excel export and import — Process overview.

Sheet selection

After selecting the export type, select which Excel sheets to include in the export. Each Excel sheet corresponds to an asset area in the migration plan. This enables partial exports, where only the selected areas are included in the generated file.

Template structure

Exported templates include:

  • Individual sheets corresponding to migration plan tabs (for example, Apps, Users, Shared spaces, Managed spaces)
  • Column header colors indicating data origin or target
  • Header comments describing usage, format, and whether a value is mandatory or optional
  • Dropdown menus with predefined options for fields with fixed values
  • Optional export log providing details on the export operation

How to export a plan to Excel

Do the following:

  1. Open the migration plan in the Qlik Analytics Migration Tool.
  2. Navigate to the tab to export (for example, Apps, Users, Shared spaces, or Managed spaces).
  3. Select Export to Excel.
  4. Choose an export option: Clean template, From connections, or Current table.
  5. (Optional) Select the Excel sheets (asset areas) to include.
  6. (Optional) Include sample rows or export log if required.
  7. Save the generated Excel file.

The exported file can be updated in Excel and re-imported into the migration plan.

Considerations

The following points should be taken into account when exporting:

  • Plan configuration options and From connections
    Plan configuration options such as Space Settings and User Email Mapping are not applied when exporting with From connections. These options do apply to Current table exports, because they are applied to the table content in the tool before export. Exports from connections extract raw metadata without these adjustments.

  • Published apps in Qlik Sense Client-Managed
    When exporting using From connections, apps published in Qlik Sense Client-Managed are set to a shared space named after the stream where the app resides. The Publish flag is set to Off by default. Managed spaces are not created automatically, because managed spaces cannot share the same name as shared spaces. Exported apps should be reviewed to determine which require managed spaces, and appropriate naming conventions should be defined in the Excel file. One-to-one mappings between streams and spaces are uncommon; defaulting shared space names to existing streams provides a consistent basis for replacing them with custom mappings as required.

Related pages

Visit the discussion forum at community.qlik.com

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!