We decided to move our Qlik apps. How do we prove nothing changed on the way?

lab build · Oct 2026 The family end to end

The team has already chosen its target: a Qlik Sense app moves to Databricks for the data and Power BI for the report. The hard part is not rebuilding the report. It is proving that every number survived. The app, built for this demo on synthetic data, uses the expressions that make these migrations hard: set analysis, TOTAL, Aggr and search sets. First, ade-catalog reads the app. From the load script it shows which files feed which tables. It links each Qlik measure to the tables it reads and the KPI it feeds, with the expression intact, and it stores every measure with its fields and sources. Then ade-ops assesses every object and says why it lands where it does: converted by rule, checked by a person, redesigned, or out. Expressions become DAX that keeps Qlik's semantics, and what has no faithful rule is refused and listed, never guessed. The load script becomes Databricks notebooks, the data lands with the same rows, and the Power BI report is generated from the Qlik sheets. Then comes the proof: every translated measure on every slice, read from the live Qlik engine and from Power BI, side by side. 146 of 154 cases match. The other 8 are one Aggr expression that the two engines evaluate differently. The reason is measured and declared, for the business to decide. Last, ade-lens brings the verdict to the people who use the numbers: the divergence is shown as declared, and an agent beside the migrated report explains a KPI from the model. Here that KPI is "Customers above margin target", 27 of 60, and the agent shows the DAX it ran to check it.

What it does not show

• This is one app built for the demo, not a customer estate.
• What stays human is not converted: alternate states, Section Access to row-level security, selection-dependent logic and text-formatting KPIs are redesign items.
• The parity figures are the results on this app; they have not been re-run independently.
• The ade-lens verdict cards come from the 2026-10-17 run, which covers fewer slices than the 154 cases.
• The lens agent reproduces the measure from the model, because the model does not expose its DAX text. The original Qlik object is not shown next to it.
• The same method runs the other way too: see the Power BI to Qlik round trip. Neither direction is a recommendation of a platform.

Transcript

• 0:00 We decided to move our Qlik apps. How do we prove nothing changed on the way?
• 0:05 The starting point: a Qlik Sense app built for this demo on synthetic data, live in Qlik Cloud
• 0:19 Behind the figures: set analysis, TOTAL, Aggr, search sets
• 0:29 ade-catalog reads the app's load script: which files feed which tables, and the app holding them
• 0:40 ade-catalog links each Qlik measure to the tables it reads and the KPI it feeds, expression intact
• 0:50 One measure as ade-catalog stores it: expression, fields read, sources, where it is shown
• 1:01 Every object gets a tier and the rule that decided it: auto, assisted, redesign, out
• 1:11 Qlik expressions become DAX with Qlik's semantics; no rule means refused, never guessed
• 1:21 The load script becomes Databricks notebooks: the same rows as the Qlik reload
• 1:29 The Power BI report, generated from the Qlik sheets, on the Databricks model
• 1:39 Parity: 146 of 154 cases match the live Qlik engine
• 1:53 The other 8: one Aggr expression the two engines read differently, declared with its reason
• 2:06 ade-lens shows it for what it is: a declared divergence, not a silent mismatch
• 2:14 ade-lens: an agent explains each KPI of the migrated report, from the model
• 2:28 The trail: the DAX it ran, as the user, to reproduce the measure and pin the 35% target
• 2:36 Checked, not claimed.
• 2:36 Every number is compared with the live source engine. What has no rule is listed; what differs is declared. The same method runs the other way too.
• 2:36 ade-catalog · ade-ops · ade-lens · lab builds · AI voice · synthetic data · recorded 2026-10-18

ade-catalog, ade-ops and ade-lens lab builds · AI voice · a Qlik Sense app built for this demo in Qlik Cloud, a Databricks demo workspace, a Power BI demo workspace · synthetic data · recorded 2026-10-18