How to update inFlow On-Premise to a newer version?

Please note: we will sunset inFlow On-Premise on July 31, 2024. After sunset we will stop selling or activating new licenses for inFlow On-Premise and stop providing support (including online KB articles).

In the meantime we will still provide technical support to customers with an active Support Plan.

Thinking of updating your inFlow On-Premise to the latest version? Great, there are some things you should know before starting the process.

First, it’s highly recommended to create a couple of backup files of your current database. Instructions can be found here.

Next, please be aware that your databases can be restored to newer versions of inFlow, but they can’t be restored to older versions of inFlow. (for example, you can restore a v3.5.2 database to v3.6.1, but you cannot restore a v3.6.1 database to a v3.5.2 version)

There are two ways you can update to a newer version of inFlow On-Premise:

  1. Run the installer overtop of an existing downloaded inFlow on-premise (this will start the update)
  2. Create a backup file, uninstall your current version of inFlow, re-install using the newest version of inFlow On-Premise

Of the two options, number 1 will most likely be quicker and requires less setup (it’ll use pre-existing settings).

Updating inFlow On-Premise from any v3 version to v3.6.1

Downloading the update to inFlow 3.6.1

  1. Go to and log into your account.
  2. On the right-hand side of the page, look for the Download section. Click on Online Installer to start the download
  3. Follow the installation steps.

If you’d like to choose your settings, please select the Server and Client option during the installation.

If you decided to use option 2, you’ll have a few additional steps to follow:

  1. If you haven’t already logged in, go to Main Menu>Options>About inFlow>Login. (this will apply your licenses to your account)
  2. Restore your data, Main Menu>General>Restore Data (only needed when installing a fresh copy)

If you have multiple computers connected to inFlow, you will need to update them so they can connect to the updated server PC. Please follow these instructions How do I set up multi-user mode for multiple computers to connect together?

Updating inFlow On-Premise from v2 version to v3.6.1

It is highly recommended to create backups before updating inFlow

When updating inFlow On-Premise, it needs to convert the database to the new version, but prior to v2.5.1 the program the data conversion gap is too big for the program to just update to the newest version and crashes. Instead, it’s needed to get the version to a minimum of v2.5.1 before the jump to v3.6.1 can be made.

Contact the inFlow team if you’re having any trouble using your inFlow account with inFlow 3.6.1.

Updating versions prior to v2.5.1 (server computer)

  1. Download inFlow v2.5.1 from here.
  2. Run the installation file, and the update should begin.
  3. Next, create an inFlow v2.5.1 backup file. Go to Main Menu>General>Backup data. Save this file on your PC. Please repeat to ensure you have an adequate amount of backup files.
  4. Follow the instructions above to “download the update to v3.6.1” (please note it may take longer to restore/update because extra time is needed to convert your version 2 information)

Note: Customers using VPN and/or have remote SQL servers, we don’t support the use of these applications, but would like to offer a few helpful warnings.

  • Please make lots of backups (especially for customized databases)
  • You may have to re-do your 3rd party setup/settings (for your VPN, and possibly for customized databases if certain tables change)

How about New Features?

As of July 31, 2024, inFlow On-Premise will be sunset. You can get in touch with the inFlow team to learn more about switching to inFlow Cloud for your inventory needs. 

Kerisha Caines
Archon Systems
260 Carlaw Ave #397
Toronto, ON, M4M 3L1
July 27, 2023

Rate this article

This article has been rated 5.00 out of 5 (1 votes)
1 star2 stars3 stars4 stars5 stars
  • Did this article help? If not, please let us know so we can improve it.

  • This field is for validation purposes and should be left unchanged.