Planning Your migration
Migrating to Qlik Cloud from Qlik Sense Client-Managed or QlikView represents a strategic evolution in enterprise analytics. This transition is not a lift-and-shift operation—it is a modernization initiative that requires deliberate planning, stakeholder alignment, and architectural foresight.
The Qlik Analytics Migration Tool is purpose-built to execute a defined migration plan. It provides a structured sequence of procedural steps to migrate applications, users, spaces, connections, and related assets. However, the tool does not define the broader migration strategy. It does not determine how assets should be segmented across business units, prioritized by impact, or phased across timelines. Instead, the tool offers a predictable framework for executing the migration after that strategy is in place.
This page outlines the foundational planning work necessary to support a successful transition to Qlik Cloud. With thorough preparation, migration can accelerate innovation, streamline operations, and enhance governance.
1. Establish migration objectives
Clarify business and technical goals to ensure stakeholder alignment. Common migration drivers include:
| Objective | Examples | Value |
|---|---|---|
| Modernization | Adopt Qlik Cloud SaaS capabilities and future-ready architecture | Access innovations like AI, automation, augmented analytics, and native collaboration |
| Operational efficiency | Eliminate infrastructure maintenance and manual updates | Reduce administrative overhead and increase agility |
| Cost optimization | Consolidate licenses, retire legacy systems | Reduce TCO and reinvest savings in analytics development |
| Scalability | Accommodate growing data volumes and user demand | Meet enterprise analytics needs without infrastructure upgrades |
| Governance alignment | Centralize access controls and policies | Enhance data protection and compliance |
| Improved user experience | Deliver responsive, browser-native interfaces | Increase adoption and satisfaction |
Key activities:
- Define measurable success criteria (e.g., app performance, system decommissioning timelines)
- Identify key stakeholders and sponsors
- Document constraints and interdependencies
2. Audit and rationalize existing assets
Before defining what will be migrated, perform a comprehensive inventory of the Qlik environment. This should include:
- Qlik Sense and QlikView applications
- Extensions and themes
- Qlik NPrinting reports
- Data connections and data sources
- Reload tasks and dependencies
- Users, roles, and security rules
Classify each asset:
- To migrate — actively used, high-value, or strategically important
- To redesign — requires adjustment for Qlik Cloud compatibility
- To decommission — no longer in use or redundant
SaaS readiness tools are available through Qlik technical representatives and certified Qlik partners to assist with this process. These are not publicly available and must be requested through authorized channels.
A well-structured audit supports focused migration planning and avoids carrying over unused or outdated content.
3. Define migration scope and structure
Structure the migration effort around clear boundaries to enable testing, iteration, and phased rollout.
Qlik Analytics Migration Tool components:
- Plans — define what is being migrated (apps, users, data, and so on)
- Projects — organize related plans and settings
- Jobs — execute procedural steps defined in a plan
Consider the following planning guidance:
- Segment plans by business unit, region, or asset type
- Limit plan size to simplify testing and rollback
- Prioritize lower-risk content for early validation
- Coordinate timelines based on business impact and dependencies
Qlik Analytics Migration Tool defines the order of execution steps but does not define how to structure migration phases. Strategic planning determines scope, timing, and coordination across teams.
4. Design Qlik Cloud environment structure
Migration success depends on proper alignment with Qlik Cloud architecture. Design the environment in advance to support security, collaboration, and scalability.
Spaces and app lifecycle
- Map Qlik Sense streams to shared or managed spaces
- Create dedicated spaces for data segregation or business domains
- Establish spaces for lifecycle stages: development, validation, production
- Define space ownership, access roles, and promotion workflows
Data Access Strategy
- Review access requirements for all data sources
- Firewalled/on-prem sources may require Qlik Data Gateway - Direct Access
- Data gateways are configured outside of Qlik Analytics Migration Tool
- Gateway use may impact connection names and script logic
Load script paths may need to be updated. Use the Search and Replace Rows feature in migration plans to adjust connections programmatically.
5. Prepare user mapping and security
Align user identities and roles between source environments and Qlik Cloud.
Identity matching
- On-premises systems (for example, Active Directory) differ from cloud IdPs (for example: Azure Entra ID, Okta)
- Users must be matched using email address or subject field
- Matching is required to preserve ownership and access rights
Identity matching considerations are explained in Creating plans.
Access control
- Allocate entitlements appropriately (Professional, Analyzer)
- Map user groups to Qlik Cloud space roles (viewer, contributor, owner)
- Ensure users exist before assigning ownership
- Use Export Users and Import Users to maintain consistency
6. Plan for QlikView conversion
QlikView applications are converted using the QlikView Converter, available in Qlik Sense Desktop and Qlik Sense Client-Managed. Qlik Analytics Migration Tool integrates this converter programmatically via API.
Converted assets include:
- Variables
- Master dimensions and measures
- Master visualizations
QlikView sheets are not recreated in Qlik Sense. While similar in purpose, the platforms differ significantly in design philosophy, layout structure, and user interface. Conversion is a starting point—modernization should reflect Qlik Cloud best practices and user needs. This is an opportunity to rethink content presentation and take advantage of responsive design, dynamic filtering, and modern interaction models.
7. Schedule a development freeze
To maintain consistency during migration:
- Coordinate temporary content freezes to avoid mid-migration changes
- Communicate clearly with development and analytics teams
- Allow time for testing and issue resolution
8. Validate the migration
Use built-in Qlik Analytics Migration Tool capabilities:
- Job Logs for step-by-step visibility
- Validate Applicaations to compare source and target behavior
- Reset App Descriptions and Reset QlikView App Descriptions for cleanup
9. Post-migration governance
Align ongoing operations with Qlik Cloud best practices:
- Use spaces to support DTAP workflows
- Leverage Qlik Cloud's automation and monitoring tools
- Establish and maintain access policies, naming conventions, and ownership documentation
10. Engage Qlik Professional Services
For comprehensive migration support:
- Partner with Qlik Professional Services or certified Qlik partners
- Access SaaS readiness tools and strategy workshops
- Leverage proven frameworks for environment design, execution, and adoption
Contact a Qlik sales representative to explore service options and ensure a smooth migration experience.