How to Migrate Your Plex Server to a New Machine

Published September 1, 2026 · 10 min read

Hardware upgrades happen. Maybe your current Plex server is underpowered, running out of storage, or you are moving from a desktop to a dedicated NAS. Whatever the reason, migrating Plex to a new machine is straightforward if you follow the right steps. Done correctly, your new server picks up exactly where the old one left off: same libraries, same watch history, same user accounts, same everything. Done incorrectly, you lose years of metadata and watched statuses.

This guide walks through the complete migration process, from pre-migration planning to post-migration verification.

Pre-Migration Checklist

Before touching anything, gather this information and confirm these prerequisites:

• Document your current library paths. Open Plex Web, go to each library's settings, and note the exact folder paths. You will need to update these if the paths are different on the new machine.
• Note your current Plex version. Install the same version or newer on the new machine. Restoring a database from a newer version into an older one can cause problems.
• Verify your Plex account credentials. You will need to sign in on the new machine to claim the server.
• Plan your media file transfer. If media files are on the same drive as the server (not a separate NAS or network share), you need to transfer them to the new machine too. For large libraries, this can take hours or days over the network.
• Check the new machine's OS compatibility. If migrating between operating systems (for example, Windows to Linux), the process works but file paths will be different and require updating.

Step 1 — Back Up the Old Server

A proper backup is the safety net for the entire migration. If anything goes wrong, you can restore the old server to its original state. See our detailed Plex backup guide for the full process. Here is the abbreviated version:

1. Stop Plex Media Server on the old machine.
2. Copy the entire Plex data directory. This includes the database, preferences, metadata, and plugin data. The location varies by platform:
   • Windows: %LOCALAPPDATA%\Plex Media Server\
   • macOS: ~/Library/Application Support/Plex Media Server/
   • Linux: /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/
   • Synology: /volume1/PlexMediaServer/AppData/Plex Media Server/
3. Store the backup safely. Copy it to an external drive, a network share, or cloud storage. Do not rely solely on the old machine's drive.

The data directory can be large (10 GB to 50 GB or more for libraries with extensive metadata). If you want to save time and space, the absolute minimum you need is the Plug-in Support/Databases/ folder and Preferences.xml. However, copying the full directory preserves custom posters, cached artwork, and plugin configurations.

Step 2 — Install Plex on the New Machine

1. Download the latest Plex Media Server from plex.tv/media-server-downloads for your new machine's operating system.
2. Install it following the normal installation process. On Linux, use the package manager; on macOS, drag to Applications; on Windows, run the installer.
3. Start Plex once to let it create the default data directory structure. This generates empty database files and default configuration that you will replace in the next step.
4. Stop Plex immediately. Do not run the setup wizard. Do not claim the server. Just confirm it starts, then shut it down.

Step 3 — Copy the Data Directory

This is the core of the migration. You are replacing the fresh data directory on the new machine with the backed-up data from the old machine.

1. Make sure Plex is stopped on the new machine.
2. Delete or rename the default data directory that Plex just created on the new machine.
3. Copy the backed-up data directory from the old machine into the same location on the new machine. The folder name must be "Plex Media Server" and it must be in the correct parent directory for your OS.
4. Verify file permissions. On Linux, the Plex user (usually plex) must own the data directory. Run sudo chown -R plex:plex /var/lib/plexmediaserver/ to fix ownership. On macOS, permissions usually transfer correctly if you are using the same user account.

Cross-Platform Migration

If you are moving between operating systems (for example, Windows to Linux), the database and preferences files are platform-independent. Copy them the same way. The main complication is file paths, which you will update in the next step.

Step 4 — Update Library Paths

If your media files are in different locations on the new machine (different drive letters, different mount points, different directory structure), you need to update every library's folder paths.

1. Start Plex on the new machine.
2. Open the Plex Web interface at localhost:32400/web.
3. Go to Settings, then Manage Libraries.
4. For each library, click "Edit" and update the folder path to the new location on the new machine.

For example, if your movies were at D:\Movies on Windows and are now at /mnt/media/movies on Linux, update each library path accordingly. Plex will verify the new path is accessible and contains media files.

