Qlik to Amazon Quick
Qlik to Amazon Quick migration, with the estate mapped before anything moves
A Qlik estate keeps its logic in two places people rarely document: the load scripts and the chart expressions. Data Foundations reads both for every app, traces each dashboard back to the tables and files it really uses, designs the gold layer those dashboards need, and gives your team an Amazon Quick starter pack per app — with a clear line between what was converted and what still needs a person.
Why Qlik estates are hard to move
- The transformation logic lives in load scripts — joins, resident loads, mapping loads, incremental QVD patterns and file loops — not in a warehouse you can query.
- Chart expressions use set analysis, Aggr, dollar-sign expansion and inter-record functions such as Above and RangeSum, which have no one-to-one equivalent in Amazon Quick.
- Section Access security has to be rebuilt as row-level security in the target, not copied.
- Thousands of apps read the same QVD layers and connections, so moving one app at a time without the shared picture creates rework.
- AWS Transform's BI migration, announced in May 2026, covers Power BI and Tableau. Qlik estates need a different route.
What you get
Sheets, objects, measures, dimensions and load-script sources, with each app triaged simple, medium or complex and the reasons listed — plus indicative effort bands to calibrate on a pilot wave.
Connections, SQL tables, QVD layers and loop-loaded files traced to the dashboards that read them. The most-shared sources come first — they set the order of the migration waves.
The dashboards' measures become facts and their grouping fields become conformed dimensions. A physical model with DDL for your warehouse, reviewed in the platform's modelling workbench.
Per app: a dataset skeleton and an analysis definition, visuals mapped from Qlik object types, and calculated fields converted where the translation is mechanical. Set analysis, Aggr and dollar expansion are flagged for review.
Every app with Section Access is flagged, so row-level security is planned from the start rather than discovered at go-live.
Estate summary, full inventory, sources, object mapping and hard expressions in one Excel file.
In our own testing on a synthetic 5,000-app estate, the inventory was parsed in under a minute and the full lineage — over 15,000 nodes — was built in under 30 seconds.
What stays with your people
Accelerate, don't decide. Automated conversion is marked as such, and every item that needs judgement is listed rather than dropped.
- Deciding what set analysis and Aggr expressions should mean in the target model
- Designing row-level security from Section Access
- Replacing extensions and mashups
- Reconciling numbers between Qlik and Amazon Quick, and signing them off
How an engagement starts
- 1Send an export
A zip with one folder per app: the load script and, for Qlik Sense, the output of qlik app unbuild. Scripts and object definitions only — no data rows.
- 2Estate readout
We run it through the platform and walk you through the inventory, lineage, complexity split and the shared sources that set the waves.
- 3Pilot wave
A handful of representative apps end to end — gold model, starter packs, reconciliation — to calibrate effort before committing to the rest.
Questions
What do you need from us to start?+
A zip with one folder per app containing the load script (.qvs or .txt) and, for Qlik Sense, the JSON from qlik app unbuild. No data rows are needed.
Does it work for QlikView as well as Qlik Sense?+
Yes for the load scripts, which carry the sources and transformation logic in both. Qlik Sense unbuild output adds the sheet, object and expression detail.
How large an estate can it handle?+
Up to 10,000 apps and 100 MB per upload, ingested in the background. Larger estates go in batches, and re-uploading updates apps in place rather than duplicating them.
Is the conversion fully automatic?+
No, and it says so. Mechanical translations are converted and marked; anything that needs judgement — set analysis semantics, Section Access, extensions — is listed for a person rather than dropped.
Is this an AWS product?+
No. Data Foundations is built by Data Reply UK, part of the Reply group. It targets Amazon Quick and runs alongside your AWS account rather than inside it.
See it on an estate like yours
Thirty minutes: the inventory, the lineage, the gold model and a starter pack, on a sample estate — then what it would take for yours.