Move from Qlik Sense

Export your Qlik Sense work with unshackle, then use a coding agent and Querio CLI to rebuild and check it in Querio.

Move a Qlik Cloud app's sheets, master measures and business logic into a Querio analysis your team can inspect and adapt.

Already exported? Go straight to Move exported work to Querio.

1. Prepare access

Install unshackle and run the commands below from your analytics Git repository.

  • QLIK_TENANT_URL and either QLIK_CLIENT_ID/QLIK_CLIENT_SECRET or QLIK_API_KEY.
  • An OAuth machine-to-machine client needs the Trusted consent method and a bot user with access to the app's space.
  • For an app with Section Access, the exporting identity needs access to the app; reading its script requires an ADMIN entry in the access table.

2. Export one report

unshackle check qlik --prompt
unshackle inventory qlik
unshackle migrate qlik --only app:APP_ID
unshackle todo

Replace APP_ID with the selected item's ID from inventory. The credential prompt saves values to a local, git-ignored .env; keep those values out of agent prompts.

Read migration/report.md for missing dependencies, extraction errors and unfinished translations before continuing.

Using exported files instead

You can also import an app folder produced by the Qlik CLI:

qlik app unbuild --app APP_ID --dir exported-app
unshackle init
unshackle import qlik exported-app
unshackle build qlik
unshackle todo

The folder alone may not describe LOAD * columns and associations. Add the app's data metadata response as data-metadata.json beside script.qvs when needed; see the Qlik export guide. Bookmarks and usage are not carried by this file export.

3. Review what needs adapting

  • Resident loads, mapping, script joins and QVD dependencies need warehouse or dbt equivalents.
  • Review Aggr(), TOTAL, alternate states and measures spanning associated tables.
  • Preserve selection behavior and filter defaults. Map Section Access identities explicitly.

Save a chart's data after making a known set of selections in Qlik. Include a cross-table measure and a restricted-access case if those are part of the app. Compare the same selections in Querio.

4. Rebuild and check it in Querio

Open the repository in Claude Code, Codex or your preferred coding agent. Give it this brief:

Read https://docs.querio.ai/llms/guides/move-bi-workflow/already-unshackled.md.
Use this repository's Qlik Sense export to rebuild REPORT_NAME in Querio.
Pay attention to Qlik associations, set analysis, load-script dependencies
and Section Access.
Ask me for the target workspace, datasource and a trusted source result.

Replace REPORT_NAME with the report you chose. Follow Move exported work to Querio for CLI authentication, the full agent task, verification and sharing. Check the rebuilt Querio output against your source result before using it as a replacement.

For export settings and the full list of translation gaps, see unshackle's Qlik Sense guide.

Was this page helpful?

Last updated on October 28, 2026

On this page