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.

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.

Do the following:

1. Click the Let's get started button in the email that you received from Qlik.
2. 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.

3. 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.

   Information note

   Anonymous access tenants can only be created in the Sweden region. If you are not creating an anonymous access tenant, you cannot select the Sweden region.

   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 (London)	eu-west-2	Europe (Spain)	eu-south-2
   Europe (Frankfurt)	eu-central-1	Europe (Milan)	eu-south-1
   Europe (Sweden)	eu-north-1	N/A	N/A
   Asia-Pacific (Singapore)	ap-southeast-1	Asia Pacific (Seoul)	ap-northeast-2
   Asia-Pacific (Sydney)	ap-southeast-2	Asia-Pacific (Melbourne)	ap-southeast-4
   Japan (Tokyo)	ap-northeast-1	Japan (Osaka)	ap-northeast-3
   India (Mumbai)	ap-south-1	India (Hyderabad)	ap-south-2

   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.

4. Click Finish.

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.

• 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:

1. Log in to tenant using the original hostname.
2. Go to the Administration activity center.
3. Navigate to Configuration > Settings.
4. Under Tenant enter the Alias hostname.
5. Optionally, add a Display name.
6. 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

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

Assign user entitlements

In the Administration activity center, under Settings > Entitlements, enable dynamic assignment of both Professional and Analyzer entitlements.

Set up an SMTP server

In the Administration activity center, 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

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.