Executive summary dashboard
After a conversion completes, QV2QS displays an interactive executive summary dashboard. The dashboard provides conversion metrics, identifies items that require follow-up, and breaks down results by object type. The same dashboard is available in the user interface and as two exportable files. QV2QS generates a self-contained HTML file (reports/executive_summary.html) and a machine-readable JSON file (reports/executive_summary.json).
In single-project mode, the dashboard displays one panel with all conversion details. In batch mode, an Overview tab aggregates metrics across all projects, and individual project tabs provide per-project detail. For more information on batch reporting, see Batch reporting.
Dashboard header
The header displays the project name, the generation timestamp, and the total run time. For cloud deployments, the total run time measures the complete pipeline from start to finish (conversion, media upload, app build, and reload). For local-only runs, the total run time equals the conversion duration.
KPI cards
Eight key performance indicator cards appear at the top of the dashboard. Each card is clickable and navigates to the corresponding detail section.
The following table describes each KPI card.
| KPI card | Value | Category |
|---|---|---|
| In-scope objects | Count of QlikView objects eligible for conversion. Built-in objects (Current Selections, Search) are excluded. | Informational |
| Auto-converted | Objects converted to Qlik Sense format with no manual follow-up required. Displayed as a count and a percentage of in-scope objects. | Informational |
| Skipped | Built-in or out-of-scope objects excluded from conversion scoring. | Informational |
| Errors | Objects that failed during conversion and require manual remediation. | Action required |
| Placeholders | Objects created as empty placeholders because no direct Qlik Sense equivalent exists. These objects must be rebuilt manually. | Action required |
| Adjustments | Objects that were partially converted but may need manual review or property corrections. | Action required |
| Sheets | Number of QlikView sheets discovered and converted. | Informational |
| Other findings | Additional QlikView features and patterns detected during analysis. The primary number shows items that need manual review. The subtitle provides a breakdown including review count, auto-fixed count, and total. The card is amber when items still require review, or green when all expression findings were auto-fixed. | Action required |
Triage cards
Two summary cards appear below the KPI row to separate automated outcomes from items that need attention.
- Handled automatically — Displays the count of auto-converted objects, the count of dimension or measure overflow adjustments that QV2QS resolved without manual intervention, auto-fixed expression findings, and unused VBScript macros (macros defined in Module.txt but never invoked from any object).
- Action required — Lists each category of follow-up work with a count and a link to the detail section. Categories include placeholders, adjustments, errors, developer bookmarks, macro invocations, compatibility findings, and expression findings that need manual attention. Only macros with traced invocations appear here; unused macros are shown in Handled automatically instead. Only categories with items greater than zero are shown.
Detail tabs
Six detail tabs organize the conversion results. Each tab focuses on a specific aspect of the conversion.
Overview
The Overview tab contains the following cards.
- Inventory — Key counts from the source QlikView application: sheets, variables, groups, unique images, referenced image files, and overflow adjustments handled (if any). The inventory also displays data model field count, table count, and total data size in megabytes.
- Conversion health — A table showing the breakdown of in-scope objects into Auto, Follow-up, and Skipped categories. Each row displays the count, percentage of in-scope objects, percentage of total objects, and contextual notes. This card provides the primary measure of conversion completeness.
- Follow-up scope — A horizontal bar chart showing the distribution of follow-up work across Adjustments, Placeholders, and Errors. Each bar is clickable and navigates to the relevant detail section. A table view is also available with counts and percentages.
- Objects by project (batch mode only) — A stacked horizontal bar chart showing Auto, Follow-up, and Skipped counts for each project. Each row is clickable and navigates to the individual project tab. A table view shows per-project columns: In-scope, Auto, Auto %, Follow-up, Errors, Skipped, and Total.
Object types
The Object types tab contains two cards.
- Outcomes by QlikView object type — A segmented bar chart showing how each QlikView object type was converted. Each bar is divided into Auto, Adjustments, Placeholder, Error, and Skipped segments. The top 10 types are shown by default. Click Show all to display every type. A table view provides the same data with numeric columns for each outcome category.
- Converted Qlik Sense visualization types — A horizontal bar chart showing the distribution of generated Qlik Sense visualization types. Each bar displays the count and percentage share. This card provides a quick view of which Qlik Sense types dominate the converted app.
Objects requiring attention
The Objects requiring attention tab contains sub-tabs for each category of follow-up work. Only categories with items greater than zero appear. Each sub-tab badge is orange to indicate that items require manual action.
- Placeholders — Objects that need to be built from scratch in Qlik Sense. A chart view aggregates placeholder counts by QlikView type. A table view lists each object individually with columns: Sheet, Object ID, Object (title), Type, and Reason. In batch mode, an App column is added.
- Adjustments — Objects that were converted but need manual review. The chart and table layouts match the Placeholders sub-tab.
- Bookmarks — Developer-created bookmarks from the QlikView document that must be manually recreated in Qlik Sense. The table lists each bookmark with columns: ID, Name, Fields, Field Names, Scope, Layout Objects, Layout State, and Selections.
- Macros — VBScript macro definitions and invocations detected in the QlikView document. Three tables are displayed. The first lists macro definitions with columns: Name, Type, Lines, Objects, Sheets, Invoked From, and Status. The second lists macro invocations with columns: Macro Name, Source Object, Sheet, and Trigger. The third cross-references macros invoked but not defined in
Module.txt.
Chart adjustments
The Chart adjustments tab displays objects where QV2QS automatically adjusted dimensions, measures, or trellis grid settings to fit Qlik Sense visualization limits. The table lists each affected object with columns: Object ID, Viz Type, Original (dimension and measure counts), Reason, and What was done. In batch mode, an App column is added. The Reason column explains why the adjustment was necessary (for example, too many dimensions, an incompatible combination, or a trellis grid smaller than the number of distinct dimension values). The What was done column describes the action taken (for example, moved extra dimensions to alternatives, truncated to fit limits, or expanded the trellis grid to show all dimension values).
Other findings
The Other findings tab contains two sub-tabs: Compatibility and Expression. Only sub-tabs with items greater than zero appear. When only one sub-tab has items, the sub-tab bar is hidden and the content is displayed directly. The tab badge and sub-tab badges use dual colors: an orange count for items needing manual review and a gray count for auto-fixed items. The Compatibility sub-tab badge is always orange because all compatibility findings require manual action. The Expression sub-tab badge shows an orange count for items needing review and a gray count for auto-fixed items when both are present.
The Compatibility sub-tab displays additional QlikView features and patterns detected during analysis. Some findings are informational, such as binary load statements or INCLUDE references. Others identify features that work differently in Qlik Cloud or require manual configuration. The table lists each finding with columns: Source, Finding, Description, Confidence, and Details. In batch mode, an App column is added. Confidence values are color-coded: High (green), Medium (amber), and Low (red). For more information, see Analysis.
The Expression sub-tab displays set analysis quoting findings, unsupported function calls, bare field references, and bare unbraced values. A legend above the table explains the three status badges. Auto-fixed (green) indicates corrections applied during conversion. Review (amber) indicates items requiring manual attention. No fix (red) indicates items that must be rewritten manually. Unsupported functions, bare field references, and bare unbraced values receive the No fix status because QV2QS cannot automatically correct these patterns. Findings where no automatic fix is available highlight the problematic text in red within the Expression column. A filter toggle provides three views: All (every finding), Auto-fixed (only corrected items), and Needs attention (only items requiring manual action). The table is sorted with auto-fixed items first, then grouped by issue type. The table lists each finding with columns: Source, Object ID, Type, Sheet(s), Field, Set Field, Matched Text, Impact, Status, Rule, Description, Applied Fix, and Expression. In batch mode, an App column is added. The Source column indicates whether the finding originates from a variable definition or a chart object expression. The Status column indicates whether QV2QS corrected the expression automatically. The Applied Fix column shows the corrected expression that was applied during conversion. The Expression column displays a compact single-line view with comments stripped; the copy button preserves the original formatting including newlines, indentation, and comments. When a finding has multiple occurrences of the same matched text, the Matched Text column shows the value with a count (for example, GetCurrentField() (×4)). The value is not repeated. Description values that contain URLs are rendered as clickable links. For more information, see Analysis.
App info
The App info tab displays metadata about the source QlikView application and timing metrics. The tab contains four sub-tabs:
- App metadata — Source directory, QVW file path, PRJ folder path, project output folder, base RAM in MB and GB (if available), last reload time, and timing metrics.
- Fields — Data model fields with cardinality, byte sizes, and tags.
- Tables — Data model tables with row counts, field counts, and byte sizes.
- Data lineage — Data connection types detected in the load script.
Timing metrics (within the App metadata sub-tab):
- Conversion duration — Time spent parsing the QlikView PRJ and generating the Qlik Sense build folder. This measures the local conversion phase only and does not include cloud deployment.
- App build time — Time spent on the
qlik app buildoperation in Qlik Cloud. The label indicates whether the build included a reload. This field appears only when cloud deployment was performed. - Total run time — Wall-clock time from start to finish, including authentication, local conversion, cloud deployment, media upload, and reload. This field appears only when cloud deployment was performed. For local-only runs (
--unbuildOnly), total run time equals the conversion duration.
Batch project tabs
In batch mode, the executive summary adds one tab for each project in the batch. Each project tab provides a self-contained summary of that project.
Each project tab contains the following sections.
- Header — Project name, sheet count, in-scope object count, and auto-conversion percentage. An Open app button links to the Qlik Cloud app when available.
- KPI cards — Four cards: In-scope, Auto-converted, Follow-up, and Errors.
- Outcomes by QV type — A segmented bar chart showing the top 10 QlikView object types and their conversion outcomes for the project.
- Qlik Sense types — A horizontal bar chart showing the top 8 generated Qlik Sense visualization types for the project.
- Placeholders (if any) — A table listing placeholder objects with columns: Sheet, Object ID, Object, Type, and Reason.
- Adjustments (if any) — A table listing adjustment objects with the same column layout.
- Project metadata — Project path, output path, conversion duration, app build time (with reload flag), and total run time. App build time and total run time appear only when cloud deployment was performed.
Standalone HTML export
QV2QS generates a self-contained HTML file (reports/executive_summary.html) alongside the JSON file. The HTML export reproduces the full interactive dashboard with all CSS and JavaScript embedded inline. The file has no external dependencies and can be opened in any modern browser, shared via email, or archived alongside the conversion output.
The standalone HTML file inherits the active color theme (light or dark) from the user interface when generated via Open in new tab. A theme toggle button appears in the dashboard header to switch modes independently. The selected theme is embedded directly in the HTML file, so saved or shared files display the correct theme without requiring the QV2QS server.
In batch mode, the aggregate file is saved as batch_summary.html in the batch output root directory. Each individual project also receives a per-project executive_summary.html in the project reports/ subfolder.