---
locale: "en"
updated_at: "2026-08-13T12:25:00.528Z"
canonical: "https://www.isdecisions.com/en/fileaudit/docs/guides/installation/migrate-fileaudit-server"
---

# Migrate FileAudit server to another machine

Migration steps to move FileAudit to a new machine.

## Introduction

You can only migrate FileAudit to a server running the **same or a newer Windows version**.

If your goal is to **upgrade FileAudit**, see [Upgrade procedure](/fileaudit/docs/guides/installation/upgrade-procedure) Guide instead.

Ensure you have the necessary permissions on both servers.

## Step1. Prepare the new server

Before you begin, keep the following requirements in mind:

- If FileAudit audits the server itself (it means local paths), you must use the **same machine name** for the new server. After completing the steps below, you will need to reconfigure the audit of all audited paths on the new server in the Windows paths view.
- If FileAudit does not audit the local server, the name of the new server does not matter.
- Make sure you use the **same installation path** for FileAudit on the new server.

## Step 2. Prepare the old server

1. Stop the **FileAudit service** on the old server.
2. If you are using the default SQLite database included with FileAudit, make a copy of the database file: `C:\ProgramData\ISDecisions\FileAudit\Database\FileAudit.db`
3. Make a copy of the configuration file: `C:\ProgramData\ISDecisions\FileAudit\Default.xml`
4. Make a copy of your scheduled report and scheduled operation task files: `C:\ProgramData\ISDecisions\Tasks\FileAudit task for [your scheduled report name].xml`
  and
  `C:\ProgramData\ISDecisions\Tasks\FileAudit[Maintenance | Cleannig | Archiving].xml`
5. In the **Microsoft Task Scheduler**, export each scheduled task related to FileAudit (they are named `FileAudit...`).
  > **⚠️ Important**
  >
  > Keep the original task name when exporting.

## Step 3. Install FileAudit on the new server

1. Run the FileAudit installer, using the **same installation path** as the old server. See [Installation](/fileaudit/docs/guides/installation/) Guide
2. Enter your **license key**. See [Manage the license](/fileaudit/docs/guides/configuration/manage-the-license) Guide
3. Stop the **FileAudit service** on the new server.

## Step 4. Transfer configuration and data

Transfer the configuration and data files from the old server to the new one, always preserving the original paths:

1. Copy the database file if you use SQLite database.
2. Copy the  `Default.xml` configuration file.
3. And finally copy your scheduled report and scheduled operation task files to their respective directories on the new server.
4. In the **Microsoft Task Scheduler**, import each scheduled task you exported earlier. Keep the original task name when importing.

## Step 5. Finalize configuration

1. Start the **FileAudit service** on the new server.
2. If you audit local paths on the new server, reconfigure them in the Windows paths view. See [Check an audited path's configuration](/fileaudit/docs/guides/operations/manage-windows-audit#check-an-audited-paths-configuration) Guide.
3. If using a custom database (not SQLite database), update the **Database** section in **Server Properties**. See [Define a production database](/fileaudit/docs/guides/database/set-production-database) Guide
4. If you audit cloud storage providers, restart the connection procedure See [Connect a cloud storage provider](/fileaudit/docs/guides/operations/manage-cloud-audit#connect-a-cloud-storage-provider) Guide.