Docs

Start with discovery and no-data validation. That gives teams a fast, low-risk view of estate complexity before deciding which apps need full reload validation, redesign, retirement, or business-owner review.

• Inventory one or more QlikView source areas under the agreed project scope.
• Assess complexity, data dependencies, reload risk, and ownership before conversion work begins.
• Use no-data exports for broad structure validation before moving sensitive data.
• Reserve full reload/data export for apps that are ready for deeper validation.
• Keep cleanup, acceptance, and exception decisions visible in the migration record.

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.