Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Forums for Qlik Analytic solutions. Ask questions, join discussions, find solutions, and access documentation and resources.
Forums for Qlik Data Integration solutions. Ask questions, join discussions, find solutions, and access documentation and resources
Qlik Gallery is meant to encourage Qlikkies everywhere to share their progress – from a first Qlik app – to a favorite Qlik app – and everything in-between.
Get started on Qlik Community, find How-To documents, and join general non-product related discussions.
Direct links to other resources within the Qlik ecosystem. We suggest you bookmark this page.
Qlik gives qualified university students, educators, and researchers free Qlik software and resources to prepare students for the data-driven workplace.
Qlik DataTransfer will be officially End-of-Life by the end of Q1 2026.
It will be removed from the Product Downloads site later this year and will no longer be available for new installations or upgrades. Qlik will provide support until April 30, 2026.
Support for Qlik DataTransfer ended in April of 2026, and it is expected to stop functioning after November 29th, 2026. Review and implement the recommended alternatives documented in this blog post. A more in-depth breakdown of the alternatives will follow in late October.
To ensure a smooth transition, we recommend you begin utilizing Qlik Data Gateway – Direct Access, the supported alternative.
We have compiled a list of resources to assist you in adopting Qlik Data Gateway - Direct Access:
Additionally, for those needing feature parity with Qlik DataTransfer, we recommend pairing with the File Connector via Direct Access, REST Connector via Direct Access, and the generic ODBC Connector.
Further Resources:
We will share an update later this year with the exact deprecation and end-of-support dates.
For assistance, please contact Qlik Support. Questions on how to contact Qlik Support.
Thank you for choosing Qlik,
Qlik Support
Effective in the Qlik Sense Enterprise on Windows November 2026 release, and in the latest patches for May 2025, November 2025, and May 2026, the ODBC connector used by Qlik Sense Enterprise on Windows will no longer support connections secured with TLS 1.0 or TLS 1.1. To maintain uninterrupted connectivity, customers should upgrade their environments to use TLS 1.2 or higher ahead of applying these releases or patches.
The changes are expected after October 28th, 2026 and will be communicated in the respective release notes.
TLS 1.0 and TLS 1.1 are legacy encryption protocols that are no longer considered secure and have been deprecated across the industry for several years. Removing support for these older protocols in the ODBC connector aligns Qlik's connectivity stack with current security standards and reduces exposure to known vulnerabilities in outdated TLS implementations.
This change affects the ODBC connector in Qlik Sense Enterprise on Windows only. At this point, Qlik Sense Desktop and QlikView are not affected by this change. The standalone ODBC Connector (QvOdbcConnectorPackage.exe) remains unaffected for the time being.
Any data source connection made through the ODBC connector in Qlik Sense Enterprise on Windows that relies on TLS 1.0 or TLS 1.1 will be affected once support is removed, regardless of whether the TLS version is enforced by the data source itself, a network intermediary, or the client driver configuration.
If your data source, ODBC driver, or the underlying operating system is currently configured to negotiate connections using only TLS 1.0 or TLS 1.1, those connections will fail once you move to a version of Qlik Sense Enterprise on Windows that removes TLS 1.0 or TLS 1.1 support.
Reload tasks, extensions, and any other workflows using affected ODBC connections will no longer be able to connect to the data source.
If you have questions or need assistance planning your upgrade, our forums are open to you, and Support is only a chat away.
Thank you for choosing Qlik,
Qlik Support
We are excited to open the Public Preview of Studio AI Assistant, the most significant addition to Qlik Talend Studio in years and the first step in bringing agentic assistance to the entire Studio development experience. It is a capability the Studio community has asked for consistently, and the prototypes we showed at Qlik Connect were met with exactly the response we hoped for. Now it is in your hands.
If you already build in Studio, this post walks through what the assistant does today, component by component. If you are a Qlik customer who has never opened Studio, a quick orientation first.
Qlik Talend Studio is the design environment at the heart of Qlik Talend Cloud for engineers who build data integration pipelines, application integration routes, and data services. It pairs a visual, low-code canvas with an extensive library of connectors and components, full control over custom logic when you need it, and deployment wherever your data lives, on premises or in the cloud. Studio is where enterprise pipelines are built with the rigor production demands, and it is the foundation Studio AI Assistant is designed around.
Studio AI Assistant takes two forms inside Studio. The first is an embedded assistant window, available across the application and scoped to whatever you currently have selected: open it while working on a job and it already knows the job; move to a component and its context moves with you. Describe your intent in plain language and the assistant builds from it. The second is a set of dedicated buttons in the interface for the tasks you will do most, such as generating documentation for the job in front of you, one click and no prompt required.
Behind both, every request is secured through the Qlik Talend Cloud LLM Gateway on Qlik Cloud, so the assistant operates inside the same governance boundary as the rest of your Qlik Talend Cloud tenant. There is nothing to configure and no separate console to visit.
One principle runs through all of it: you stay in control. The assistant generates, suggests, and explains. You review, refine, and decide what ships.
The Public Preview opens with the capabilities that cover the everyday work of building in Studio, from documenting what you have built to drafting something new from a description. Watch the video below for a first look, then read on for what each one does and where you will find it in Studio.
Ask the assistant to document the job and it reads the job as built (the sources, the transformations, the targets) and completes the description and purpose fields for you: what the job consolidates, where each input comes from, and the business rules it enforces. The same applies to routes and data services. Documentation becomes part of the build rather than a task that follows it, and the next engineer who opens the job finds an accurate description waiting.
Open the tMap on a customer dimension job and the assistant can automatically map source columns to target columns based on the column descriptions you already have. Where a mapping calls for real logic rather than a straight match, a contextual helper inside the tMap and cMap Expression Builders assist you in constructing the expression. You still make the calls that require judgment, how risk gets classified, which source wins when two disagree. The assistant handles the mechanical work underneath those decisions.
Studio's low-code components cover the vast majority of a pipeline. For the moments that call for custom logic, the assistant turns a prompt into code, right where that code lives:
Describe the calculation or the query you need, review the generated code in place, and keep building. Custom code stays inside the governed flow of the job rather than arriving from somewhere else.
After a job runs, ask the assistant for a summary of the logs and an analysis of possible errors. Instead of working through raw execution output, you start from a plain-language account of what happened and where the likely fault lies, whether that is an upstream schema change, an empty lookup, or a type mismatch three components downstream. The diagnosis is the assistant's. The fix, and the decision to apply it, remain yours.
Describe the pipeline, the API, or the route you need, and the assistant drafts it for you to review and build on. This is the capability the community asked for most, and it is available from the first day of the preview in its initial form. It is also the area we will strengthen most visibly with each monthly release, so expect the assistant's ability to generate, update, and complete jobs, data services, and routes to grow steadily as the preview progresses.
Public Preview is the starting line, not the finish. Studio ships monthly, and every release through the preview strengthens the assistant: broader coverage, better generation, tighter integration with the work in front of you. The assistant you use in December will do more than the one you open today, on the way to General Availability, which we are targeting for Q1 2027.
Preview participants shape that path. The feedback you give during the preview directly informs what we prioritize and how the assistant behaves at GA.
The market is filling with AI coding assistants, and most of them ask you to move your work to where the assistant lives. Studio AI Assistant takes the opposite approach: it brings AI to the environment your pipelines already run in.
Speed and governance were never meant to be a trade-off. Studio AI Assistant is built to deliver both.
We asked the Studio community, and the answer was consistent. In a December 2025 survey of qualified Studio users, AI-assisted job creation and editing ranked as the single most requested capability, selected by 48 percent of respondents, with documentation generation at 45 percent and transformation optimization at 43 percent close behind.
The signal was strong among experienced Studio developers, and stronger still among engineers newer to Studio, many arriving from data and analytics backgrounds, who want to be productive from their first week. Studio AI Assistant is our direct answer to what you asked for.
Studio AI Assistant is available now in Public Preview, in the September release of Studio, for Qlik Talend Cloud Premium and Enterprise customers. There is no additional charge for the assistant during the Public Preview; pricing will be announced ahead of general availability.
Because the assistant runs through the Qlik Talend Cloud LLM Gateway on Qlik Cloud, it is available to Qlik Talend Cloud customers. Talend customers who have not yet moved to Qlik Talend Cloud can talk to their Qlik team about the path there. Qlik customers exploring Studio for the first time can start with a Qlik Talend Cloud trial.
To activate this feature, work with your platform administrator. It is a three-step process:
For more information, see Enabling cross-region inference.
For more information, see Enable feature preview for the tenant.
For more information, see Roles and permissions for users and administrators.
To get started, review the documentation, then open Studio, select a job, route, or data service, and open the assistant. Start by creating documentation on something you have already built, then try auto-mapping in a tMap, a Java or SQL prompt in a component, and a job described from scratch. Tell us what works and what you want next.
Studio has always been where serious data engineering gets done. Starting today, it gets done with an assistant that understands the work. Welcome to the Public Preview!
Qlikデータソンは、Qlikユーザー・パートナーの皆様がスキルとアイデアを競い合うコミュニティイベントです。過去5回はQlikアプリの構築力やデザイン力を競ってきましたが、第6回のテーマは「AI」。Qlik Cloudに搭載されたAI機能を使って、「QlikのAI、こんな使い方ができるのか!」と驚くアイデアを形にし、5分以内のデモ動画で競います。
本日10月15日(木)より、TECH PLAYにて参加申込を開始しました。
Qlik Answers、Qlik MCP Server、AIエージェントなど、Qlik CloudのAI機能を1つ以上、作品の中核として使ってください。テーマもデータも自由です。業務シナリオでも、業務外の題材でも構いません。Claude や ChatGPT など外部のLLMとの組み合わせも歓迎します。これまで培ったQlikのBIスキルと組み合わせた作品も大歓迎です。
こんな方におすすめ!
・Qlik Answers や Qlik MCP Server を触ってみたい、使いこなしたい方
・「AI × Qlik」で業務を変えるアイデアを持っている方
・自社のQlik活用スキルをコミュニティに発信したい方
※Qlikを使い始めたばかりの方も歓迎します。アイデアと伝わりやすさも評価の対象です。
・参加申込:2026年10月15日(木)〜11月24日(火)17:00(定員100名・先着順)
・作業期間:10月29日(木)〜11月30日(月)17:00(オンライン・最大約4週間、ご自身のペースで)
・キックオフイベント:11月4日(水)14:00〜15:30(オンライン・録画公開)
・Qlik審査・ファイナリスト決定:12月1日(火)〜12月8日(火)
・結果発表:12月10日(木)「第6回 Qlikデータソンアワードパーティ」にてファイナリスト作品の上映・最終審査・表彰(東京会場+オンライン配信)
・対象:Qlik製品をご利用中、またはご利用をご検討中の企業の方、Qlikパートナー企業の方(Qlik未経験の方も参加できます)
・部門:ユーザー部門/パートナー部門(部門別に審査・表彰)
・参加形態:個人参加またはチーム参加(1チーム3名まで)。1組1作品。参加費無料
・成果物:5分以内のデモ動画+エントリーシート(Qlik Senseアプリ等の提出は不要)
Qlik Cloud Analytics と Qlik Talend Cloud の両方を、必要なAI機能をセットアップ済みの状態でご利用いただけるQlik Cloud環境をQlikが用意します。事前準備は不要です。
データはご自身でご用意いただくほか、Qlik提供のサンプルデータ(化粧品・トイレタリー企業の売上・EC・問い合わせデータ等)もご利用いただけます。
初心者の方もイメージしやすいよう、15のアイデアを用意しました。詳細はTECH PLAYのイベントページをご覧ください。
・Qlik Answers:経営アシスタント/商品カタログ・コンシェルジュ/社内ルール・マニュアルFAQ
・Qlik MCP Server:「このCSVでダッシュボード作って」/週次レポートの自動生成/Claude Skills × MCPで「Qlikアプリ作成の完全自動化」
・AIエージェント:非分析者向けの対話型探索/「そのデータどこ?」をエージェントに聞く/データ準備の対話化
・Qlik Talend Cloud × AI:データ統合から対話分析まで一気通貫/カタログの自動ドキュメント化/パイプライン運用エージェント
・組み合わせ・体験設計:見る→聞く→深掘り/Slack・Teams連携bot/BIスキル × AI「読めるダッシュボード」
驚き・新規性 / ビジネス価値・実用性 / AI機能の活用度 / 技術的完成度・再現性 / 伝わりやすさ
※Qlik Answersのみの作品も、外部LLMを組み合わせた作品も、同じ基準で評価します。
最優秀賞(部門別)ほか、各賞に豪華賞品をご用意します。
Bose、Meta Glasses、Dyson 、リファなど
※こちらは賞品の一例です。賞品は一部変更となる可能性がございます。
ファイナリストの発表と表彰は、12月10日(木)の「第6回 Qlikデータソンアワードパーティ」で行います。ファイナリスト作品を上映し、パーティ会場での最終審査で受賞者を決定します。受賞された方には、その場で一言コメントをいただく予定です。
開催形態は東京会場+オンライン配信(お申し込み多数の場合)です。東京会場の席は抽選で決定し、抽選に外れた方はオンラインでご視聴いただけます。データソン参加者の皆様は、ぜひアワードパーティにお申し込みください。ご欠席の場合も受賞は有効で、賞品は後日お送りします。データソンに参加されない方も、アワードパーティのみのご参加を歓迎します。アワードパーティの申込ページは別途ご案内します。
Qlik Answers、Qlik MCP Server、AIエージェントの基本を学べる資料・動画のリンク集をTECH PLAYのイベントページに掲載しています。あわせてご覧ください。
▼ お申し込み(TECH PLAY)
[TECH PLAY申込URL]
お問い合わせ:TECH PLAYの申込ページからQlikデータソン事務局にお問い合わせください。
皆様のご参加をお待ちしています。
Beginning January 2027, the Qlik Cloud and Direct Access Gateway (DAG) ODBC Connectors will no longer support connections secured with TLS 1.0 or TLS 1.1. To maintain uninterrupted connectivity, customers should upgrade their environments to use TLS 1.2 or later in advance.
For the relevant announcement and dates regarding Qlik Sense Enterprise on Windows, see ODBC Connector for Qlik Sense Enterprise on Windows: Upcoming End of Support for TLS 1.0 and TLS 1.1 in 2026.
Refer to the release notes and What's New upon release for details.
TLS 1.0 and TLS 1.1 are legacy encryption protocols that are no longer considered secure and have been deprecated across the industry for several years. Removing support for these older protocols in the ODBC connector aligns Qlik's connectivity stack with current security standards and reduces exposure to known vulnerabilities in outdated TLS implementations.
This change affects the ODBC connector in Qlik Cloud and Direct Access Gateway only. Customers using Qlik Sense Enterprise on Windows should instead refer to the separate announcement covering that change.
Any data source connection made through the ODBC connector in Qlik Cloud or Direct Access Gateway that relies on TLS 1.0 or TLS 1.1 will be affected once support is removed, regardless of whether the TLS version is enforced by the data source itself, a network intermediary, or the client driver configuration.
If your data source, ODBC driver, or the underlying operating system is currently configured to negotiate connections using only TLS 1.0 or TLS 1.1, those connections will fail once this change takes effect.
Reload tasks, extensions, and any other workflows using affected ODBC connections will no longer be able to connect to the data source.
This will impact you on January 20, 2027 for Qlik Cloud, or following your Direct Access Gateway update to release 1.8.4.
If you have questions or need assistance planning your upgrade, our forums are open to you, and Support is only a chat away.
Thank you for choosing Qlik,
Qlik Support
本 Web セミナーシリーズでは、Qlik でデータからアクションを起こすデータ主導のビジネスで成功しているお客様より、課題から導入の経緯、デモンストレーション、活用例などをご紹介します。
サッポログループは、営業、物流、会計をはじめ、バリューチェーンの各領域を横断したデータ活用を支える共通基盤「SAPPORO DATA FACTORY」を構築し、全社的なデータ民主化を推進しています。本 Web セミナーは、データ基盤構築に取り組んだ背景や、Qlik Talend Cloud® を採用した理由、そして導入によって得られた成果をご紹介します。データドリブン経営を支える基盤づくりの実践知をお届けします。
Hi everyone,
Want to stay a step ahead of important Qlik support issues? Then sign up for our monthly webinar series where you can get first-hand insights from Qlik experts.
The Techspert Talks session from October looked at AI Best Practices with Qlik Cloud.
But wait, what is it exactly?
Techspert Talks is a free webinar held on a monthly basis, where you can hear directly from Qlik Techsperts on topics that are relevant to Customers and Partners today.
In this session we will cover:
There have been new Qlik Sense features the past few months that I was excited to see. One of my favorites, which I am sure you are aware of, is the layout container. If you have not heard about it, check out Michael’s blog post here. Another favorite of mine is the copy and paste style feature which allows developers to copy and paste styles from one visualization to another. With all the styling options available in visualizations, being able to copy and paste styles saves time and eliminates the need to go into the styling properties of each visualization and set all the styling options you would like to use.
Some of the latest charts that have been upgraded to the new styling property panel are the Grid, Funnel and Sankey, giving users the ability to customize the title, subtitle, footnote, and background of a chart as well as the style the axes, labels, legends, and values in a visualization. Borders and shadows can be added to these visualizations as well.
The Filter Pane now has font styling for the title, subtitle, footnote, and header as well as font header and content styling. Like the charts above, borders and shadows can be added as well. Developers can change the background color or use an image in the background and control the color of the selected state. Here are a few examples.
With all these styling options, it is awesome that developers can now copy and paste the style from one visualization to another. If you remember the QlikView days, you know how valuable this feature is. Assume I have an app with a theme applied and have made some styling changes to the Margin KPI (see image below). If I want to apply the same styling changes to the Margin %, I have two options. One option is to open the styling properties of the Margin % KPI and make the same changes to the background color, border color and shadowing.
The second option and the easiest option is to right click on the Margin KPI while in Edit mode, click on the three dots (…) and select Copy style.
Then right click on the Margin % KPI, click on the three dots (…) and select Paste style.
That is a lot easier than styling the KPI manually, especially if there are multiple visualizations to update.
There are a few limitations to using the copy and paste style - you cannot copy and paste the style in a map or a master visualization. New styling properties for visualizations are being add all the time, giving users many options to style and make their app stand out. The copy and paste functionality is a great addition to Qlik Sense and makes designing and styling apps easier.
Thanks,
Jennell
Qlik is updating the S3 connector (V1). As part of this update, the Creation_Date column in the ListBuckets table is being renamed to CreationDate.
See Amazon S3 | Qlik Web Storage Provider Connectors for general information about the connector and its availability.
This is a breaking change: any load script or data model that references the old Creation_Date column name against the ListBuckets table will fail on reload once the change takes effect.
We have reviewed usage across our tenants and have not identified any customers currently using this column. No impact is expected.
If a reload of the ListBuckets table fails after this update, update your load script to reference CreationDate instead of Creation_Date. This is the only change required to restore functionality.
No other columns or tables in the S3 connector (V1) are affected. Simply update the column name in your script and reload again.
A note for Qlik Cloud users: As rollout timing can vary, there is no action you can take in advance since the change cannot be pre-empted or scheduled around.
If your script references Creation_Date in the ListBuckets table, that reload will fail once the change takes effect or after you upgrade Qlik Sense Enterprise on Windows and/or the Web Connector package.
If you have any questions, we're happy to assist. Reply to this blog post or take your queries to our Support Chat.
Thank you for choosing Qlik,
Qlik Support
The Oracle Essbase for Qlik Sense Enterprise on Windows (client-managed) connector will reach end of life and is therefore no longer recommended for use.
The Essbase Connector will reach end of life beginning with the Qlik Sense Enterprise on Windows May 2027 release and will no longer be included in the installation package.
Earlier Qlik Sense Enterprise on Windows releases that still include the Oracle Essbase connector are unaffected by this change and continue to be supported according to their normal lifecycle.
Applications and data connections using the Oracle Essbase connector will stop working once an environment is upgraded to the Qlik Sense Enterprise on Windows May 2027 release. As a workaround, Qlik Sense Enterprise on Windows supports connecting to systems that offer a REST API using the Qlik generic REST connector. Essbase exposes a REST interface that can be used as an alternative way to bring the same data into your applications.
We're happy to assist with any follow-up questions. Reply to this blog post or take your queries to our Support Chat.
Thank you for choosing Qlik,
Qlik Support
日本最大級の自治体向け情報システム展示会、「地方自治情報化推進フェア2026」では、自治体 DX やマイナンバーカードの利活用推進に資する最新の情報や取り組みをご紹介します。
Qlik は、パートナー企業の AWS ブース内にて、ブースとシアターセッションで参加します。
自治体における DX 推進や生成 AI 活用、AWS との連携による、自治体業務の課題解決に向けた取り組みについてご紹介します。
【開催概要】
日時:10/27(火)9:30 - 17:30
10/28(水)9:30 - 17:00
会場:幕張メッセ国際展示場展示ホール 1 - 3
千葉県千葉市美浜区中瀬 2-1
定員:事前登録制
主催:地方公共団体情報システム機構(J-LIS)
| Qlik シアターセッション AWS ブース内 |
|
10/27(火)15:00-15:15
|
Dear Qlik Customers,
In April 2026, SAP published a series of updates that will restrict your ability to extract certain SAP data using Qlik products. We are writing to explain what is changing, what it means for your Qlik integration, what you can do next, and how Qlik is responding.
SAP has recently updated SAP Note 3255746 and its API Policy, which together prevent customers from using the ODP-RFC interface to perform bulk data extractions to non-SAP systems. Here is what you need to know.
The CDC connectivity via ODP will be at most risk by the implementation of the June 9th SAP security update, as it will be blocked. The main products affected are:
Other impacted products that also offer ODP functionality are:
The following Qlik Products do not use the ODP-RFC interface and therefore will not be impacted by the June SAP Security update:
You should be in control of your business-critical data, wherever it creates value. Without interoperable architectures, SAP customers like you face higher costs, performance issues, and less freedom to choose, including loss of flexibility in implementing AI.
Qlik already supports alternatives to ODP and is actively developing additional migration paths and solutions to preserve your flexibility through this transition and beyond. We will continue to work on viable alternatives to our ODP endpoints and help you navigate this change on your terms, not SAP's. To learn more about how Qlik can support your specific environment, please reach out to your Qlik representative.
This communication reflects Qlik's current interpretation of SAP's restrictions, which are outside our control and subject to change. Customers should consult SAP's official communications and seek independent guidance on operational and legal impact. Roadmap statements are forward-looking and not commitments; disruptions arising from SAP's decisions do not constitute a defect in Qlik's products or services.
データと AI の活用が重要な経営戦略となる一方、多くの金融機関ではガバナンスの構築やAIエージェントの運用、AI 前提の組織への転換などさまざまな課題に直面しています。金融ビジネス変革を実現するためには、人と AI が協働する持続可能な推進体制を整えると共に、最新の IT テクノロジーやソリューションを積極的に取り入れていくことが求められています。
本イベントでは、基調講演にて株式会社みずほフィナンシャルグループよりデータ基盤・AI エージェント活用の考え方について、特別講演にて株式会社横浜銀行よりデータ・AI 活用の推進について具体的な事例と共にご紹介いただきます。
今すぐ申し込む
【開催概要】
日時:10/28(水)14:00-18:15(受付開始 13:30)
17:45以降:ネットワーキング
会場:JA 共済ビル カンファレンスホール
東京都千代田区平河町 2-7-9 JA 共済ビル
定員:200 名(事前登録制)
主催:株式会社セミナーインフォ
エンタープライズ AI 戦略において、Snowflake 上のデータ基盤整備は急務となっています。本 Web セミナーでは、基幹システムからのリアルタイムのデータパイプライン構築、データ抽出コストを最適化できる Iceberg レイクハウス、分析とデータエンジニアリングをシームレスにつなぐ MCP サーバーをご紹介します。統合からインサイト創出まであらゆるデータから価値を生む AI 時代の最新アプローチをご紹介します。
今すぐ視聴する
| オンデマンド配信 |
AI エージェントに Qlik のすべてを - MCP サーバーで広がる Snowflake 活用 Qlik MCP Server は、Qlik のすべてを AI エージェントに解放する仕組みです。Snowflake Native App を通じて、CoWork や Cortex Agents から自然言語でのアプリ探索やダッシュボード操作、Declarative Pipelines では Snowflake へのパイプライン構築を実現します。分析とデータエンジニアリングを 1 つの AI の入り口でつなぐ新しい形を紹介します。 クリックテック・ジャパン株式会社 |
|
クリックテック・ジャパン株式会社 |
Internet Explorer (IE) was retired by Microsoft in 2022 and no longer receives security updates. In line with this, Qlik will stop shipping the QlikView IE plugin starting with the QlikView September 2027 release.
While you may choose not to move to the QlikView September 2027 upgrade and remain on an older version, your eligibility for maintenance and support may be impacted. Qlik supports versions for 24 months from the initial release date in accordance with its release management policy.
You are encouraged to stay on a supported version and explore one of the options below, if you are impacted:
Thank you for choosing Qlik,
Qlik Support

