QVF export
QV2QS can export the deployed app as a QVF file for offline distribution or import into another Qlik Cloud tenant.
QV2QS exports the deployed app as a QVF file and then deletes the app from Qlik Cloud. This mode still uses the Qlik Cloud engine to build the app, so a tenant and API key are required. The exported QVF can be imported into a different Qlik Cloud tenant.
Importing QV2QS-generated QVF files into Qlik Sense Enterprise Client-Managed is not tested across all versions or officially supported and is discouraged. QV2QS targets the latest Qlik Cloud visualization types, and feature parity with QSECM is not guaranteed. For details, see Qlik Sense Enterprise Client-Managed compatibility.
To enable QVF export, use --exportQvf. To export without data, add --exportQvfNoData. For details, see Argument reference.
QV2QS publishes all converted sheets as base sheets before exporting the QVF. The published status is preserved inside the exported file, so sheets are visible to all users when the QVF is imported into another tenant. To skip publishing, pass --noPublishSheets.
The QVF file is saved to the qvf/ subfolder in the project output folder (for example, <outputDir>/Sales/qvf/) with a timestamped filename. After export, QV2QS deletes the cloud app automatically. A cloud/cloud_app_deleted.txt marker file containing the deleted app ID is written to the project subfolder.