Quick start
Run a first conversion end-to-end using the wizard or the command line.
Prerequisites
- A Windows machine (Windows 10, 11, or Windows Server 2019, 2022, 2025)
- A copy of the QlikView document (
.qvwor QlikView-created.qvffile) in a local working folder. Qlik Sense QVF files are not valid source inputs. Do not point QV2QS at production files on shared drives or QlikView Server mount points. For details, see Source file safety. Alternatively, use one of the bundled example projects. See Example projects. - A Qlik Cloud tenant with API key access enabled (for cloud deployment). For setup instructions, see Setting up Qlik Cloud access.
Using the wizard
Do the following:
- Double-click
QV2QS.exe. On first launch, QV2QS displays a license agreement. Accept the agreement to continue. The wizard opens in the default browser. - On the Setup step, select Build to Qlik Cloud.
- On the Project step, select the QVW file. Leave Auto-generate PRJ enabled (extracts the QVW into a set of XML and text files that QV2QS reads during conversion).
- On the Output step, select an output root folder. QV2QS creates a subfolder named after the QVW file automatically.
- On the Qlik Cloud auth step, enter the tenant URL and API key. The wizard validates the connection.
- On the Qlik Cloud app step, enter an app name. Enable Reload and Auto-binary to populate the app with data.
- On the Review step, verify the configuration summary. The wizard also includes Styling, Advanced, and Conversion report steps with sensible defaults. Adjust these steps as needed before running.
- Click Run. QV2QS generates the PRJ folder, converts the QlikView UI, deploys the app to Qlik Cloud, and generates a conversion report.
After the conversion completes, the executive summary dashboard displays conversion metrics and follow-up items. Open the Qlik Cloud app directly from the summary to review the converted sheets.
Using the command line
The following example generates a PRJ folder from a QVW file, converts the UI, deploys the app to Qlik Cloud with data, and generates an Excel report:
QV2QS.exe --generatePrj --qvw Sales.qvw --outputDir ./output --qsAppName "Sales" --qlikContext my-tenant --autoBinary --reload --reportXlsx
The --autoBinary flag temporarily uploads the QVW file to Qlik Cloud so the converted app can load data via a Binary statement. After the reload completes, QV2QS deletes the uploaded file and restores the original load script in the Cloud app.
QV2QS applies default values for options not specified on the command line. Console output uses rich formatting in dark mode, a conversion report is generated automatically, and the dynamic grid layout is used unless fixed canvas mode is enabled. For the full list of arguments and defaults, see Argument reference.
What to expect
A single-app conversion with cloud deployment and data reload typically completes in two to five minutes end-to-end. The local conversion step (PRJ extraction, XML parsing, and JSON generation) runs in under 30 seconds even for complex applications. Cloud deployment and app building add one to three minutes. Reload time depends entirely on the data volume and data source configuration. For a detailed timing breakdown by pipeline step, see How conversion works.
What is produced
After a successful conversion, the project subfolder (for example, ./output/Sales/) contains the converted app structure, extracted media, a conversion report, and diagnostic logs. For a complete description, see How conversion works.