Raptor MCP Docs
Migration
QlikView Migration
Use Raptor MCP to inventory, assess, convert, export, and clean up QlikView-to-Qlik Sense work.
Recommended migration flow
Start with inventory and no-data exports. That gives teams a fast, low-risk view of estate complexity before deciding which apps need full reload validation, redesign, or retirement.
- Inventory one or more QlikView folders with qv_inventory_documents.
- Run local assessment and conversion against selected QVW files.
- Use qvf_export_no_data for broad Cloud-ready export passes.
- Reserve full reload/data export for apps that are ready for deeper validation.
- Clean up temporary Cloud apps after export.
Why no-data export first
No-data QVF export is the default migration-factory path because it proves structure, script conversion, metadata, and target-app creation without waiting on every source reload or moving sensitive data unnecessarily.
Previous
Enterprise Gateway
Next