Create restore points in Qlik before an upgrade — and roll back in one click
Every Qlik Sense upgrade carries the same quiet risk: a platform update, a patch, or a client refresh lands, and a published app that worked yesterday now throws expression errors, renders a broken sheet, or reloads against a changed engine and produces the wrong numbers. Qlik admins want a real restore point before they upgrade — a snapshot they can drop the app back to the moment something breaks, without a scramble.
The manual way: copies and QVF exports
Without version control, the pre-upgrade backup is a manual ritual. You duplicate every important app in the hub, or open the QMC and export each app as a QVF to a network share, dating the folder so you can tell which copy is "before the upgrade." For a tenant with dozens of published apps, that is dozens of exports to babysit.
Then the upgrade breaks something. Now you re-import the QVF, republish it into the right stream, replace the live app, and re-point its data connections and reload tasks — because those don't travel inside the QVF. There is no partial restore: if only the load script regressed, you still swap the entire app and lose any good change made since the copy. And the copy is only as good as the person who remembered to make it.
Gitoqlok brings Git version control, collaboration and change history to Qlik Sense and Power BI — right inside your browser. Try Gitoqlok Free
The Gitoqlok way: commit before you upgrade, Update to roll back
Gitoqlok turns each saved version of a Qlik app into a restore point in Git. Before the upgrade, open the app, click the Gitoqlok icon, and on the Local Changes tab click Save changes — pick the load script, app objects, bookmarks and (on Enterprise) reload tasks and data connections, add a message like "pre-upgrade baseline," and commit. The app is now serialized to your repository: data_load_script/<section>.qvs, one JSON file per sheet under objects/, plus variables, bookmarks and properties.
When the upgrade breaks the app, you don't hunt for a QVF. Reopen Gitoqlok, pick the "pre-upgrade baseline" commit in the commit selector, and click Update — Gitoqlok reads that version back from Git and applies it to the live app. The arrow next to Update lets you restore only the affected parts (just the script, just the objects, just the automations). For a clean tenant-level recovery, Deploy from Git rebuilds the app from any commit, and Environment Migration restores the QMC objects — tasks, streams, security rules — that a QVF leaves behind. See Update and Roll Back.
TIP
Before any planned upgrade, make one commit per critical app with a dated "pre-upgrade baseline" message. Because branches and commits are never deleted, that restore point stays available long after the upgrade is done.