---
title: "Migrating From a Tenant Instance to a Standalone Database"
slug: "migrating-from-a-tenant-instance-to-a-standalone-database"
tags: ["Multi-Tenant Setup", "Multi-Tenant ", "Multi-Tenancy ", "Installation", "V8"]
updated: 2025-06-30T16:23:59Z
published: 2025-06-30T16:23:59Z
canonical: "documentation.decisions.com/migrating-from-a-tenant-instance-to-a-standalone-database"
---

> ## 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.

# Migrating From a Tenant Instance to a Standalone Database

## Overview

**Multi-Tenancy** in v9 provides **Administrators** the flexibility and option to establish **Tenant** **Instances** from any desire locations. This may be completed by installing a new **Version 9** Installation [Tenant Instance from scratch](https://documentation.decisions.com/v9/docs/multi-tenancy-adding-and-setting-up-a-tenant-instance), or by migrating a [pre-existing standalone environment into a **Hosted** **Tenant** **Instance**](https://documentation.decisions.com/v9/docs/converting-a-standalone-database-into-a-multi-tenant-database). Conversely, Tenant Instances can be migrated back into standalone databases. This allows Administrators the ability to detach a database from a Multi-Tenancy as desired/needed. The following document demonstrates how to migrate a Tenant (Hosted) Database to a **Standalone** (**Unmanaged**) **Database**.

---

## Example

1. From the **Local** **File** **System** of the **Standalone** **Database** navigate to **C:\Program Files\Decisions\Decisions Server** and open **Settings.xml** in a **Text** **Editor**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-02-16_14h29_32.png)
2. From Settings.xml, change the value in between the **<ServerType/>** tags from "Hosted" to "Unmanaged". ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-02-16_15h15_26.png)
3. **Save** and close the Settings.xml.
4. Right-click **DecisionsServerInstaller.exe** and select **Run as administrator**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-02-16_14h35_44.png)
5. From the **Decisions** **Installer**, select RESTART SERVICE. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-30_11h17_14(2).png)
6. After the **Decisions** **Service** restarts, open and log into the **Decisions** **Studio**/**User** **Portal** for the respective database; verify that the **Hosting** **Folder** is no longer accessible via **System**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-08-07_10h21_21.png)

---

For more information regarding Multi-Tenancy, see [Decisions Forum: Multi-Tenant](https://support.decisions.com/forum/forum23-multitenant.aspx).