Automation score
The automation score is the primary quality metric for a QV2QS conversion. The score measures the percentage of in-scope objects that converted automatically without requiring any manual follow-up.
The formula is: auto-converted objects divided by in-scope objects, expressed as a percentage. An automation score of 100% means every object converted without manual intervention.
Two additional scores are included:
- Build coverage — Percentage of in-scope objects that produce an object in the Qlik Sense app (auto-converted + adjustments + placeholders). A build coverage below 100% indicates errors that prevented object creation.
- Readiness score — A weighted score that accounts for the effort required for each outcome category: auto-converted objects count as 1.0, adjustments as 0.7, and placeholders as 0.4. The weights reflect typical post-conversion effort. Adjustments (0.7) require minor manual configuration such as expression tweaks or label changes but retain the original object structure. Placeholders (0.4) require creating or substantially rebuilding the object but still benefit from the layout positioning and sheet context provided by the conversion. The readiness score estimates how close the app is to being production-ready.
Conversion outcomes
Each object receives one of four scored conversion outcomes. Built-in objects (Current Selections, Search) are excluded from scoring and do not appear in the list below. For the full set of five outcome categories, see Conversion outcomes.
- Auto — The object converted fully. No manual work is required.
- Adjustments Required — The object exists in the Qlik Sense app but requires configuration changes after the build. No rebuild is needed.
- Placeholder — The object type or configuration is not supported. A placeholder object is created to preserve the sheet layout.
- Error — An unexpected failure occurred during conversion. No object was created.
Typical score ranges
Automation scores vary depending on the types of objects in the QlikView document. The following ranges are representative for typical QlikView estates.
| Score range | Typical profile |
|---|---|
| 90–100% | Standard dashboards using charts, tables, listboxes, and text objects. Few or no macros or extension objects. |
| 75–89% | Applications with some unsupported objects (bookmark selectors) or button actions that require manual adjustment. |
| 50–74% | Applications with significant use of macros, extension objects, or complex action triggers on non-button objects. |
| Below 50% | Heavily macro-driven or extension-dependent applications. Consider partial rebuild in Qlik Sense rather than post-conversion cleanup. |
Applications that rely primarily on standard QlikView visualizations (charts, tables, filter panes, text objects, and containers) typically score above 85%. The most common drivers of lower scores are QlikView extension objects and objects with unsupported action types.