Upgrading from v4/v5 to v6

Upgrading from an old Syncplify.me Server! v4 or v5 to Syncplify Server! v6 is a process that requires careful planning. The purpose of this article is to help the system administrator minimize this task's complexity.

Before you begin, make sure to execute these twoi preparatory steps:

  1. Upgrade to the latest release of your current v4/v5 version
  2. Take a backup of your old V4 or V5

Once you have performed the two preparatory steps, and you have the backup file from your old installation ready at hand, please make sure you read these few short observations and recommendations, they will save you a lot of headaches in the future:

For these reasons we do not recommend in-place upgrades, what we recommend instead is to perform a migration-upgrade. Please, read below for more details.

Performing a migration-upgrade is as simple as:

The video here below shows just how quick and easy it is:

Important note for existing V4/V5 license holders: every new major version, traditionally, uses a new license code type, so if you own a v4/v5 license it won't work with v6. But if you do have an active maintenance/support subscription, you can simply request a free v6 upgraded license code by submitting a ticket here.

But what if, in spite of the best-practices and recommendations here above, you still wish to perform an in-place upgrade?

In-place upgrades are certainly possible, though not highly recommended. Here's the key points to keep in mind in order to successfully perform an in-place upgrade:

image.png

Final steps

As with all major version upgrades, upgrading to V6 provides an opportunity to review your entire configuration to enhance your security posture. We highly recommend taking advantage of this opportunity. If your previous version (the one you're upgrading from) was configured to use algorithms that are now considered weak, note that V6 may still support some of these algorithms for backward compatibility with legacy systems. After completing the upgrade, you may want to manually disable these weaker algorithms to ensure optimal security.


Revision #21
Created 3 February 2023 18:01:59 by DevTeam
Updated 7 April 2025 10:18:38 by DevTeam