This article explains the recommended method for installing multiple versions of Spire Server using virtual machines (VMs). This approach avoids database conflicts caused by PostgreSQL incompatibilities across different versions and changes made to the Spire database which contains the Accounts and Integrations tables.


Why Use Virtual Machines?

It was never advisable to install previous version of Spire Server without uninstalling Spire Server and deleting C:\ProgramData\Spire\PostgreSQL (called a Spire tear down). After installing Spire version 3.13, it is no longer even possible to install version 3.12 or earlier over a database already accessed by a Spire 3.13 or later. Using virtual machines ensures each Spire Server version runs in a clean environment, preventing compatibility issues.


Recommended VM Setup Method

Spire recommends using Hyper-V for creating and managing virtual machines on Windows. For step-by-step instructions on setting up and managing VMs, please refer to the following Spire Academy course:



This course covers essential topics including creating virtual machines, configuring resources, and installing operating systems.


Installing Spire Server on Your VM

Once you've created your VM environment:

  1. Transfer the installation files for the desired Spire Server version to the VM.

  2. Install Spire Server within the VM, ensuring that each version runs on its own separate VM.


Best Practices for Managing Multiple Versions

  • Clearly label each VM with the corresponding Spire Server version (e.g., "Spire Server 3.12").

  • Regularly back up VMs to prevent data loss.

  • Allocate sufficient system resources to ensure optimal performance.


For further assistance, see the related article:
Installing Multiple Versions of Spire Desktop