Back up Qlik data connections, streams, tasks and users — not just apps

You version your Qlik Sense apps, so a broken sheet or a bad reload is one rollback away. But an app is only part of the environment. The data connections it reads, the streams it publishes to, the reload tasks that feed it and the user directories behind your access rules all live in the QMC — and if a server has to be rebuilt, none of that comes back with a QVF.

Qlik gives you a clean way to preserve an app — download the QVF or commit it. Data connections, streams, custom properties, security rules, reload task chains and user directory settings have no equivalent button. Teams end up screenshotting QMC pages, pasting connection strings into a wiki, or keeping a spreadsheet of task schedules that goes stale the week after it's written.

Then a server migration, a disaster-recovery drill or a tenant move arrives. The apps restore in minutes; the connections point nowhere, the streams are missing, the tasks are rebuilt one by one from memory, and access rules are reconstructed by trial and error. The recovery that should take an hour takes days, and nobody is certain it matches what was there before.

On Qlik Sense Enterprise, click the Gitoqlok icon on the hub and choose Env Migration. In the Export tab, tick the QMC objects you want — Data Connections, Reload Tasks, Streams, Custom Properties, Security Rules, Tags, Load balancing rules, User Directories and Custom Themes — pick or create a Git repository, and click Export. Each object is written to the repository as its own file, so every backup is a versioned commit you can diff and roll back to. To restore, open the Import tab, select the repository and click Import; the objects are written straight back into the QMC of the target server. On Qlik Cloud, the hub popup's Import Data Connections restores connections stored in a repository into a new tenant. See Environment Migration.