Qlik's support for QlikView 12.90 ends on 31 October 2026. The latest release, QlikView 12.100, is supported until 30 September 2027. Nothing stops working on the day, but once a release is out of support, getting help starts with a request to upgrade. Every QlikView estate now has a horizon, and the documents on it need a plan.

The dates that matter

  • QlikView 12.80: support ended on 31 October 2025.
  • QlikView 12.90 (May 2024): support ends on 31 October 2026.
  • QlikView 12.100 (September 2025): support ends on 30 September 2027.

Your options

  • Upgrade to QlikView 12.100. The quickest way back into support, and it buys time until September 2027. It does not buy a destination.
  • Move to Qlik Sense or Qlik Cloud. Load scripts and QVD files largely carry over, but QlikView documents do not open in Qlik Sense, so sheets and charts are rebuilt.
  • Move to Power BI or another platform. Common where the business already runs on Microsoft 365. The logic in the load scripts has to be rebuilt, not copied.
  • Retire what nobody uses. Often the biggest saving: every document you switch off is one you never rebuild or test.

What a QlikView estate hides

Many businesses have run QlikView for well over a decade. Estates built over that long carry far more than the document list suggests.

  • QVD files that feed other documents, so one load script quietly sits underneath dozens of dashboards.
  • Publisher tasks that reload and send documents on a schedule, sometimes to people outside the business.
  • Business logic in load scripts and chart expressions, including hard-coded rates and mapping tables.
  • Section Access rules that decide who sees what, which have to be rebuilt in whatever comes next.
  • The same KPI calculated differently in different documents, often by people who have since left.

What to settle before you choose

  • Which documents are actually opened, and by whom. QlikView Server session logs show it; ask for the last twelve months.
  • Which QVDs and scripts feed what, so sources move before the dashboards that depend on them.
  • Who owns each important document and will sign off its replacement.
  • Which KPIs are calculated more than once, and which definition the business agrees.
  • How you will prove the new reports match the old ones before anything is switched off.

Whatever the destination, these answers decide the size of the job. A plan that starts with them is scoped on evidence. A plan that starts with a platform choice tends to discover the estate halfway through, on the programme's budget.