Migrate Qlik Sense on Windows to SaaS Without PowerShell
Moving an app from Qlik Sense Enterprise on Windows (QSoW) to Qlik Cloud is rarely a single app. You have dozens, and you want the migration to be repeatable rather than a manual export-import marathon. The catch: there is no automation connector for QSoW, so most teams reach for Qlik CLI and PowerShell to push apps from on-prem to the cloud tenant.
The Qlik CLI and PowerShell way
The usual recipe: install qlik-cli, set up two contexts — one for the QSoW endpoint, one for the Cloud tenant — then script the export of each .qvf and the import into a target space. You wire up authentication on both ends (API keys or JWT on the cloud side, certificates or headers on-prem) and loop over the app list in PowerShell.
Gitoqlok brings Git version control, collaboration and change history to Qlik Sense and Power BI — right inside your browser. Try Gitoqlok Free
It works until it doesn't. Data connections don't travel inside the .qvf, so you re-point every lib:// reference by hand afterward. One expired token or one changed space ID breaks the loop mid-run, and you are left guessing which apps actually made it across. And every engineer who runs the migration needs the CLI installed and the contexts configured — the script is only as portable as the environment around it.
How Gitoqlok migrates apps without a script
Gitoqlok turns the migration into a commit on one side and a deploy on the other, straight from the browser. On QSoW, open the app, click the Gitoqlok icon, and on the Local Changes tab click Create Repository, then Save changes. The load script, sheets, master items, variables and bookmarks are committed to your Git repository as JSON — data_load_script/<section>.qvs, objects/sheets/<id>.json and so on. Then open your Qlik Cloud hub, click the Gitoqlok icon, and choose Deploy from Git: pick the repository, branch and commit, give the app a name, and click Deploy. The app lands in the tenant in seconds.
The lib:// references are restored with Import Data Connections in the same hub popup, so data connections resolve on the new tenant without hand-editing. Because every version is a Git commit, you can deploy the same tested commit to several tenants and roll back if a deploy goes wrong — no CLI, no auth contexts, no PowerShell on anyone's machine.