Connecting to your data
Tag your data connection’s status and method of migration. You can track progress in the Data connection sheet in the Migration app.
-
Validate your migration / connectivity strategy for each data connection type:
-
Native – Cloud based sources for which you can connect from SaaS.
-
Data Gateway – Data Access – data sources that will remain on premise.
-
-
Folder connections should be migrated to data files within a shared / managed space or some storage provider (S3, OneDrive).
-
Data connections used with few apps should be created in same space as the application.
-
Data connection used with many apps should be created in its own shared space to facilitate single connection definition / reuse.
-
Web Files connections should be replaced with REST or OData where possible.
-
Manually migrate / create new connections to SaaS.
Moving QVDs
Moving data is the third phase of your migration project.
Planning your data migration
-
List your data sources by business and project.
-
Define your data migration strategy based on your data sources and tools. See Planning your migration to Qlik Cloud.
Examples
A multi-project platform
| Business | Projects | Data sources |
|---|---|---|
| RH | Project 1 | On-premises data sources |
| RH | Project 2 | Cloud-based data sources |
| CRM | Project 1 | Cloud-based data sources |
| CRM | Project 2 | On-premises data sources |
| Finance | Project 1 | On-premises data sources |
| Finance | Project 2 | Cloud-based data sources |
Cloud-based data sources
Move your Qlik Sense assets using only data sources on cloud.
Prerequisites
-
A Qlik Sense tenant
-
A specific space in which you define your data connections for your projects (optional)
Configuration
-
Create your data and folder connections, see Data Sources in Qlik Sense SaaS
-
For each app (QVD generators, analytics apps), change the call to your data folder connections in the load script using this syntax: lib://<spacename>:<dataconnectionname>
On-premises data sources
Distributing apps to Qlik Cloud should be the first step of your migration plan. This will help reduce the infrastructure footprint of your Qlik Sense Client-Managed site. See Distributing apps to Qlik Cloud.
Qlik Data Gateway - Direct Access
Qlik Data Gateway - Direct Access provides a data connection type with which Qlik Cloud applications can securely access and analyze enterprise data that resides behind a firewall. There are many connector types available. The Direct Access gateway simplifies migration considerably and makes data stored behind a firewall available for analysis in a cloud analytics environment.
You can migrate Qlik Sense Client-Managed applications to the cloud by using the migration tools or by exporting the applications from the Client-Managed Qlik Management Console and importing them through the Analytics Services page of Qlik Cloud.
New data connections will need to be set up in Qlik Cloud, however the configuration of these connections is very similar to Client-Managed connections.
The Qlik Cloud application connection strings can then be changed and the application reloaded. See Data Gateway - Direct Access.
Bring your own data movement (BYODM)
You can use your own tools and scripts to move data in your cloud storage solution or directly in Qlik Cloud, if for example Qlik DataTransfer is not suitable.
QVDs transfer in your cloud storage solution
-
Develop your scripts using your cloud provider tools or APIs to transfer your QVDs.
-
Use your enterprise scheduler to trigger the transfers.
QVD transfer in your Qlik Cloud tenant
-
Use qlik-cli to develop scripts to transfer your QVDs directly to your tenant.
-
Use your enterprise scheduler or Qlik Sense Scheduler Service to trigger these scripts.
When using Qlik Sense Scheduler Service, define an external program task to execute the transfer script. Chain this task to the reload task that generates the QVDs to transfer. Use uploadwlikclouddatafile.ps1 and uploadqlikclouddatafolder.ps1 to assist you.
