Announcing the General Availability of the Qlik Analytics Migration Tool
Qlik is pleased to announce the general availability of the Qlik Analytics Migration Tool, a strategic solution designed to help customers transition from Qlik Sense Client-Managed to Qlik Cloud with control, visibility, and scalability. This tool also provides foundational support for QlikView and NPrinting migrations, helping reduce manual work and accelerate modernization. The tool originates from an acquisition by Qlik from Stretch Qonnect and has since undergone extensive branding, scaling, and feature expansion. It has been fully hardened in collaboration with the Stretch Qonnect team to meet enterprise standards and real-world complexity. This milestone was announced in the official Qlik press release, which highlights the tool’s role in accelerating customers’ move to cloud analytics: Qlik Press Release
Thank you very much for providing this tool — it's a huge step forward!
I have a couple of questions right away:
During user migration, it seems that users are simply created in the Qlik Cloud tenant. Is there a way to check if the users already exist and send invitations only to those who don’t? Right now, it appears they’re just being added without any verification or invite process.
The migration task list includes predefined jobs for Qlik Sense to Qlik Cloud, which is great. However, what about QlikView? It seems I have to manually define the jobs for QlikView migration. Are there any plans to include predefined templates or automated flows for QlikView as well?
1) The tool will check both the email address and the user subject to see if the user already exists, and if either of those match, it will not migrate the user. The purpose of user migration is to make sure that ownership of assets, including private and community content in apps, is maintained through the migration process. If you require users to receive an invitation (applicable when you are not using a 3rd party IdP) then you would want to send those invitations ahead of time from the cloud tenant itself. In this case, instead of migrating the users with QAMT, you create the mapping in QAMT and turn off the migrate boolean for all users in the user table.
2) The "Standard Jobs" list does not include all possible steps to take and is meant as a starting point. Adding additional standard jobs is currently under consideration.
Hello, I'm attempting to migrate/convert a QV app directly to Qlik Cloud.
1. I noticed when retrieving objects in a plan, the tool never saves the list of QlikView apps available once I've finished adding apps.
For example, if I fetch data using the general "Retrieve all objects" button, I get over 100 QlikView apps available in the dropdown to add. Once I select a few apps and save the plan, the remaining 100 QlikView apps are not available for me to choose again if I want to edit the plan or move onto projects/jobs. The only way for me to see these apps again is if I use the "Retrieve all objects" button once more. Has anyone else experienced this?
2. Under the "Migrate Applications job, my job is failing with this error
Failed to create HttpClient for QlikOnPremiseConnection in project ID b19b4fbc-7d6a-463b-b74c-d41f1e3f0e05: Value cannot be null. (Parameter 'connection')
Again, I'm trying to migrate a QV app from a folder directly to a Qlik Cloud tenant. One thing to note is I get no objects available to select except for QlikView Apps when I "Retrieve All Objects". Those are the only objects available to me, so I'm not sure if there's anything I can do at the tool level.
During our recent migration we were facing a major challenge: many of our applications contained hundreds of private objects. This new migration tool handled this perfectly and turned it into the easiest part of the whole process.
That said, I think there’s room for an important enhancement. It would be incredibly valuable if the tool could also support backing up applications (including all their content and private objects) to an external storage location (for example, SharePoint) and then allow us to easily import them back when needed.
To me, this feels like a natural capability that should already exist in Qlik SaaS, and adding it would be wonderful for both flexibility and peace of mind.
