Wizard steps
The user interface is a wizard-style interface for the full conversion process. The wizard opens in the default browser after double-clicking QV2QS.exe or running the executable with the --ui flag. The current version number is displayed in the About dialog. A theme toggle button in the top-right corner switches between light and dark mode. For more information, see Dark mode.
The wizard presents the following steps in order. Steps that do not apply to the selected workflow mode are hidden automatically.
Setup
Select a workflow mode (required). The selected mode determines which subsequent steps are available.
- Build to Qlik Cloud (default) — converts the QlikView UI and deploys the resulting app directly to the Qlik Cloud tenant. Choose this mode to see the converted app in Qlik Cloud immediately. This mode is the recommended workflow for migration.
- Export QVF — converts the QlikView UI using the Qlik Cloud engine, exports the resulting app as a QVF file, then deletes the cloud app. Choose this mode to produce a file for sharing with another team or importing into a different tenant. This mode still requires a Qlik Cloud tenant and API key. Importing into Qlik Sense Enterprise Client-Managed is not tested across all versions or officially supported. For details, see Qlik Sense Enterprise Client-Managed compatibility.
- Local only — performs the conversion on disk without connecting to Qlik Cloud. No Qlik Cloud tenant or API key is required. Local only mode generates the full conversion report and build output for assessment, review, or offline use. The local build output does not include media uploads, background image resolution, alternate state creation, or sheet publishing — these operations require the Deploy phase. For a complete deployment, use Build to Qlik Cloud or Export QVF mode. For details on Local only limitations, see How conversion works. Targeting QSECM with the build output is not tested across all versions or officially supported. For details, see Qlik Sense Enterprise Client-Managed compatibility.
Project
Configure the input source. Do one of the following:
- Single project (default): provide a QVW file (required). Auto-generate PRJ is enabled by default and generates the PRJ folder from the QVW file automatically. Disable this option to provide a PRJ folder or ZIP manually. Click Try example to load a bundled example project without browsing. The button is visible only when the QVW field is empty. See Example projects.
- Batch: provide one or more folders to scan (required). QV2QS discovers all matching QVW and PRJ pairs recursively. Click Try example to populate the folder field with the bundled examples folder. Batch workers controls how many conversions run in parallel (default: auto-detect based on CPU cores). For more information, see Batch conversion.
Always point QV2QS at copies of source documents in a local working folder, not at production files on QlikView Server or shared network drives. The QlikView Desktop engine acquires a file lock during PRJ generation, which can conflict with active QlikView sessions. For details, see Source file safety.
Output
Set the output root folder (required). QV2QS creates a subfolder named after the project inside the output root automatically (for example, <outputDir>/Sales/). If two projects share the same name, a _2, _3 suffix is appended to avoid collisions. Enable Clean logs to delete existing log files before the run.
Qlik Cloud auth
This step appears only in Build to Qlik Cloud and Export QVF modes.
Select or create a qlik-cli context for authenticating with the Qlik Cloud tenant (required). Create a new context by providing the tenant URL and API key. The wizard validates the connection before proceeding.
Qlik Cloud app
This step appears only in Build to Qlik Cloud and Export QVF modes.
| Setting | Description | Default |
|---|---|---|
| App name | Name for the Qlik Sense app in Qlik Cloud | QVW file name, PRJ folder name, or output folder name |
| Reload | Reload the app after building to execute the load script | On |
| Auto-binary | Temporarily upload the QVW file for binary data load, then delete the file after reload. Requires Reload. | On |
| Binary AppId | Use an existing QVW or QVF app in Qlik Cloud for the binary load instead of uploading. Requires Reload. Click the browse button to open the QVW picker. | — |
| Reuse existing app | Update a previously created app instead of creating a new one. When enabled, QV2QS checks the output folder for a previous deployment matching the selected QVW file and populates the app ID automatically. If no previous deployment is found, enter the app ID manually or click the browse button to open the QVF picker. | Off |
| Preserve load script | Keep the existing load script in the target app. The converted script is not applied. Requires Reuse existing app. Turns off Reload by default; re-enable to execute the existing script. | Off |
| Preserve variables | Keep the existing variables in the target app. The converted variables are not applied. Requires Reuse existing app. | Off |
| Skip pre-deploy backup | Do not export a QVF backup before overwriting the app. By default, a no-data backup is saved to cloud/backups/. Requires Reuse existing app. |
Off |
| Publish sheets | Publish all converted sheets as base sheets after building. Base sheets are visible to every user who has access to the app. Disable this setting to keep sheets as personal (unpublished) objects. When Reuse existing app is enabled, the setting applies to new sheets only. Previously published sheets are restored automatically regardless of this setting. | On |
| Build without data | Skip data loading during the build phase. The app is assembled on the tenant with no data, allowing the UI structure to be tested without waiting for a reload. | Off |
| Export without data | Strip data from the exported QVF file. The cloud app may still contain data from the build, but the downloaded QVF is smaller. Export QVF mode only. | Off |
The Binary AppId and Reuse existing app fields include browse buttons that open cloud app picker modals. Each picker loads apps from the connected tenant with search filtering by name, owner, space, or app ID. The QVW picker also provides an app type filter (QVW, QVF, or all). Select an app from the list to populate the field automatically.
Expression adjustments
| Setting | Description | Default |
|---|---|---|
| Fix single-quoted search values | Convert single-quoted wildcards and comparisons to double quotes in set analysis expressions. For more information, see Argument reference. | On |
| Fix unquoted set values (experimental) | Wrap unquoted bare string values in single quotes in set analysis expressions. For more information, see Argument reference. | Off |
Styling
The following settings control sheet appearance and layout behavior.
Theme
| Setting | Description | Default |
|---|---|---|
| App theme | Qlik Sense theme applied to the converted app. The dropdown lists the four built-in Qlik themes. When a Qlik Cloud context is configured, click the refresh button to fetch custom themes installed on the tenant. Sense Classic produces the highest 1:1 fidelity with QlikView. Non-classic themes may alter object borders, background colors, fonts, and padding. The theme sets the default only; users can switch themes at any time in the Qlik Sense client. | Sense Classic |
Backgrounds
| Setting | Description | Default |
|---|---|---|
| Sheet background images | Extract and apply QlikView sheet wallpapers | On |
| Fallback to document background | Use the document-level background for sheets that do not have one | On |
| Background color override | Solid color fill applied to all sheets (#RRGGBB) |
— |
Layout
| Setting | Description | Default |
|---|---|---|
| Show sheet header | Add a header region to converted sheets | Off |
| Skip hidden sheets | Omit sheets with constant-false show conditions | Off |
Listboxes & sorting
| Setting | Description | Default |
|---|---|---|
| Preserve QV listbox colors | Apply original QlikView listbox background colors and transparency | On |
| Date field sort guard | Keep date-like listbox fields (Year, Quarter, Month, and similar) sorted chronologically instead of by selection state. For more information, see Argument reference. | On |
Advanced
| Setting | Description | Default |
|---|---|---|
| Fixed sheet canvas | Enable pixel-accurate QlikView-style positioning. Reveals scale factors, minimum dimensions, and canvas cropping options. Canvas scale and object scale are linked by default; click the chain icon to set independent values. For more information, see Conversion layout settings. | On |
| Auto-extend dynamic sheet | Allow sheets to grow vertically beyond the default grid height | On |
| Media upload workers | Number of parallel workers for uploading media files (wallpapers and images) to Qlik Cloud. Applies to Build to Qlik Cloud and Export QVF modes. | 2
|
| Script replacements | Toggle script replacement processing on or off and manage individual rules. For more information, see Argument reference. | On |
The Script replacements section includes an inline rule editor. Toggle the master switch to enable or disable all script processing. Expand the section to view, add, edit, or delete individual rules. Each rule can be toggled on or off independently. Click Reset to Defaults to restore the eight built-in rules. A summary badge shows the number of enabled rules.
Click the up and down arrow buttons on a rule to change execution order. Rules with a lower execution order run first. Click Export to download all rules as a JSON file. Click Import to load rules from a JSON file, replacing the current set. Imported files must contain a JSON array where each rule has a description, pattern, and search field.
To create a custom rules file for import, click Export first to get the built-in rules in the correct format. Edit the exported file to add, remove, or modify rules, then click Import to load the updated set.
When custom rules or disabled defaults are configured, the command preview displays a notice. The copied command does not include custom rules. Export rules to a JSON file and add --scriptReplacements <path> to the command to include custom rules on the command line.
For an explanation of how rules work, including the two-stage matching process and the built-in rule list, see Argument reference.
Open Mockup Studio from the Advanced step to interactively preview fixed canvas and dynamic grid layouts, adjust scaling, and apply settings back to the wizard.
Conversion report
The following settings control conversion report output.
| Setting | Description | Default |
|---|---|---|
| Generate report | Produce a console conversion report | On |
| Excel report | Export the report as an XLSX file with per-object detail and automation scoring. Enter a filename (e.g. MyReport) or a full path. The .xlsx extension is added automatically. Leave blank to auto-name in reports/. |
On |
| Include selections and search objects | Include the Current Selections box and Search object in the report. These are added automatically by Qlik Sense and excluded by default. | Off |
Review
Confirm all settings before running. The review step displays summary cards for project, workflow, cloud, and output configuration. In batch mode, a table lists all discovered projects.
A required actions checklist in the sidebar tracks items that must be configured before running. Items are grouped by category: workflow, inputs, output, and cloud auth. Each item shows OK when configured or SET when a value is missing. Click an item to navigate directly to the relevant wizard step.
A command preview panel displays the equivalent CLI command for the current wizard configuration. Toggle between PowerShell and Bash syntax. Click Copy to copy the command to the clipboard. The command preview is useful for learning the CLI arguments or saving the exact command for scripted re-runs.
Click Run to start the conversion.
Run
Displays live console output as the conversion executes. Stop a running conversion, follow logs in real time, and open the output folder or Qlik Cloud app when the run completes.