Managing connections
Last updated: 2026-11-03This page provides an overview of how to manage environment connections within the Qlik Analytics Migration Tool. Connections define the source and target systems for migration and are configured once, then referenced across multiple migration plans and projects.
Each plan must specify a source and target connection. By predefining these connections in the Connections tab, they become reusable components throughout the migration configuration process.
Overview of connection tasks
The Connections tab enables the setup and maintenance of the following connection types:
- Source connections
- Qlik Sense Client-Managed
- QlikView
- Qlik NPrinting
- Target connections
- Qlik Cloud
Once configured, connections are available for selection in any migration plan. Each connection is independently editable and may be tested prior to use.
QlikView conversion uses the QV2QS converter directly and no longer needs a connection. The Qlik Sense Converter connection type is no longer offered. An existing Qlik Sense Converter connection still loads and can be edited, but a new one cannot be added.
Connection security
The following applies to all connection types:
- The option to accept any certificate turns off certificate and host name validation. The server identity is then unverified, and credentials are readable in transit. Use this option only when you accept these risks.
- Redirects are not followed on any Qlik connection.
- A URL with a non-HTTP scheme, or a URL that points to a link-local address, is refused before any credential is sent.
Available topics
Use the following sections to manage specific connection types and tasks:
Creating connections
- Creating a Qlik Cloud connection
- Creating a Qlik Sense Client-Managed connection
- Creating a QlikView connection
- Creating a Qlik NPrinting connection
Maintaining connections
Best practices
- Use clear and descriptive names for connections (for example,
QlikCloud-Prod,APAC-QlikView) - Define separate connections for development, test, and production environments
- Validate each connection before referencing it in a migration plan
- Avoid removing connections that are currently in use by active plans or projects