--- title: "Upgrading Decisions (v8 to v9)" slug: "upgrading-decisions-v8-to-v9" updated: 2026-02-12T21:09:31Z published: 2026-02-12T21:09:31Z --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt > Use this file to discover all available pages before exploring further. # Upgrading Decisions (v8 to v9) IMPORTANT CONSIDERATIONS - Running v8 and v9 simultaneously from the same database is **NOT**supported. A v8 database can be upgraded to v9. A fresh database is not needed. - Upgrading directly from v7 or below to v9 is **NOT**supported. Upgrade to v8 first before upgrading to v9. Refer to this [article for more information](https://documentation.decisions.com/v9/docs/upgrading-decisions-v7-or-below). - After upgrading to v9, downgrading is **NOT**supported. - v9 **Web Service Integrations** requires the installation of the [.NET Core 6.0 SDK](https://dotnet.microsoft.com/en-us/download/dotnet/6.0/runtime) and a machine restart for proper configuration. - Upgrading clustered environments requires deploying a Redis server for external caching. Refer to [Redis External Caching](https://documentation.decisions.com/v9/docs/setting-up-redis-external-caching) for more information on deploying and configuring a Redis Server. - Before beginning an upgrade that involves moving or converting Projects, review [Legacy Projects and Upgrading to v9](https://documentation.decisions.com/docs/legacy-upgrades-v9) to understand upgrade order and ProjectHub conversion considerations. ## Overview The following article provides instructions for upgrading from**Version 8** to **9******and troubleshooting potential upgrading issues. --- ## Upgrading Multiple Servers It is recommended to update servers in the following order: - Development Server - Repository and Test - Production Once Development has been upgraded, Projects cannot be deployed to Repository or Test servers until those servers have been upgraded. It is possible to upgrade Development, Repository, and Test at the same time. Deploying to Production is also blocked until it has been upgraded. --- ## Backing up the Previous Installation It is highly recommended to back up the v8 installation and its affiliated database before upgrading. While it cannot be used as a substitute for v9's Settings.xml, the v8 Settings.xml is a valuable reference to ensure the necessary variable match when upgrading. 1. **Back up**the [**Database**](https://documentation.decisions.com/v9/docs/backup-of-decisions-database-and-file-system) noting the **DB****Server**and **DB****name**(or **C****onnection S****tring**). 2. Navigate to **C:\Program Files\Decisions\Decisions Server**, and copy and paste the Settings.xml file into the desired location. 3. Navigate to **C:\Program Files\Decisions\FileStorage\Primary\Settings.** 4. Copy and paste the **Keys.dat**file to the desired location. 5. Navigate to **C:\Program Files\Decisions\FileStorage.** 6. Back up the **FileStorage**Folder and reference the v8 **Settings.xml**file, copied above, to re-configure the exact path later in the **v9****Installer**. --- ## Downloads, Selecting Installation Type, and Database Setup 1. Fulfill all [v9 Prerequisites](https://documentation.decisions.com/v9/docs/installation-guide#:~:text=Postgres%2C%20are%20detailed.-,Prerequisites,-Download%20and%20install) before beginning installation. 2. Download the **Decisions 9 Installer** from [Download Decisions](https://releases.decisions.com/Releases/) webpage. 3. Right-click the installer, then select **Run as Administrator**. 4. From the Decisions Installer, enable **Change Settings on Update,** then click UPDATE. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-30_11h50_32(2).png) 5. Review the terms, check the **I accept the terms of the License Agreement**box, and then click **Next**to proceed. 6. For the installation type, select the desired server type. This example chooses a Standard server. Select Next to continue. 7. Upon reaching the **Settings** screen, click Next. 8. On the **Database Setup** screen, select the appropriate **Database****Type**, and match the **Connection Type** and **Connection Settings** for the new v9 database. Click Next**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-30_12h01_18.png)** 9. If upgrading a clustered environment, the installer will prompt users to enter the Redis Base URL. Enter the Redis Base URL for the clustered environment. For more information, refer to [Setting Up Redis External Caching](https://documentation.decisions.com/v9/docs/setting-up-redis-external-caching). ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-30_12h03_07.png) 10. Continue past the **Full-Text Warning** screen. --- ## Portal Base URL Set up the Portal Base URL based on the chosen [Hosting Option](https://documentation.decisions.com/v9/docs/installation-guide#:~:text=Hosting.%20Click%20Next.-,Self%20Hosting%C2%A0,-In%20the%20Portal). It is recommended to maintain the same URL in the prior version if possible. To ensure previously emailed v8 task links resolve correctly, reference the v8 Settings.xml file to configure the matching values during the v9 installation. --- ## Email Server, Encryption Keys, and File Storage 1. Select the**Outbound E-mail****Server**option previously used in **v8**, then click **Next**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-30_12h05_01.png) 2. If database encryption was used, click **Restore Key File**to upload the copied v8 **Keys.dat,**then click Next.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-30_12h06_10.png) 3. Define a new **v9****File****Storage**location or select the original one. Then, click Next.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-30_12h07_44.png) 4. This ends any upgrade-specific changes from the standard installation. Proceed with the installation as detailed in the [Installation Guide](https://documentation.decisions.com/v9/docs/installation-guide#:~:text=Review%20any%20warnings%20in%20the%20System%20Requirements%20Check%20before%20clicking%20Next%C2%A0to%20proceed.). --- ## Manually edited .less Conflicts Direct edits to the custom .less files made outside the [Theme Editor](/v9/docs/theme-editor) may cause errors in the Portal UI. Upgrading from v8 automatically overrides the .less files, but a conflict file is generated once this error occurs. The conflict file contains the old .less file's information. To resolve this issue: 1. Open the provided conflict file named e.g. "theme.portal.less.conflict" found in the same folder as the .less files. 2. Open the .less file associated with the conflict file. Matching the example above, this would be the "theme.portal.less" file. 3. Replace each changed value in the .less file with the value shown in the conflict file. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1653495996933.png) 4. Restart the Decisions server to apply changes.