Unpack Qlik. Line by line.

A lot of the business logic in a Qlik estate lives in load scripts, so it’s hidden from anyone who only looks at the sheets. A migration that starts from the screens misses it. We start from the scripts.

What we read

• Load scripts — LOAD and SQL SELECT statements, joins, mapping tables, ApplyMap and incremental-load logic.
• QVDs — what each file contains, what produces it and what consumes it.
• Data models — associations, synthetic keys and link tables.
• Master items — dimensions and measures, including set analysis and Aggr().
• Variables — including expressions expanded with $(...).
• Sheets and objects — charts, filter panes and bookmarks.
• Section Access — who can see which rows.
• Usage — which apps and documents are still opened.

Both Qlik Sense apps and QlikView documents are supported.

How it translates

Where the care goes

• Associative behaviour. Qlik’s green, white and grey selection states have no direct equivalent elsewhere. We model the questions people actually ask with them.
• Synthetic keys and link tables. These are reshaped into a star schema with clear grain.
• Complex set analysis. Modifiers such as P(), E() and nested sets are translated into explicit filter logic and parity-tested.
• Alternate states. Comparison analyses are rebuilt with the target’s own patterns.