---
locale: "en"
updated_at: "2026-08-10T09:20:49.757Z"
canonical: "https://www.isdecisions.com/en/fileaudit/docs/guides/database/migrate-to-another-database"
---

# Migrate to another database

Copy all auditing data to a new database and make it the production database.

## Before you begin

Migrating **copies all data** from your current production database to another database. Once the copy completes, the new database becomes the production database and FileAudit continues auditing against it.

Use this guide when you change databases and want to keep your existing records. To switch the production database **without copying** any data, use [Set production database](/fileaudit/docs/guides/database/set-production-database) instead.

Before you start, make sure you have:

- The connection details for the destination database (server, instance, and credentials, depending on the provider).
- Network access to the destination database from the FileAudit service.

## Migrate to a new database

1. On the main screen, click the **Database & audit maintenance** tile. On the **Database manager** tab, click **Migrate**.
2. Click the three dots (`...`) at the end of the **Connection string** field to open the **Database connection** window.
  ![Archiving the database](https://a.storyblok.com/f/122374/1074x748/2fe761ac4c/archiving-database.png)
3. Select your destination database connector (such as SQL Server, ODBC Wizard, OLEDB Wizard, or SQLite) and click **OK**. A window opens for you to enter the connection details for that connector.
  ![Migrate database Properties](https://a.storyblok.com/f/122374/1140x616/62b09c5fa1/migrate-database-properties.png)
4. Fill in the connection details and confirm.
5. Back in the Migrate database dialog, the **Connection string** field updates. Click **Next**.
  ![Migrate database success](https://a.storyblok.com/f/122374/1015x594/d9923af218/migrate-database-success.png)
6. Click **Migrate**.

> **Note**
>
> ⚠️** Important**
> Migration can take a while when the production database holds a large volume of events. Let it finish: do not close FileAudit or interrupt the service while the migration is running.

## Confirm the data was migrated

The new database should contain all the events from your previous database, not just events recorded after the switch. To confirm:

1. Check that the production database has been updated to the migrated one.
2. Open a report covering a date range from **before** the migration.
3. Check that the events from that period appear. See [Displaying the events](/fileaudit/docs/getting-started/displaying-the-events) Getting started.

If your older events show up, the migration copied your data successfully.