If your media files are on a NAS or network share that both machines can access, and the mount path is the same on both machines, you may not need to change anything. This is one of the advantages of storing media on network-attached storage rather than local drives.

Step 5 — Re-Claim the Server

This step is critical and is where many migrations go wrong. Your Plex server is tied to your Plex account through a "claim" process. The old machine's server was claimed by your account. The new machine needs to be claimed too.

If the Data Directory Includes Preferences.xml

If you copied the full data directory including Preferences.xml, the server should recognize your account automatically. Open the Plex Web interface and check if it shows your libraries and your account name. If it does, you are claimed and can skip ahead.

If You Need to Re-Claim

If the server appears unclaimed (you see the setup wizard instead of your libraries), you need to claim it. Sign in with your Plex account at plex.tv/claim to get a claim token. Alternatively, access the Plex Web interface on the new machine's local network (localhost:32400/web) and sign in there. Plex will prompt you to claim the server.

If you are accessing the new server remotely (not on the local network), you may need to set up an SSH tunnel to reach localhost:32400 on the new machine. Claiming only works when accessed from the local network or localhost.

Step 6 — Verify Remote Access

Remote access settings from the old machine may not carry over cleanly, especially if the new machine has a different local IP address or is behind a different router.

1. Go to Settings, then Remote Access.
2. Check if the green checkmark appears. If it does, remote access is working.
3. If you see a red indicator, click "Retry." Plex will attempt to configure UPnP on your router.
4. If automatic configuration fails, manually forward port 32400 on your router to the new machine's local IP address. See our remote access guide for details.

Test remote access by connecting from a client on a different network (for example, your phone on cellular data) to confirm everything works end-to-end.

Step 7 — Verify Everything Works

Run through this checklist after migration:

• Libraries load correctly. All your libraries should appear in the sidebar with their content intact.
• Watch history is preserved. Check a few titles and confirm that previously watched items show as watched (with the orange progress indicator or checkmark).
• Playlists and collections exist. Open your playlists and collections to verify they transferred.
• User accounts work. If you have managed users or shared users, verify they can connect and see their appropriate libraries.
• Metadata and posters are correct. Spot-check a few titles to ensure posters, descriptions, and ratings are present. If you skipped the Metadata folder during backup, you may need to run a metadata refresh.
• Remote access works. Test from an external network.
• Hardware transcoding works (if applicable). If your new machine has a different GPU or CPU, verify that hardware-accelerated transcoding is configured and functional under Settings, then Transcoder.

Common Pitfalls

Claiming fails because old server is still running. If the old Plex server is still running and claimed, the new server may conflict. Stop (or ideally uninstall) Plex on the old machine before claiming the new one. A Plex account can have multiple servers, but if both are claiming the same server identity, things get confused.

File permission errors on Linux. The most common Linux migration issue. The copied files are owned by your user account or root, but Plex runs as the plex system user. Always run chown -R plex:plex on the data directory after copying.

Database version mismatch. If the old server was running a much newer version of Plex than what you installed on the new machine, the database may not be compatible. Always install the same version or newer on the new machine.

Forgetting to update library paths. If paths are wrong, Plex shows empty libraries. It does not delete your metadata; it just cannot find the media files. Update the paths, and everything reappears.

Loss of custom DNS or reverse proxy configuration. If you access Plex through a custom domain with Nginx or Caddy, you need to update the proxy configuration to point to the new machine's IP address. This is outside of Plex itself but easy to forget.

Synology-to-Linux or vice versa. NAS platforms sometimes store the Plex data directory in non-standard locations. Double-check the source and destination paths for your specific platforms.

After Migration: Decommissioning the Old Server

Once you have verified everything works on the new machine, you can safely decommission the old one:

1. Stop Plex on the old machine.
2. Uninstall Plex Media Server.
3. Keep the old data directory backup for at least a few weeks in case you discover a migration issue after the fact.
4. If you kept media files on the old machine's local drives, make sure they have been fully transferred to the new machine or NAS before wiping the old drives.