# System requirements QV2QS is distributed as a single Windows executable. There is no installer, no runtime dependencies, and no server infrastructure required. ## Supported operating systems * Windows 10, 11, or Windows Server 2019, 2022, 2025 ## Supported browsers The user interface requires a modern browser. The following browsers are supported: * Google Chrome * Microsoft Edge * Mozilla Firefox Internet Explorer is not supported. QV2QS detects the default browser at startup. If the default browser is Internet Explorer, QV2QS opens Chrome, Edge, or Firefox instead. If no supported browser is installed, the console displays download links. If Internet Explorer reaches the user interface directly, a page is displayed prompting the user to install a supported browser. Information note On Windows Server 2019, Internet Explorer is the only browser installed by default. Install Chrome or Edge before running QV2QS in wizard mode. On Windows Server 2022 (fully patched) and Windows Server 2025, Edge is available or can be installed separately. ## Hardware recommendations QV2QS reads QlikView documents through the bundled QlikView Desktop engine and converts the extracted metadata to Qlik Sense format. QV2QS does not load the full QVW file into its own process memory. The bundled QlikView Desktop engine opens the document and extracts the application structure, and QV2QS reads the resulting PRJ folder (small XML and text files). | Resource | Single project | Batch mode | | --- | --- | --- | | CPU | 2 cores minimum | 4 cores recommended | | RAM | 4 GB minimum | 8 GB recommended | | Disk | Free space proportional to the QVW file size for temporary PRJ extraction | Free space for all concurrent PRJ extractions plus output files | In batch mode, each parallel worker processes one project at a time. The default worker count is auto-detected based on CPU cores (cores minus 1). Reduce `--batchWorkers` on machines with limited RAM. ## QlikView document formats QV2QS requires a QlikView document as input — a `.qvw` file or a `.qvf` file created by QlikView 12.70 or later — optionally with a PRJ folder. QV2QS can generate the PRJ folder automatically from the source file. QlikView 12.60 and earlier saves documents as `.qvw`. QlikView 12.70 (May 2022) changed the default save format to `.qvf` for newly created files. Existing `.qvw` files continue to save as `.qvw`. Both file extensions contain a QlikView document and QV2QS supports both. These QlikView-generated `.qvf` files are distinct from the `.qvf` files exported by Qlik Sense — QV2QS accepts only QlikView documents as input. To revert the QlikView default, set `QvDefaultFileFormat=qvw` in `Settings.ini`. A PRJ folder is a set of text files that QlikView creates alongside a document when a folder named `-prj` exists next to the source file. The PRJ folder contains individual files for each sheet, object, variable, load script, macro module, and document property. QV2QS reads these files to extract every detail of the QlikView application without loading the binary document. For a complete description of PRJ folder contents, see [QlikView project files](https://help.qlik.com/en-US/qlikview/September2025/Subsystems/Client/Content/QV_QlikView/QlikView_Project_Files.htm) in the QlikView documentation. ## Network requirements Build to Qlik Cloud and Export QVF modes require outbound HTTPS access to the Qlik Cloud tenant URL. QV2QS does not support HTTP proxy servers at this time. If the network requires a proxy for outbound HTTPS traffic, copy the QVW files to a machine with direct Qlik Cloud access and run QV2QS in Build to Qlik Cloud mode from the connected machine. Alternatively, use Local only mode to generate the conversion report for assessment purposes. For details on Local only limitations, see [How conversion works](https://help.qlik.com/en-US/migration/Content/Qv2qsMigration/getting-started/how-conversion-works.htm#local-only-mode). ## Qlik Cloud requirements Build to Qlik Cloud and Export QVF modes require a Qlik Cloud tenant and an API key. The tenant administrator must enable API key generation and assign the required roles before a user can connect. Two roles are needed: * A custom role with the Manage API keys permission — enables API key generation. * The Private Analytics Content Creator role — enables app creation in the personal space. For the full tenant setup procedure, see [Setting up Qlik Cloud access](https://help.qlik.com/en-US/migration/Content/Qv2qsMigration/getting-started/setting-up-qlik-cloud-access.htm). After the roles are assigned, generate an API key from Profile > API keys in Qlik Cloud. Copy and store the key securely — the key is displayed only once. For authentication setup options, see [Authentication](https://help.qlik.com/en-US/migration/Content/Qv2qsMigration/getting-started/authentication.htm). Information note Both the Build to Qlik Cloud and Export QVF workflows use the Qlik Cloud engine to create and build the app. Only the Local only mode does not require cloud access. For details, see [Wizard steps](https://help.qlik.com/en-US/migration/Content/Qv2qsMigration/user-interface/wizard-steps.htm). ## Learn more * [QlikView Desktop engine](https://help.qlik.com/en-US/migration/Content/Qv2qsMigration/getting-started/qlikview-desktop-engine.htm) * [Setting up Qlik Cloud access](https://help.qlik.com/en-US/migration/Content/Qv2qsMigration/getting-started/setting-up-qlik-cloud-access.htm) * [Quick start](https://help.qlik.com/en-US/migration/Content/Qv2qsMigration/getting-started/quick-start.htm)