The September release introduces new capabilities that make migration planning and execution more flexible, efficient, and aligned with dependencies.
Features
Migration Plan: Excel export and import for bulk edits to plans
Export site metadata as empty templates, prefilled from source connections, or based on the current plan. Excel workflows enable iterative bulk editing, external data generation, and advanced transformations not available through the interface. Imports are validated with annotated files for guided corrections, and Excel data can be merged with site metadata and further updated in the tool for maximum flexibility.
Migration Plan: Data Gateway support
Data connections that support a Data Gateway can now be bound to one directly in the plan or through Excel, providing greater control over how source data is accessed in Qlik Cloud.
Projects and jobs: Standard job lists by scope
Selecting Create standard jobs now prompts for the project scope, such as Qlik Sense Enterprise Client-Managed, QlikView, or Qlik NPrinting. Standard jobs are then generated automatically for the chosen scope, reducing setup effort.
Jobs: Job promotion and demotion
Jobs can be promoted or demoted in the list to reorder execution. This is especially useful since new jobs are added at the bottom by default. Reordering helps align jobs in a logical top-to-bottom sequence that reflects dependencies.
Migration Plan: Folder data connection modal update
The folder connection interface has been improved with a clearer design and a rename option. Application scripts now support searching for renamed files to update references.
I had the same issue. The QAMT logs showed this error:
[ERR] An error occurred while reading the key ring. System.Xml.XmlException: Root element is missing.
I fixed it by going into %LOCALAPPDATA%\ASP.NET and deleting the DataProtection-Keys folder. When I restarted the QAMT service the folder was regenerated and the tool opened normally.
