QlikView · Qlik Sense · Qlik Cloud
Leaving Qlik? Take your logic with you, not just your dashboards.
Leaving QlikView or Qlik Sense does not mean working out your business rules again. Unwind Data reads your load scripts, set analysis and QVDs, describes every rule in plain language and translates it into an open semantic layer, so the logic moves to Power BI, Omni or any other platform. A Logic Scan maps every app and script in 5 working days for €4,950.
Starts with a free 30-minute intake call.
What we extract
What we take out of Qlik
Every object that carries logic is read, linked to what depends on it, and checked for use.
Load scripts
The ETL inside Qlik: how data is loaded, joined and transformed.
Set analysis expressions
The filters and comparisons behind your KPIs, often the sharpest business rules.
QVD files
Intermediate files and the chains between them, including what is no longer used.
Master items (dimensions and measures)
The reusable definitions in your apps, compared across apps.
Variables
Values that run through scripts and expressions, such as year and period.
Section access
Who may see which data, so permissions move correctly.
What you get
AI-native migration: more than new dashboards
Your logic leaves the old platform as something you own, can read and can query.
The result is a semantic layer your BI tools and AI agents share. Choosing one? Read dbt Semantic Layer vs Cube and the Open Semantic Interchange guide. How we expose it to AI: MCP-driven data consulting.
Curious what's in your environment? The Logic Scan shows you in 5 working days.
Book a Logic Scan for QlikOptional: Rebuild
Where can your Qlik logic go?
There is no single best destination. It depends on where your definitions should live next. This is what is left of your logic at each one.
Qlik Sense or Qlik Cloud
You stay on the same engine. Load scripts and most set analysis carry over from QlikView; the layouts are rebuilt.
your users like the associative model and you mainly want off QlikView or off on-premises.
Power BI
Set analysis becomes DAX, QVD loads become dataflows or a lakehouse. The associative model gives way to a star schema, so the logic is rewritten, not translated.
your organisation already runs on Microsoft.
OmniA code model with views and joins. The load-script logic moves underneath, into SQL or dbt, and users keep exploring freely.
you want self-service exploration on governed definitions.
dbt Semantic LayerLoad-script transformations become dbt models, set-analysis expressions become metrics with one definition.
your team works in dbt, or you want one definition for every tool.
SigmaA spreadsheet on your warehouse. Models are built mostly in the interface, not in code.
your users explore data themselves and think in spreadsheets. Keep your definitions in dbt, so they don't get locked into one tool again.
Claude or ChatGPT
Claude Dashboards and the Data agent in ChatGPT write a query per chart on your warehouse. They only use your definitions when they can read them from a semantic layer; otherwise each chart works out its own number.
people want answers and quick dashboards in the assistant they already use. Both are new (Claude Dashboards is in beta), so keep a governed tool for reports many people rely on.
Qlik Sense or Qlik Cloud
What is left of your logic: You stay on the same engine. Load scripts and most set analysis carry over from QlikView; the layouts are rebuilt.
Fits when: your users like the associative model and you mainly want off QlikView or off on-premises.
Power BI
What is left of your logic: Set analysis becomes DAX, QVD loads become dataflows or a lakehouse. The associative model gives way to a star schema, so the logic is rewritten, not translated.
Fits when: your organisation already runs on Microsoft.

Omni
What is left of your logic: A code model with views and joins. The load-script logic moves underneath, into SQL or dbt, and users keep exploring freely.
Fits when: you want self-service exploration on governed definitions.

dbt Semantic Layer
What is left of your logic: Load-script transformations become dbt models, set-analysis expressions become metrics with one definition.
Fits when: your team works in dbt, or you want one definition for every tool.

Sigma
What is left of your logic: A spreadsheet on your warehouse. Models are built mostly in the interface, not in code.
Fits when: your users explore data themselves and think in spreadsheets. Keep your definitions in dbt, so they don't get locked into one tool again.
Claude or ChatGPT
What is left of your logic: Claude Dashboards and the Data agent in ChatGPT write a query per chart on your warehouse. They only use your definitions when they can read them from a semantic layer; otherwise each chart works out its own number.
Fits when: people want answers and quick dashboards in the assistant they already use. Both are new (Claude Dashboards is in beta), so keep a governed tool for reports many people rely on.
Whichever you choose, we first capture your definitions in Apache Ossie, an open standard. You pick the destination on facts, and your BI tools and AI agents keep using the same numbers.

Who does the work
One specialist for Qlik
Andreea Urzica, 12 years of experience with Qlik, data strategy and governance. One fixed point of contact who signs off on the reconciliation.
Proof
What it looks like
metrics:
- name: net_revenue
expression: SUM(amount_excl_vat)
filters:
- is_intercompany = false
- is_credit_note = false
owner: finance
source: Revenue.qvsCase
ExampleHealthcare organisation, 600 employees
96 objects (band M) · Logic Scan in 5 working days, Logic Extract in 3 weeks
- Set analysis behind 38 KPIs captured in one semantic layer
- 22 duplicate QVD flows merged
- Rebuilt in Power BI from documented definitions
Start here
Logic Scan for Qlik: €4,950
Inventory, complexity score, risk map and a fixed quote. 5 working days, credited when you commission the next step within 60 days.
Book a Logic ScanStarts with a free 30-minute intake call.
What does a full migration cost? Read how BI migration costs add up.
Frequently asked questions
Other sources
- SQL Server, SSRS, SSISSQL Server 2016 out of support since 14 July 2026.
- SAP BusinessObjectsBO 4.3 and Crystal Reports 2020 are running out.
- MicroStrategyOn-premises support ends on 31 December 2026.
- TableauYour calculated fields are worth more than your licence.
- Power BIMake your DAX readable outside Microsoft.
- LookerLookML is already code. Now free your logic from Looker.
- Excel and AccessThe report that lives in one person's spreadsheet.