Qlik to Power BI Migration Center¶

The definitive resource for migrating from Qlik Sense Enterprise/Cloud to Power BI, Microsoft Fabric, and CSA-in-a-Box.

Who this is for¶

This migration center serves BI leads, analytics engineers, data architects, CDOs, IT directors, and procurement officers who are evaluating or executing a migration from Qlik Sense (Enterprise on Windows, Enterprise SaaS, or Qlik Cloud) to Power BI Service and Microsoft Fabric. Whether you are responding to Thoma Bravo-driven price increases at renewal, consolidating on the Microsoft stack, replacing NPrinting with paginated reports, or pursuing Fabric convergence for zero-copy analytics with Direct Lake, these resources provide the evidence, patterns, and step-by-step guidance to execute confidently.

With over 40,000 Qlik customers worldwide, many of whom face 15-30% annual price increases under PE ownership, BI consolidation to Power BI is one of the most common platform migrations in the analytics market.

Quick-start decision matrix¶

Power BI licensing decision matrix¶

Not all Power BI SKUs are equal. Choosing the right licensing model depends on your user count, feature requirements, and whether Fabric capacity is part of the strategy.

If your organization is deploying CSA-in-a-Box with Fabric capacity F64 or above, all Power BI Premium features are included. This means paginated reports (NPrinting replacement), XMLA endpoints, deployment pipelines, and larger semantic models are available at no additional BI-specific cost. The Fabric capacity covers both data platform and BI workloads.

Strategic resources¶

These documents provide the business case, cost analysis, and strategic framing for decision-makers.

Migration guides¶

Domain-specific deep dives covering every aspect of a Qlik-to-Power BI migration.

Technical references¶

Tutorials¶

Step-by-step, hands-on guides for the most common migration tasks.

Government and federal¶

How CSA-in-a-Box fits¶

CSA-in-a-Box is the data platform layer that makes the Qlik-to-Power BI migration architecturally superior to a simple BI tool swap. Instead of replacing QVD files with Power BI Import extracts (which trades one extract pipeline for another), CSA-in-a-Box provides:

• Medallion architecture (Bronze/Silver/Gold) -- raw ingestion through ADF, transformation through dbt, business-ready tables in the Gold layer
• OneLake / ADLS Gen2 -- Delta Lake tables accessible to Power BI via Direct Lake (zero-copy, always-fresh BI)
• Microsoft Purview -- end-to-end lineage from source system through Bronze/Silver/Gold to Power BI report, with auto-classification of PII/PHI/CUI
• Unity Catalog / Fabric catalog -- governed metadata layer replacing Qlik's per-app data model isolation
• Data contracts (contract.yaml) -- schema, SLA, and ownership enforced at the Gold layer before BI consumption
• Data Mesh support -- domain-owned data products with self-service BI, versus Qlik's centralized per-app model

flowchart LR
    subgraph BEFORE["Qlik Architecture"]
        SRC_Q[Source Systems] --> SCRIPT[Qlik Data Load Script<br/>Per-app ETL]
        SCRIPT --> QVD[QVD Files<br/>Proprietary binary<br/>Data duplicated per app]
        QVD --> APP[Qlik App<br/>Associative model<br/>In-memory]
        APP --> VIZ_Q[Sheets / Visualizations]
    end

    subgraph AFTER["Power BI + CSA-in-a-Box"]
        SRC_P[Source Systems] --> BRONZE[Bronze Layer<br/>Raw ingestion via ADF]
        BRONZE --> SILVER[Silver Layer<br/>dbt models: cleaned]
        SILVER --> GOLD[Gold Layer<br/>Business-ready Delta tables<br/>in OneLake]
        GOLD --> DL[Direct Lake<br/>Zero-copy BI<br/>No extract, always fresh]
        DL --> VIZ_P[Power BI Reports]
    end

Why Direct Lake replaces the QVD pattern¶

The QVD file is the backbone of every Qlik Sense deployment. Every app loads data from source systems (or from intermediate QVDs), transforms it in the data load script, and stores it in a proprietary in-memory format. This means:

• Data is duplicated across every app that uses it
• Reload tasks must run on schedule to keep data fresh
• QVD chains (QVD-to-QVD) create hidden dependencies
• No shared semantic layer -- each app defines its own measures

Direct Lake eliminates all of this. Power BI reads Delta Parquet files directly from OneLake. No data duplication. No scheduled reload. No stale dashboards. The Gold layer in CSA-in-a-Box becomes the single source of truth, and Power BI's shared semantic model replaces per-app measure definitions.

Migration timeline¶

gantt
    title Qlik to Power BI Migration
    dateFormat  YYYY-MM-DD
    axisFormat  %b %d

    section Phase 1 - Discovery
    App and QVD inventory              :p1a, 2026-05-05, 7d
    Expression catalog and complexity  :p1b, after p1a, 7d
    Usage analysis and prioritization  :p1c, after p1a, 7d

    section Phase 2 - Data Layer
    QVD to Gold table mapping          :p2a, after p1c, 7d
    Star schema redesign               :p2b, after p2a, 7d
    Direct Lake semantic models        :p2c, after p2b, 5d

    section Phase 3 - Report Conversion
    Wave 1: Top-20 apps                :p3a, after p2c, 21d
    Wave 2: Medium-priority apps       :p3b, after p3a, 14d
    Wave 3: Remaining apps             :p3c, after p3b, 14d

    section Phase 4 - Server Migration
    Workspace and permissions setup    :p4a, after p2c, 7d
    RLS and refresh schedules          :p4b, after p4a, 7d
    NPrinting to paginated reports     :p4c, after p4b, 10d

    section Phase 5 - Adoption
    Champion training                  :p5a, after p3a, 7d
    General user training              :p5b, after p5a, 14d
    Office hours and feedback          :p5c, after p5b, 21d
    Decommission Qlik                  :p5d, after p5c, 10d

Audience and estimated reading time¶

Cross-references¶

Maintainers: CSA-in-a-Box core team Last updated: 2026-04-30