Skip to main content Skip to complementary content

Excel export and import

Excel export and import provides greater flexibility for editing migration plans than in-tool bulk update features. Bulk select and update is available for straightforward changes. For example, exporting and importing with Excel is useful when handling complex updates such as user mappings that go beyond simple domain-to-email substitutions, or transformations that require logic not available directly in the Qlik Analytics Migration Tool.

Process overview

The Excel export and import process is iterative. The standard approach is to export either directly from the source connections or the current assets within the plan, make adjustments in Excel, and import it. Corrections can be applied directly in the annotated file, which can then be re-imported. This cycle of importing, reviewing validation results, correcting in the annotated file, and re-importing can be repeated until the results are satisfactory.

Validation modes control whether imports continue when issues are detected. The default mode, fail on error or warning, stops the import if either errors or warnings are present, ensuring all issues are addressed before continuing. Other modes allow more flexibility by stopping only on errors, skipping invalid rows, or importing all rows regardless of issues.

Other variations are possible, such as combining exports from connections or the current table with further edits in Excel or the tool itself. These approaches can be adapted to different workflows, but the annotated file loop with strict validation is the most common pattern.

Templates used in this process include headers, column descriptions, and dropdowns to ensure data consistency. Templates can be exported empty (including sample data if preferred), populated from existing connections, or based on the current migration plan.

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!