# Conversion output issues ## Conversion produces placeholder objects Possible cause The source QlikView document contains object types that do not have a direct equivalent in Qlik Sense. These types are converted as placeholder text objects. Proposed action Review the Excel conversion report for objects with a Placeholder outcome. The placeholder contains a description of the original object type and properties. Recreate these objects manually in Qlik Sense using the appropriate visualization type. Information note For details on which object types produce placeholders, see [Conversion scope](https://help.qlik.com/en-US/migration/Content/Qv2qsMigration/known-limitations/conversion-scope.htm). ## Batch conversion reports failures for some projects Possible cause Individual projects within a batch run can fail independently due to PRJ generation errors, conversion errors, or cloud deployment issues. Proposed action Review `batch_summary.json` or the batch summary HTML for per-project results. Each project lists the outcome and any error message. To re-run only the failed projects, copy the failed QVW files to a separate folder and run a new batch against the folder, or run each failed project individually with `--qvw`. Reduce the number of parallel workers with `--batchWorkers 1` if failures appear related to resource contention. Check the per-project log files in each project `logs/` subfolder for detailed error traces. ## Objects appear with unexpected dimensions or measures Possible cause The source QlikView object has more dimensions or measures than the target Qlik Sense visualization type supports. QV2QS moves excess items to the alternatives collection. Proposed action Open the object in the Qlik Sense app editor. The excess dimensions or measures are available in the alternatives panel (the section at the bottom of the data pane labeled Alternative dimensions or Alternative measures). Drag the items back to the active area or select a visualization type that supports the required number of fields. Check the Overflow\_Actions worksheet in the Excel report for details. ## Fonts appear different after conversion Possible cause Qlik Sense supports a limited set of web-safe fonts. QlikView fonts that are not available in Qlik Sense are mapped to the closest available alternative. Proposed action Review the font mappings in the conversion report. Adjust fonts manually in the Qlik Sense app editor if the automatic mapping does not meet the requirements. For details on supported fonts, see [Object conversion details](https://help.qlik.com/en-US/migration/Content/Qv2qsMigration/conversion-reference/object-conversion-details.htm). ## Converted app looks different than expected Possible cause QlikView and Qlik Sense render content differently. Visual differences can result from the layout mode, the applied theme, or expression quoting differences. Proposed action Do one of the following: * If background images do not align with objects, try fixed canvas mode (`--fixedSheetCanvas`). Fixed canvas preserves the original QlikView pixel layout. Verify that canvas scale and object scale are set to the same value. For details, see [Conversion layout modes](https://help.qlik.com/en-US/migration/Content/Qv2qsMigration/conversion-layout-settings/index.htm). * If colors or fonts look different, check whether a non-classic theme is applied. Non-classic themes override object borders, backgrounds, and fonts. Use Sense Classic for the highest fidelity with the original QlikView appearance. * If expressions do not evaluate correctly, review the Expression\_Findings worksheet in the Excel report for set analysis quoting differences between QlikView and Qlik Sense. * Review the Follow-up\_Objects worksheet for objects marked Adjustments Required that may need manual refinement. ## Batch conversion output is missing recent QlikView changes Possible cause In batch mode, `--generatePrj` only generates PRJ folders for QVW files that do not already have a PRJ folder. If a PRJ folder exists from a previous extraction, it is reused even if the QVW file has been updated since. Proposed action Delete the outdated PRJ folder next to the QVW file and re-run the batch conversion with `--generatePrj`. QV2QS generates a fresh PRJ folder when no existing folder is found. Alternatively, open the QVW file in QlikView Desktop and save it — QlikView regenerates the PRJ folder automatically when a `-prj` folder exists in the same directory. In single-project mode, `--generatePrj` always replaces the existing PRJ folder automatically. ## Source file is a Qlik Sense QVF Possible cause The selected file is a QVF exported from Qlik Sense, not a QlikView document. QV2QS accepts only QlikView documents (`.qvw` files or `.qvf` files created by QlikView 12.70 or later) as input. The console or wizard displays `This QVF was created by Qlik Sense, not QlikView. QV2QS converts QlikView documents only.` Proposed action Select a QlikView document instead. QlikView-created QVF files can be identified by opening them in QlikView Desktop. For details on supported input formats, see [System requirements](https://help.qlik.com/en-US/migration/Content/Qv2qsMigration/getting-started/system-requirements.htm). ## Learn more * [Conversion outcomes](https://help.qlik.com/en-US/migration/Content/Qv2qsMigration/conversion-results/conversion-outcomes.htm) * [Object type mapping](https://help.qlik.com/en-US/migration/Content/Qv2qsMigration/object-type-mapping.htm) * [Dimension and measure limits](https://help.qlik.com/en-US/migration/Content/Qv2qsMigration/conversion-reference/dimension-and-measure-limits.htm) * [Batch reporting](https://help.qlik.com/en-US/migration/Content/Qv2qsMigration/batch-conversion/batch-reporting.htm) * [Conversion layout settings](https://help.qlik.com/en-US/migration/Content/Qv2qsMigration/conversion-layout-settings/index.htm)