Let me begin with a caveat: I have used "Data Transfer", and I currently use "Data Gateway"... As a user and not as a Qlik data transfer expert... I don't know of a way to move a QVD file that exists inside of your firewall as a file transfer with either "Data Transfer" or "Data Gateway". You can move an existing QVD file from inside your firewall to a Qlik space manually using this technique:
1) Using the Qlik Analytics "Catalog" menu option, use the space selector to select the space where you want to land the QVD file.
2) Once the space is selected, click on the "Create New" button found in the upper right hand corner of the "Catalog" screen.
3) From the list of things that you might be able to create, select "Dataset". a "Connection - Select tables" screen will appear.
4) Press the "Upload Data File" button found in the upper right corner of the "Connection - Select tables" screen.
5) In the "Add File" screen that appears, press the Browse button and navigate to the file that you want to upload from your local computer (inside your firewall). Select that file and upload it. The qvd file will be copied into the Qlik space that you selected.
You can use this approach to copy QVD files that exist in a QVD library inside your local Qlik Sense or Qlik View server. There may be a way to use "Automations" to automate this process, but that Automations ability is pure conjecture on my part.
I have also created Qlik Apps in Qlik Cloud with load scripts to reach through "Data Gateway" and load data from data sources inside my local firewall, and then save that data as a QVD file on my Qlik Cloud server. I could not connect to a QVD file inside my firewall to do this. I needed to connect to a database, etc. So a similar script that is used to create your QVD files inside your firewall may be recreated using a connection through "Data Gateway" (and possibly "Data Transfer") to load that same data into a Qlik Cloud space. This approach, however, does place double the demand on your local data engines - once to load locally and once to load into the Cloud. If you are not careful it will also create slightly different sources of truth because the local file will be generated in a slightly different time than the file in Qlik Cloud.
For my organization, we began by creating a QVD file library in Qlik Cloud. We placed different QVD files into different spaces, and used user access controls to each space to manage data access governance. Over time we moved to "Data Gateway" connecting directly to our local data lake. When connecting to a database inside of our firewall (we are almost entirely as SQL Server database shop), we can pass credentials through data gateway and so we can use tried and true SQL Server user access with Active Directory (or whatever it calls itself today) to controlled access via user roles.
I hope this helps,
BuildItStrong