Contributor and Keywords frequency

Learning resource

All Qlik stakeholders

Learning resource
Sign up for the Private Preview and get hands-on with real-time Iceberg tables in your own Google Cloud project — no lock-in, no re-architecting.
If you're running analytics on Google Cloud, you already know the tension. BigQuery is fast and familiar, but the more data you pour into it, the more your ingestion and storage bill climbs, and the more your data ends up shaped around one engine. You want the performance without the lock-in, you want your data to stay yours, and you want to free up some budget for more valuable workloads.
That's exactly the problem Qlik Open Lakehouse solves — and we're getting ready to launch a Private Preview on Google Cloud this September that you can be part of.
Qlik Open Lakehouse gives you a fully managed way to ingest real-time data straight into Apache Iceberg tables that live in your own Google Cloud Storage buckets. No proprietary formats, no copies, no re-architecting your data layer. Query those same tables from BigQuery, Trino, or any Iceberg-compatible engine, and pay a fraction of what you'd normally spend moving and storing that data.
If you've followed our work on AWS, this will feel familiar — and that's the point. We're porting a proven architecture to Google Cloud, not building a science experiment.
Open Lakehouse builds the bronze layer of your medallion architecture, ingesting and landing real-time data as optimized Apache Iceberg tables, with the heavy lifting executed in your own Google Cloud project. From there, push-down transformations in Qlik Talend® Cloud pipelines create your silver and gold layers directly on BigQuery. Here's the path your data takes, stage by stage.
|
|
1 · Ingestion at the edgeYour sources land through two paths. For change data capture and bulk loads from databases, SAP, and mainframe systems, the Qlik Data Movement Gateway sits in your managed environment and handles CDC and bulk ingestion. For streaming and event data, you connect Kafka topics or Google Cloud Storage directly. Both routes feed the landing stage without your data ever leaving your control. Later in the Private Preview, we'll also add support for Qlik Replicate as a source, so if you're already a Replicate customer, you can onboard data from your existing CDC sources into Iceberg without migrating a single pipeline or switching tools. |
|
|
2 · Compute in your projectTwo components run on Google Compute Engine inside your environment. The Network Integration Agent runs on a standard Compute Engine VM and brokers secure connectivity between the Qlik Talend Cloud tenant and your resources. The Open Lakehouse Cluster — the engine that writes and optimizes your Iceberg tables — runs on a Compute Engine managed instance group built on Spot VMs. That Spot-based design is deliberate: it's where a large part of the cost savings comes from, because you're running the ingestion and optimization workload on Google Cloud's most cost-efficient compute instead of always-on, premium-priced infrastructure. |
|
|
3 · Open storage you ownEverything lands in Google Cloud Storage, split across a landing bucket for incoming data, a config bucket for pipeline metadata, and table storage where your data comes to rest as Apache Iceberg tables. These buckets are in your account. The data is written in an open table format from the start, so there's never a moment where it's trapped in something only Qlik can read. |
|
|
4 · A catalog any engine can useIceberg tables are registered in the Google Lakehouse runtime catalog, so your tables are discoverable and governable through Google Cloud's native catalog rather than a Qlik-proprietary one. That's what makes zero-copy querying real: BigQuery reads the same tables through ELT, and so can Trino or any other Iceberg-compatible engine, all pointing at one physical copy of the data. |
|
|
5 · A managed bronze layer, ready to build onThe pipeline moves through managed stages — landing, storage, and mirror — to produce clean, governed Iceberg tables without you hand-coding each hop. You get Type 1 and Type 2 slowly changing dimensions or append-only patterns out of the box, so history and current-state tables are handled for you. We'll also add zero-copy mirroring to BigQuery during the Private Preview, so you can surface your Iceberg data straight in BigQuery. If you want to replace an existing native table, you can, since downstream queries keep working exactly as before. |
The result: real-time data flows from your sources into governed, query-ready Iceberg tables in your own Google Cloud Storage, optimized continuously, queryable from BigQuery and beyond — and you never gave up control of a single byte.
We didn't start from zero for Google Cloud. Qlik Open Lakehouse first shipped on AWS, where it's already running these same patterns: CDC and streaming ingestion, Spot-based compute for cost-efficient optimization, Iceberg tables in customer-owned object storage, and open querying across engines.
Bringing it to Google Cloud is a deliberate step toward feature parity across clouds. The architecture mirrors what's proven on AWS, adapted to Google Cloud's building blocks: Compute Engine in place of EC2, Google Cloud Storage in place of S3, BigQuery and the Google Lakehouse runtime catalog as the native query and catalog layer. Same engine, same principles, GCP-native execution.
This matters because of what it says about our direction. We believe you should be free to choose where your data lives, which engine queries it, and to change your mind later without a migration project. Delivering the same open lakehouse capability across AWS and Google Cloud, with more to come, is how we make that freedom real rather than a slide in a pitch deck.
Everything above maps to three things we care about:
|
TRUST
Build governed data products in Qlik Talend Cloud on top of your Iceberg tables. Your data stays in open Apache Iceberg format, in your own account. |
FREEDOM
Query from BigQuery, Trino, or any Iceberg-compatible engine, and swap or add engines later without re-architecting. No lock-in to a single vendor or format. |
COST OPTIMIZATION
Spot VM compute and zero-copy, single-storage architecture mean you spend far less to move and hold your data at scale. |
We're accepting participants now, and we're prioritizing organizations already standardized on Google Cloud and working with BigQuery or Apache Iceberg in their accounts.
Request your spot in the Private Preview →Opt in through the form and the Qlik team will reach out to schedule a welcome call. Already signed up? Sit tight — we'll be in touch.
The Region Mover, available with the Qlik Talend Cloud Migration Toolkit (QTCMT), enables users to migrate a Talend Cloud (TC) or Qlik Talend Cloud (QTC) tenant to another Qlik Talend Cloud tenant while either remaining on Talend 7 or upgrading to Talend 8.
Before starting a migration, users can view the source tenant inventory directly in the Qlik Talend Cloud Migration Toolkit. This provides visibility into the currently existing assets and those available for migration.
The migration is organized into three steps:
For questions or assistance, please contact Qlik Support.
There are several scenarios where customers may need to move assets to a different region, including:
Region Mover enables faster migration, migrating assets to a new tenant more than 20x faster than performing the same migration manually, and significantly simplifies each migration step while giving you full control over exactly which assets get migrated.
Migration options include:
Download the latest release from the Migration Center page on Qlik Help.
Thank you for choosing Qlik,
Qlik Support
Stay a Step Ahead
This issue is about staying ahead of the curve and getting more from what you're already running. Read on for this month's best insights and resources.
In this issue
We asked 200+ enterprise leaders what stalled their agentic AI rollouts. The blocker was not the models, it was the data feeding them, so if agentic AI is on your roadmap, you need to read this first.
Read the State of Agentic AI →Steffen Bischoff takes one dataset from core system to governed data product, versioned in Git and quality-checked by agents. The example is insurance data, but the pattern works on whatever source you run.
Watch the Walkthrough →
Consolidating on Qlik Talend took AriensCo's partner onboarding from weeks to days, proof it doesn't have to stay that way for any team maintaining more integration tools than it can name.
See How AriensCo Did It →
Congratulations to the 2026-2027 class of Qlik Luminaries: leaders shaping Qlik's future through real-world insights, product influence, and advocacy.
Meet the 2026 Luminaries →Stay a Step Ahead
This issue is about staying ahead of the curve and getting more from what you're already running. Read on for this month's best insights and resources.
In this issue
Valpak's customers now ask packaging and ESG questions in plain language instead of compiling the data themselves, a pattern that works for any team fielding the same report requests every month.
See How Valpak Did It →
Qlik asked 200+ enterprise leaders what stalled their agentic AI rollouts. The blocker was not the models, it was the data feeding them, so if agentic AI is on your roadmap, here's what you need to read first.
Read the State of Agentic AI →Try upcoming features before everyone else, so you're ready to use them the moment they launch, not scrambling to catch up.
Explore Public Previews →
Congratulations to the 2026-2027 class of Qlik Luminaries: leaders shaping Qlik's future through real-world insights, product influence, and advocacy.
Meet the 2026 Luminaries →