> For the complete documentation index, see [llms.txt](https://docs.staffwatch.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.staffwatch.app/migration-guide.md).

# Migration Guide

{% hint style="warning" %}
The legacy website has been shut down as of 6/1/2026. You may still be able to migrate your data using the steps below if you have a copy of one of your server's secrets. If you require additional assistance, you can email <support@staffwatch.app> or create a ticket in Discord and we do our best to help you.
{% endhint %}

### What happens when I migrate?

During migration, the following data will be migrated:

* Your Subscription (Basic, Premium, Pro)\
  **Note: that you will need to manually resubscribe after 30 days as we have changed our payment system from Stripe to Paddle.**
* Player Data (names, playtime, first played, last played, etc)
* Player Identifiers (steam, license, discord, etc)
* Actions (commendations, warnings, kicks, and bans)

The following data will **NOT** be migrated:

* Community Settings
* Server Details
* Role Permissions
* Staff Members
* Panel Logs

### 1. Register an Account on the Beta Site

Navigate to the [registration page](https://panel.staffwatch.app/register). You may choose a different email, username, and password if you would like. This will not affect your ability to migrate your community.

<figure><img src="/files/PTfMb3vIVapOhEadlBuo" alt=""><figcaption></figcaption></figure>

### 2. Login to Your New Account

[Login](https://panel.staffwatch.app/login) to the beta. A verification email will be sent to your inbox.

<figure><img src="/files/9tcWiWzFhJdO8yz6vAIB" alt=""><figcaption></figcaption></figure>

### 3. Navigate to the Communities Page

Open the community switcher on the top-left of the page, and click the button labeled *Create Community*. This will bring you to the [communities](https://panel.staffwatch.app/communities) page.

<figure><img src="/files/UC4KGNtDtun9RIfDb3Uc" alt=""><figcaption></figcaption></figure>

### 4. Create a community

Create a new community, you can use the same name as your existing community or choose a new one. This will not affect your ability to migrate.

<figure><img src="/files/QqgYsfgnRtQAIo3u019H" alt=""><figcaption></figcaption></figure>

### 5. Switch to your New Community

Open the community switcher, select your newly created community.

<figure><img src="/files/Be3Xe7AHxZqoVrCjoH2u" alt=""><figcaption></figcaption></figure>

### 6. Retrieve an Server Secret

To prove that you are the owner of the server, you will need to provide the *secret* from one of your servers. Login to [the old site](https://staffwatch.app/servers) and copy the *Server Secret* for any of your servers. **Note: It does not matter what server you choose, player data will be migrated from all servers in your community.**

<figure><img src="/files/uJ96PfH4gtE10RG33R5F" alt=""><figcaption></figcaption></figure>

### 6. Start the Migration

To begin the migration process, navigate to the *Manage Community* page on the beta site, enter the *Server Secret* from the old system, and click the start button.

<figure><img src="/files/ModW6rtL8QnJpRnZIym3" alt=""><figcaption></figcaption></figure>

### 7. The Migration is Complete! 🥳

After the migration process is complete (which **may take up to 30 minutes** depending on the size of your community), all of your player data should be available. The migrated data should include player names, identifiers, playtime, first/last played dates, and any recorded staff actions.

<figure><img src="/files/XVfWTKzjh7JFJJ0HVK9k" alt=""><figcaption></figcaption></figure>

### 8. Setup your StaffWatch Community

As mentioned at the beginning of this article, only player data is migrated. You will still need to re-configure your community settings, servers, staff members, rules, etc. Additionally you will need to reinstall the [in-game resource](broken://pages/8WY17rH9D6IiwXdrIVl0) and reconfigure the Discord bot.