Deploying the Qlik Cloud tenant

A recommended first step when migrating to Qlik Cloud is to deploy Qlik Cloud and distribute apps from Qlik Sense Client-Managed to Qlik Cloud for consumption. Distributed apps are present both on-premises and in the cloud, supporting analysis in both environments.

It is important that you read Planning your migration to Qlik Cloud and go through the Qlik Migration Center docs before you start deploying Qlik Cloud and migrate users, apps, and other resources. Careful planning simplifies migration considerably.

Assuming that you already have a Qlik Sense Client-Managed deployment, you now need to create and configure Qlik Cloud. Qlik Cloud is a cloud-based enterprise solution for hosting independent or multi-cloud Qlik Sense Enterprise SaaS deployments.

Create the tenant

If you do not already have a subscription for Qlik Sense Enterprise SaaS, contact Qlik.com | Contact sales and complete the application form. One of Qlik's Sales representatives from your region will contact you. Once your account is set up, you will receive an invitation email to create your tenant.

Once you receive your welcome email, you will need to log in to activate your account, and then create and configure your tenant.

If you did not receive an email, you can also create your tenant by logging in to My Qlik. Log in from My Qlik portal or go to Qlik.com and select Log In > Qlik Cloud. For more information, see How to Create a Tenant from My Qlik Portal.

Do the following:

Click the Let's get started button in the email that you received from Qlik.
On the Set up your account page, set a password in Create password. Check the box to indicate that you have read and accept the Qlik terms and conditions, and click Next.

On the Almost finished page, choose a Region.

Selecting the appropriate region to store your data ensures optimal performance. The region will be part of your URL. The default region is selected based on the region that is closest to your location. You can select a different region, but you can’t change region once you have completed the tenant setup. The following regions are available:

Region name	Region code	Backup region name	Backup region code
US East (North Virginia)	us-east-1	US East (Ohio)	us-east-2
Europe (Ireland)	eu-west-1	Europe (Paris)	eu-west-3
Europe (Frankfurt)	eu-central-1	Europe (Milan)	eu-south-1
Europe (London)	eu-west-2	Europe (Spain)	eu-south-2
Asia-Pacific (Singapore)	ap-southeast-1	Asia Pacific (Seoul)	ap-northeast-2
Asia-Pacific (Sydney)	ap-southeast-2	Asia-Pacific (Melbourne)	ap-southeast-4

To request data from data connections through a firewall, you need to add the underlying IP addresses for your region to your allowlist. For more information, see Allowlisting domain names and IP addresses.

Click Finish. You will be directed to the hub.

There is a maximum number of tenants that you can create in a region. Contact Qlik Sales to manage your user account.

For OEM and Enterprise external use deployments, each end customer should be deployed to their own Qlik Cloud tenant. Using a single tenant for all end customers may result in a user having access to visibility of all other users within the same tenant - such visibility may include (but may not be limited to): user names, email addresses and the user’s subject, which is a unique string used to identify the user that is provided to Qlik Cloud by the configured Identity Provider.

Configure the tenant

Define a tenant alias name

You can define an alias for a tenant giving users two options to navigate to the tenant. The original tenant name is assigned when the service account owner (SAO) sets up your account. An alias that might better represent your company can be configured or changed at any time.

The tenant hostname never changes. The hostname is used for recovery and as a secure way to access your tenant.

A tenant admin can update the Alias hostname then log in using the new alias.
Information noteChanging the tenant alias will cause users who have bookmarked the original tenant alias to have to update their bookmarks. The new tenant alias must be communicated to users.
A tenant admin can remove the Alias hostname.
A tenant admin can update the Display name of their tenant.

To configure or change the tenant alias, complete the following steps:

Log in to tenant using the original hostname.
Go to the Management Console.
Navigate to Configuration > Settings.
Under Tenant enter the Alias hostname.
Optionally, add a Display name.
Navigate to hostname alias and log in to verify that tenant works with alias.

Create a new identity provider configuration

To simplify the migration, it's highly recommended to use your own identity IdP, and to create groups when configuring the IdP.

How to create a new identity provider configuration is described here: Creating a new identity provider configuration

Verify that the subject of the IdP aligns with the corresponding string sent from Qlik Sense Client-Managed to your Qlik Cloud tenant, see: Migrating users, groups, rules, and user allocations. If they don't align, it will be necessary to edit section access for the users. See: Managing data security with Section Access. Alternatively, you can make changes to the subject in the users.csv file that you generate from the user data in the Migration app.

When set up, try to create a space and assign groups as members.

Assign user entitlements

In the Management Console, under Settings > Entitlements, enable dynamic assignment of both Professional and Analyzer entitlements.

Set up an SMTP server

In the Management Console, under Settings > Email server, configure email support, see: Configuring email support.

Distributing apps from Qlik Sense Client-Managed to Qlik Cloud

Distributing apps from your Qlik Sense Client-Managed environment to the cloud is a good start to your Qlik Cloud journey, regardless of what your long-term plans look like. You can quickly get started working with apps and explore the new Qlik Cloud environment. If restrictions stop you from performing a migration, or you just want to evaluate what Qlik Cloud has to offer, this step is sufficient in the short term. However, the distributed apps are not truly migrated. They are linked to the source app in Qlik Sense Client-Managed and reloads in the source app are by default propagated to the Qlik Cloud app. Migrated apps don't include any dependency on the corresponding app in Qlik Sense Client-Managed. If and when you decide to migrate apps to your cloud environment, you will want to remove the distributed apps from the cloud environment and work with the migrated apps instead. The removal is straightforward.

When you publish apps to streams in Qlik Sense Client-Managed, you can also distribute them to your Qlik Cloud for consumption.

See: Distributing apps to Qlik Cloud

An alternative to distributing apps to Qlik Cloud is to use links in your Qlik Cloud environment that link to the apps in Qlik Sense Client-Managed. Then, when you want to migrate the apps to your cloud deployment, you delete the links. See: Managing generic links.

Requirements for distributing apps to cloud

The primary components of a multi-cloud deployment are:

Qlik Sense Client-Managed, deployed on-premises
Qlik Cloud, deployed to a Qlik-managed cloud infrastructure

With those two components deployed, you can configure your multi-cloud deployment and distribute apps created in Qlik Sense Client-Managed to the cloud for consumption.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!

Leave your feedback here