Skip to main content Skip to complementary content

Using the migration tool

The migration tool will migrate your QlikView NPrinting 16 projects to your new environment. Project files (.nsq) are exported and imported as .zip files.

Information noteThis process is for migrating project files from QlikView NPrinting 16 to Qlik NPrinting November 2019 or later. To move reports between different environments using the same version of Qlik NPrinting, see: Moving reports between environments.

You can import QlikView NPrinting 16 projects into Qlik NPrinting November 2019 one project at a time. Each QlikView NPrinting 16 project will be imported into a new Qlik NPrinting app. See: Working with apps. The app name will contain the import date and time. Importing the same QlikView NPrinting 16 project multiple times will result in many different apps, one for each import. Apps created from the same project are not overwritten.

Warning noteIf you have an existing Qlik NPrinting installation, you should create a backup before starting the migration. See: Backing up Qlik NPrinting.


  • A QlikView NPrinting 16 project file (.nsq), exported as a .zip file. See: Planning your migration.
  • A Qlik NPrinting user with an Administrator role assigned to them. You can also assign Import NPrinting 16 projects rights to a different role. See: Managing roles.

    Information noteIf you enable this permission, that role gains full control of all apps and task executions. This is done in order for the user performing the migration to have access and edit rights to the new Qlik NPrinting app that will be created as a result of this task.

Running the migration tool

The import job will run as a single job until completed. You cannot select individual entities to import. The entire QlikView NPrinting 16 project will be imported.

Do the following:

  1. Log into Qlik NPrinting November 2019 or newer as an Administrator, or a role with Import NPrinting 16 projects rights.
  2. In the main menu, go to Admin and, click on Import NPrinting 16 projects.
  3. In the top right corner, click on the green Import Project button.

    Import project button

  4. Click on Browse… and select the QlikView NPrinting 16 exported .zip file. You can import one project at a time.

    Browse button for uploading NPrinting 16 projects.

  5. Under Connections found, verify your connection paths. The imported paths to your QlikView documents may need to be updated. Paths are related to the Qlik NPrinting November 2019 or newer server. Relative paths are not supported and must be updated before proceeding.

    In case of connection errors or warnings, open the connection in the Qlik NPrinting web console and troubleshoot as usual. For example, you can click the Verify connection button.

  6. Click the green Start Importing button on the bottom right.

    Connection paths when importing

  7. Wait until all connection caches are generated. In case of errors, open the specific connection, correct the error, and re-generate the cache as usual. See: Connecting to QlikView documents.

    Migration in progress screen.

  8. As the migration tool runs, the result of each completed step is displayed. Some rows will have blue icons that link to the related migrated entity. You can click these to review import status.

    Import results screen, with errors and warnings

  9. Each migrated entity with a Warn or Error status has a detailed list describing the issue. You can edit the entity to solve any issues and mark it as OK.
  10. Once the migration tool stops running, review all messages to ensure your import was successful.

    Migration completed screen with details

Logs and troubleshooting

Log messages are visible on the import page. Once the migration has completed, click the Download logs button to quickly view logs.

To review old logs, go to Admin > Import NPrinting 16 projects and click on the import you want to check.

If you try to import unsupported features, they will be logged as not imported. If your migration has warnings or errors, see: Troubleshooting your migration.

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!