Migration to Qlik Cloud - Your Alternative to Qlik Data Transfer

Challenges of the End-of-Life of the Qlik Data Transfer Client (2026)

By 2026, the Qlik Data Transfer Client will be discontinued. This tool has so far worked according to the push principle, allowing data to be selectively uploaded and prepared before being transferred to Qlik Cloud. This enabled companies to ensure data quality in advance, optimize data volume, and maintain data protection.
With the discontinuation of this solution, many organizations face the task of implementing alternative approaches to maintain the same level of efficiency, security, and return on investment (ROI) in their data migration.

Learn more about migrating to Qlik Cloud

Current Options for Transferring Data to Qlik Cloud

The Qlik Direct Access Gateway remains the central option. It works according to the pull principle: data is loaded directly from QlikView or Qlik Sense Client-Managed into the cloud. This approach is particularly straightforward and does not require an additional intermediate layer.
At the same time, it comes with typical challenges — for example, data can only be processed or filtered after being imported into the cloud. This means anonymization or compression cannot take place in advance. For some organizations, this may lead to additional requirements regarding governance, data protection, storage planning, and long-term ROI.

The Qlik Data Transfer Client – which will no longer be available in the future – operated on the push principle. This allowed data from local data sources, Qlik apps, or monitored folders to be uploaded directly and automatically to Qlik Cloud, including scheduled data uploads and the option to automatically reload dependent apps.

The Solution: iVIEW Dataflow – Future-Proof and Powerful

With iVIEW Dataflow, Informatec offers a comprehensive and enhanced alternative to the Qlik Data Transfer Client. The solution takes over its core functionality and extends it with additional benefits:

• Data can be prepared in advance and then securely transferred to the cloud (push principle)
• Existing Qlik load chains from Qlik Sense Client-Managed can be imported and used for migration
• Data can be visualized, filtered, anonymized, optimized, and compressed before transfer
• The migration process is accelerated and operations in Qlik Cloud are made more efficient
• Reduced data volumes lead to lower cloud capacity requirements, better cost control, and a sustainably higher ROI

Conclusion

Companies currently using the Qlik Data Transfer Client should proactively switch to a future-proof push solution. With iVIEW Dataflow, migration to Qlik Cloud is not only seamless, but also efficient, compliant with data protection regulations, and delivers an optimized ROI through the sustainable use of cloud resources.

Learn more about iVIEW Dataflow