Product knowledge
Docs
QlikView migration
Inventory QlikView content, assess one representative app and validate conversions before expanding a migration batch.
On this page
Prepare source access and the converter
The QlikView migration tools inventory approved document folders and task metadata, inspect QMS API information and invoke the QV2QS converter. QV2QS is a Windows executable that must be installed and accessible to the Gateway process. Begin with qv2qs_doctor to check the configured executable and version.
Confirm the source folders, output location, file permissions and project scope. Keep source QVWs, original scripts and schedules under the customer's existing retention process. A migration assessment should identify data sources, QVD dependencies, unsupported objects, business ownership and security requirements before target publication.
Choose the conversion mode deliberately
A no-data export helps inspect converted structure without moving the loaded dataset. It does not prove that the app reloads, that calculations match or that user access is correct. Use a successful pilot before authorizing a larger batch or a full-data export.
- local_assessment produces offline assessment and build/report output. It is the tool's default mode.
- qvf_export_no_data creates an app-structure QVF without a data reload. This is useful for early migration batches and still requires the configured Qlik Cloud authentication used by the export flow.
- qvf_export and cloud_deploy use a Cloud build flow with reload and require Qlik Cloud access, reachable data connections and suitable permissions.
- Long-running conversions can return a background job ID. Keep that ID and poll its status rather than starting another conversion while the original is running.
Validate and close each migration
Retire source apps and schedules only through a separate customer-approved cutover. Conversion output and a green job status are intermediate results; business and operational acceptance complete the migration.
- Inventory the agreed source and run a representative local assessment.
- Review the conversion report, unsupported items and proposed target structure.
- Run the approved export or deployment mode and inspect the resulting app.
- Configure target data connections and test reloads, business totals, expressions, selections and security.
- Review representative sheets with the business owner and record accepted differences.
- Preview temporary Cloud-app cleanup, confirm the exact app IDs, then delete only the approved temporary resources.
Previous
Advanced analytics and Python SSE
Next