--- title: "Upgrading Decisions from v7 or below" slug: "upgrading-decisions-v7-or-below" tags: ["installer", "Installation", "Decisions Installation ", "Version 8", "Upgrading "] updated: 2025-06-30T16:09:43Z published: 2025-06-30T16:09:43Z --- > ## 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 from v7 or below ## Overview Upgrading directly from version 7 (or older) directly to version 9 is **not supported**. Instead, upgrade to version 8 first and then upgrade to version 9. The rest of this article provides instructions for upgrading from**version 7** to **8******and upgrading **version 6** to **8**. If you are on a version lower than v6, please contact the Support team at [support@decisions.com](mailto:support@decisions.com) for assistance. --- ## Upgrading v7 to v8 ### Backing up the Previous Installation It is highly recommended to back up the v7 installation and its affiliated database before upgrading. While it cannot be used as a substitute for v8's Settings.xml, the v7 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\Decisions Server\Instances\Control**. 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 v7 **Settings.xml**file, copied above, to re-configure the exact path later in the **v8****Installer**. --- ### Downloads, Selecting Installation Type, and Database Setup 1. Fulfill all [v8 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 8 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. 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 v8 database. Click Next**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-01-06_12h16_001.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). 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 v7 task links resolve correctly, reference the v7 Settings.xml file to configure the matching values during the v8 installation. --- ### Email Server, Encryption Keys, and File Storage, 1. Select the**Outbound E-mail****Server**option previously used in **v7**, then click **Next**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-02-11_12h02_33.png) 2. If database encryption was used, click **Restore Key File**to upload the copied v7 **Keys.dat,**then click Next.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-02-11_12h03_21.png) 3. Define a new **v8****File****Storage**location or select the original one. Then, click Next.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-02-11_12h05_54.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 v7 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. --- ### 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 they 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. --- ## Upgrading from v6 to v8 ## Important Notes IMPORTANT CONSIDERATIONS - Changing to**.NET Core**architecture requires an "uninstall" of **v****6******before installing **v8**. - Running v6 and v8 on the same database is **NOT**supported. - Upon upgrading to v8, downgrading back to v6 is **NOT**supported. - Projects using XML/XSD Data Structures may require remapping on upgrade. - v6 custom **Less**files are not supported for use in v8. - v8 **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. - Label components that use HTML will break when upgrading due to changes included in DT-029205. To resolve this, use the [HTML Display component](https://documentation.decisions.com/docs/html-display-control#display-html-as-a-label). - [SSO endpoints were modified](https://documentation.decisions.com/docs/single-sign-saml?highlight=end%20certificate%20below#version-8-endpoints) between v6 and v8. While v6 endpoints still function, the recommended endpoints have changed. - Upgrading clustered environments requires deploying a **Redis**server for external caching. Refer to [Redis External Caching](https://documentation.decisions.com/docs/setting-up-redis-external-caching) for more information on deploying and configuring a Redis Server. - HTML Templates may need to be updated. - External Service References have been removed in v8; External Web References are utilized instead. Flows using these steps will need to be updated. - [Agents](https://documentation.decisions.com/docs/introduction-to-agents) will need to be reinstalled to be compatible with version 8. For more information, refer to [Agent Setup and Testing](https://documentation.decisions.com/docs/agent-setup-and-testing). If the Agent is used for Active Directory, you will not be able to log in with AD accounts until the Agent is reinstalled for version 8. Once the new Agent is created, edit [Active Directory settings](https://documentation.decisions.com/docs/system-settings-overview?highlight=Active%20Directory%20settings) and select the new Agent and save. - Single Sign-On with Active Directory is not supported in v8. - The HTML to PDF step will not create PDFs that have links that work due to a library change. The step will need to be deleted and replaced. - The ID system for identifying design elements changed from GUIDs to ULIDs. This may cause issues in places that reference GUIDs specifically. - As part of the change included for the [DT-035693](https://documentation.decisions.com/v99/docs/version-85x-release-notes), the storage location for LESS files will be moved. This will cause custom LESS files to be lost upon upgrading. It is recommended that users create a backup of any custom LESS files. - Changes that were made using the [Theme Editor](https://documentation.decisions.com/docs/theme-editor) will persist upon upgrading. - After upgrading from v6.14 and above to newer versions, Customers using special characters in [Flow Prefix](https://documentation.decisions.com/docs/creating-a-process-folder?highlight=Inserts%20a%20prefix%20before%20the%20numeric%20ID%20is%20generated.%20The%20Flow%20Prefix%20must%20be%20unique;%20using%20a%20duplicate%20Flow%20Prefix%20in%20a%20Flow%20will%20result%20in%20a%20validation%20error.) for the [Setup Process Folder](https://documentation.decisions.com/docs/creating-a-process-folder) might cause an error running the Flow. Contact [Support@decisions.com](mailto:Support@decisions.com) for prompt assistance. - The **v6 Settings.xm****l** file will be a reference point for various parameters while installing **v8** but cannot be used between versions. - v6 supported MySQL Connector version 8.0.18, but for v8.9, download and install the latest MySQL connector version 8.0.33, and the recommended .dll file to be used for the MySQL connector is from .NET 7.0. For more information, refer to [Connect to MySQL](https://documentation.decisions.com/docs/connect-to-mysql). - For upgrading v6 [**Multi-Tenancies**](https://documentation.decisions.com/v8/docs/about-multi-tenancy), refer to [Upgrading a v6 Mult-Tenancy to v8](https://documentation.decisions.com/v8/docs/upgrading-a-v6-multi-tenancy-to-v8). --- ### Installation Requirements Requirements (based off v8.22): [.NET 8.0](https://dotnet.microsoft.com/en-us/download/dotnet/8.0) SQL Server 2017 or newer The latest [ASP.NET Core Runtime 7.0.1 (x64)](https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-aspnetcore-7.0.1-windows-x64-installer) The latest [.NET Desktop Runtime 7.0.1 (x64)](https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-desktop-7.0.1-windows-x64-installer) The latest [ASP.NET Core Runtime 7.0.1 (Hosting Bundle)](https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-aspnetcore-7.0.1-windows-hosting-bundle-installer) --- ### Pre Installation Backups 1. **Back up**the **Database (DB)****,**noting the **DB****Server**and **DB****name**(or **connection****string**). 2. Navigate to **C:\Program Files\Decisions\Decisions Service Manager**. 3. Copy and paste the **Settings.xml**file to the Desktop. 4. Navigate to **C:\Program Files\Decisions\Decisions Service Manager\Instances\Control**. Copy and paste the **Keys.dat**and **databaseid****.txt**file to the Desktop for future reference.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-07-12_14h32_47.png) 5. Navigate to and backup **C:\Program Files\Decisions\FileStorage. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-07-12_14h30_26.png)** Then reference the v6 **Settings.xml**file, copied above, to re-configure the exact path later in the **v8****Installer**. --- ### Version 6 Removal 1. Delete all the logs related to the SSO (SAML/OpenID) located at `C:\Program Files\Decisions\Decisions Services Manager\Logs\{SSO Folder}`. 2. Visit [Download Decisions](https://releases.decisions.com/Releases/); select the **Decisions 6 Installer**that matches the current version (ex:**6.10.0**) 3. Run **DecisionsServerInstaller.exe**. Then, click REMOVE. 4. After Uninstalling all the instances. Open **Services.exe** and confirm that the **Service Host Manager** is successfully removed. --- ### Version 8 Downloads, Select Installation Type, and Database Setup After removing v6: 1. **Download**and install [.NET 6 Runtime (x64)](https://dotnet.microsoft.com/en-us/download/dotnet/6.0), [.NET Core Hosting Bundle](https://dotnet.microsoft.com/en-us/download/dotnet/6.0/runtime) and [.NET Desktop Runtime](https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-desktop-6.0.8-windows-x64-installer). 2. Download the desired **Decisions 8 Installer** from the [Download Decisions](https://releases.decisions.com/Releases/) webpage. 3. Right-click the newly downloaded installer and select **Run as administrator**. 4. Click INSTALL. 5. Review the terms, check the **I accept the terms of the License Agreement**box, then click **Next**to proceed. 6. On the **Select Installation Type**window, choose the appropriate server type, then click Next.Additional OptionsTo further customize all installation options, check the **Show Advanced Settings** box.  ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1649104143564.png) 7. Upon reaching the **Settings** screen, click Next. On the resulting **Database Setup** screen, select the appropriate **Database****Type**, match the **Connection Type** and **Connection Settings** used for v6, then click Next**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-01-06_12h16_00.png)** 8. If upgrading the 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/docs/setting-up-redis-external-caching). ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1684317698469.png) 9. Select the appropriate [**Installer Hosting Option**](https://documentation.decisions.com/docs/installer-hosting-options), then click Next. Typically the recommended option is **Self Hosting**.  ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1609784464219(2).png) --- ### Portal Base URL The following section demonstrates how to set up the **Portal Base URL** for the Decisions environment for both [**Hosting Options**](https://documentation.decisions.com/docs/installer-hosting-options). Matching PortalBaseURLTo ensure previously emailed **v6**task links resolve correctly, reference the **v6****Settings.xml** file to configure matching values for the **v8**installation.  #### Self Hosting 1. By default, v6 was installed on IIS, which was using port 80. However, to install Decisions on this port, users must first release it from IIS. Refer to the following steps. - Navigate to Windows Services > World Wide Web Publishing Service > Properties. - Set **Startup Type** to Manual - Set **Service Status** to Stop - Click on **Apply** and OK. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1679917196974.png) 2. Specify the **Portal****Base****URL**used in v6 within the **Domain****Name** (ex: example.com) field. 3. Select the desired **HTTP**/**HTTPS**configuration, along with the **Certificate**path and **Password**if applicable, then click **Next**.Default Port Values and Certificate Note that Local installations default to [](http://localhost/decisions,)[localhost](http://localhost:80) with **HTTP**(Port: 80) or **HTTPS**(Port: 443). **Certificates**may be selected via **Physical****File****Path**or **Certificate****Store**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-01-06_14h47_52.png) ### IIS Hosting The following section details setting up Decisions via IIS Hosting using the **Default Web Site**. Manual Setup Instructions To manually configure the **Application****Pool**and **Application****Initialization**settings, refer to [Prerequisite for IIS Hosting](https://documentation.decisions.com/docs/prerequisite-for-iis-hosting). 1. Provide the **Portal****Base****URL**used in **v6**, then click **Next**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-01-15-1709-07-IISb(2).png) 2. From the **Web****Application**window, under **Application****Pool**, click **Create****new**. Then, click Next. Preexisting App PoolIf an **Application****Pool**with the same name already exists, use **IIS****Manager**to change the **.NET CLR** version **No****Managed****Code**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-01-15-1709-07-2-IIS(2).png) --- ### Finish Installation 1. Select the**Outbound E-mail****Server**option previously used in **v6**, then click **Next**. 2. If database encryption was previously used, click **Restore Key File**to upload the copied v6 **Keys.dat,**then click Next. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-07-12_13h36_14.png) 3. Define the **v8****File****Storage**location, then click Next.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-07-12_13h41_16.png) 4. Review and correct any System Requirements warnings before clicking **Next.** 5. Via the **Review Install Options** screen, confirm the expected installation summary details, then click **Next.**![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-01-06_15h26_18.png) 6. Installation of v8 is underway. 7. Click **Show Details** to see the installation progress. 8. When the upgrade completes, click **Finish**to close the **Installation Finished** window. 9. Attempt to login into the new upgrade Decisions environment using the admin **Username**and **Password.** --- ### Post Installation Process #### System Validations Users might face System Validations when they log in to decisions after upgrading successfully. Refer to the following Post Installation Process to resolve the system validation.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1673609481874.png) **Validation: Database "database_ID" was moved from another system. Jobs and background work will be suspended by disabling Job Server capability on this server. Please check system validations and clear this issue.** When Decisions is installed using a database backup file, it fetches the **databaseid.txt** file at a specific location. If the file is not present, users may encounter a validation message that prevents the Decisions server from being used as a Job Server. Refer to the following points to resolve this Validation. 1. Paste the already copied **databaseid.txt** file at the following location, `C:\Program Files\Decisions\FileStorage\Primary\Settings`. 2. If somehow the **databaseid.txt** file is misplaced. Run the query in the database, `select * from platform_version`, copy the value from `dbsettings_id` and paste it within **databaseid.txt** and place the file at the above-mentioned location. 3. Login to the Decisions Server. Navigate to **System Validation > Select the validation message > Resolve**. This will resolve the issue and clear the validation message from the server. 4. Navigate to **System > Administration > Servers**. Right-click on the **Server Name > Edit Server**. Enable **Can be a Job Server**. 5. [Restart](https://documentation.decisions.com/docs/restart-decisions-application) the Decisions service. --- ### Setting Inbound Rule to Port 80/443 To access the server from an external machine, admin users must open ports 80 and 443 and configure them for inbound traffic. One can configure this Rule in the [Windows Firewall settings](https://learn.microsoft.com/en-us/windows/security/threat-protection/windows-firewall/create-an-inbound-port-rule) on the server or can execute the following PowerShell script by running it as administrator. ```shell New-NetFirewallRule -DisplayName 'Decisions' -Profile 'ANY' -Direction Inbound -Action Allow -Protocol TCP -LocalPort 80, 443 ``` After applying the inbound rules, ensure that you can hit the URL from an external machine. If unable to access the server, contact [support@decisions.com](mailto:support@decisions.com). --- ### Objects with allow_restapicalls Property Any objects with the allow_restapicalls property (Flows, Rules, and Reports) will be marked as modified following the upgrade to v8. This has to do with an API layer, but otherwise will not change the objects and they will continue to work normally after the upgrade. --- ## For further information on Installation, visit the [Decisions Forum](https://community.decisions.com/categories/InstallationSetup).