Upgrading and Migrating QlikView Server: A Practical Guide

If you're running QlikView Server and thinking about upgrading to a newer version, you've got two paths: upgrade in place on your current server, or move everything to a fresh machine while upgrading. Either way works, but the migration route gives you a chance to start clean with new hardware or a different setup.

What You Need to Know Before Starting

The upgrade process differs depending on which version you're currently running. If you're on QlikView Server 12.00 or later, you're in good shape—this guide covers exactly what you need. But if you're still running 11.20 or earlier, you'll want to check out the specific migration documentation for moving from 11.20 to November 2017 or later versions. The process has some quirks when jumping across those older version boundaries.

One thing that catches people off guard: shared files with the .Shared extension don't automatically convert to .Tshared files during the upgrade. You'll need to handle that conversion manually afterward. The good news is all your bookmarks and user objects inside those shared files stay intact—nothing gets lost in the transition.

Version Compatibility You Can't Ignore

Here's something that can derail your upgrade if you're not careful: Qlik NPrinting compatibility. If you're using NPrinting alongside QlikView, your NPrinting version must match or exceed your QlikView version. Planning to upgrade to QlikView May 2023 IR? You need to upgrade NPrinting to May 2023 IR or later at the same time. This isn't a suggestion—it's a hard requirement.

👉 Need reliable server infrastructure for your QlikView upgrade? Check out high-performance dedicated servers built for data-intensive applications

The Migration Scenario: Moving to a Different Server

Migrating to a different server adds extra steps, but it's pretty straightforward once you know what to handle. The main thing is dealing with certificates and the machine name change. QlikView ties some of its licensing and security to the server identity, so you can't just copy files over and expect everything to work.

When you migrate, you're essentially doing a fresh installation on the new server, then carefully moving over your configuration, apps, and user data. The certificates need special attention because they're part of how QlikView servers identify themselves and communicate securely.

What About QlikView Desktop?

This whole discussion focuses on QlikView Server, but if you're also upgrading desktop installations for your users, that's a separate process. The desktop upgrade has its own documentation and steps—don't assume they follow the same pattern as the server upgrade.

Getting Your Upgrade Strategy Right

The smartest approach is planning around your current setup and where you want to end up. Upgrading in place is faster if your hardware is solid and you're just moving to a newer software version. But if you're dealing with aging hardware, want to change server configurations, or need to rename your server, migration during the upgrade makes more sense.

Think through your downtime window too. Users can't access QlikView during the upgrade process, so you'll want to schedule this during off-hours or a maintenance window. The actual upgrade time varies based on how many apps you have and how complex your configuration is, but budget more time than you think you'll need.

👉 Looking for managed hosting that handles server maintenance while you focus on your BI platform? Explore flexible cloud solutions

The shared file conversion issue is worth a separate mention because it's easy to miss. After your upgrade completes successfully, you'll need to run through your shared files and convert them from .Shared to .Tshared format. This isn't automatic, and if you skip it, users might run into issues accessing their shared content.

Key Takeaways for a Smooth Upgrade

Before you start, document your current configuration—server settings, user access rules, security setup, all of it. Having a complete picture of your existing environment makes troubleshooting much easier if something unexpected happens.

Test the upgrade on a non-production environment first if you can. Even a simple lab setup gives you a chance to spot issues before they affect your production users. And make sure you've got solid backups of everything before touching your production server.

The version compatibility requirements aren't negotiable, especially with NPrinting. Double-check those version numbers before you commit to an upgrade timeline. Finding out mid-upgrade that you need to also upgrade NPrinting can throw off your entire schedule.