LiquidFiles Documentation
LiquidFiles Documentation

Migrate from LiquidFiles v3.x to LiquidFiles v4.x

When migrating from LiquidFiles v3.x to LiquidFiles v4.x, we're changing the underlying operating system from CentOS 7 to Ubuntu 22.04 LTS. This means that it's not possible to do an in-place upgrade. In order to migrate from LiquidFiles v3.x to LiquidFiles v4.x, you will have to do a fresh install of LiquidFiles v4.x and migrate your data across.

Or alternatively, if you're using a physical server and wishes to use the same hardware, it is also possible to use the builtin backup and restore functionality to restore a LiquidFiles v3.7.x backup onto a LiquidFiles v4.x system. Please see this section for more information.

Also please note that migration is only possible from LiquidFiles v3.7.x. If you're currently using an older release, you will first need to update to LiquidFiles v3.7 and then migrate to LiquidFiles v4.x.

Overview of steps involved

The preferred method is that you install a new LiquidFiles system and migrate the data across. This is the safest migration method as it will give you an automatic fallback option. If the migration for whatever reason is not successful, you can just simply continue using the previous LiquidFiles v3.x system until you can retry the migration. Using this method, it's also easy to do a staged migration, you can try out the migration but still keep using the older v3.x system. Once you've verified that everything works as expected, you can repeat the migration and move the v4.x system into production.

The steps involved are:

Migration Guides:

  • Web Based Migration — This is the guide for most migrations.
  • Console Based Migration — A very similar alternative to the Web based migration, if you have access and prefer to use the console.
  • Installation First Migration — If you want your destination system to use a separate data disk or use NFS storage as data storage, you have to install the LiquidFiles system so you can configure the data storage options first, before running the migration.
    You can also use this if you've previously run another migration to test and then do the final migration using this method.
  • Restore From a Backup — If you're running LiquidFiles on dedicated hardware and want to continue using the same hardware, or if you cannot establish a network link between the source and destination system, follow this guide.

Web based migration

The simplest way is to use the web based migration. This migration will work best for most migrations. With this migration, you login to the console on the source system and run the command ft migrate and select the option to migration from this system. On a freshly installed LiquidFiles system, when you visit the Getting Started page, you select to Migrate from another system.

This will take you to a configuration page where you fill in the details and the migration function will connect to the source system and copy all the data from there.

Video Walkthrough — Web migration

Console based migration

If you have access to the console, i.e. you're running LiquidFiles in something like VMware, Hyper-V or any system where you have access to the console, that will look something like this:

From this console, on a freshly installed system (i.e. you haven't gone through the Getting Started function), you can hit F2 Setup, and select the migrate option:

Video Walkthrough — Console migration

Installation First migration

If you want to use a separate data disk or use an NFS server for data storage on the destination system, you will need to complete the Getting Started function to install the destination system so you can complete the data disk or NFS configuration before starting the migration. The most important thing to note is:

You cannot use a Trial/Demo license during installs when you want to migrate to a system.

If your source system has the following configuration:

  • Public Hostname:
  • License Code: 5ed230b1604e77a3fc6e4a59720400655285239c

You will need to use the same details on the destination system when installing the system.

You can also use this method if you want to do a staged migration where you've already migrated your system using another method to test the migration, and then finalize using this method.

Video Walkthrough — Installation First Migration

Restore a LiquidFiles v3.7 backup to LiquidFiles v4.x.

Please note that this is NOT the preferred method of migrating. The preferred method is to install a new LiquidFiles system and use one of the methods described above to migrate the data across.

The only reason to use this method is if you're running LiquidFiles on dedicated hardware, and you want to continue using the same hardware. Or if there's some reason where you cannot create a network link between the source and destination system.

If you haven't currently configured periodic backups, the procedure to migrate to LiquidFiles using the same system would be:

  • On the LiquidFiles v3.x system: Update to the latest v3.7.x version
  • On the Liquidfiles v3.x system: Configure backups in Admin → Backup
  • On the LiquidFiles v3.x system: Login to the console and run the command: ft backup to run the backup job immediately. Please make sure you don't receive any errors.
  • Install LiquidFiles v4.x using the latest version from
  • Use the same hostname as the LiquidFiles v3.x system and install the same production license.
  • Enable Console Access in Admin → System → Console Access.
  • Login to the console and run ft restore and follow the prompts.