Conversion scope

QV2QS converts the full QlikView application UI, including charts, tables, listboxes, buttons, text objects, and filter panes. Some QlikView features do not have a direct equivalent in Qlik Sense or require manual configuration after conversion.

Scope boundary

QV2QS is a UI conversion tool. QV2QS does not perform load script modernization, data connection creation, space provisioning, user mapping, or security rule migration. These tasks are handled by the Qlik Analytics Migration Tool (QAMT) as part of the full migration pipeline. For more information, see QV2QS and the Qlik Analytics Migration Tool.

The boundaries listed below reflect the intentional scope of QV2QS. Items outside the UI conversion layer are addressed by QAMT or by manual configuration in Qlik Cloud.

Bookmarks

QlikView developer bookmarks (bookmarks created locally within the document) are not converted. Qlik Sense does not currently support creating bookmarks from JSON build output, so QV2QS cannot include bookmarks in the converted app. Bookmarks must be recreated manually in the Qlik Sense app after deployment.

Load script

QV2QS applies path normalization rules to the load script (backslash to forward slash conversion) and supports custom replacement rules for additional adjustments. When a hidden load script is present in the QVW/QVF binary, QV2QS extracts and prepends it to the visible script in script.qvs. QV2QS does not perform full load script modernization. The following areas require manual attention after conversion:

• Data connections — OLEDB, ODBC, and local file path references are not converted to Qlik Cloud lib:// data connections. Data connections must be created manually in Qlik Cloud.
• Section Access — Qlik Sense supports Section Access but the syntax differs from QlikView (for example, USERID instead of NTNAME). QV2QS does not modify Section Access blocks.
• INCLUDE references — External script file references ($(Include=...)) are not resolved or uploaded. The referenced files must be made available through Qlik Cloud data connections.

For details on the built-in replacement rules and custom rule configuration, see Argument reference.

Macros and triggers

QV2QS detects VBScript macros and trigger actions during the analysis phase but does not convert macros or triggers. Macros (Sub and Function definitions in Module.txt) and document-level triggers (OnOpen, OnPostReload) are listed in the Analysis worksheet of the Excel report. Object-level macro invocations are cross-referenced to identify which objects call which macros.

Qlik Sense does not support VBScript macros. Macro-driven behavior must be recreated using Qlik Sense features such as bookmarks, variables, navigation actions, or Qlik Application Automation.

Placeholder objects

When QV2QS cannot convert an object, QV2QS creates a placeholder text object in the Qlik Sense app. The placeholder preserves the object position on the sheet and displays a message identifying the original QlikView object type. Placeholder objects must be rebuilt manually in Qlik Sense.

For the complete list of conditions that produce a placeholder, see Conversion outcomes. For the list of supported and excluded object types, see Object type mapping.

Features that require manual adjustment

Some QlikView features are converted but require manual configuration after the build. These objects are counted as Adjustments Required in the conversion report and appear in the Objects requiring attention tab of the executive summary.

For the complete list of conditions that produce an Adjustments Required outcome, see Conversion outcomes.

Learn more

• Object type mapping
• Qlik Cloud resource limits
• Object conversion details
• Dimension and measure limits