Migrate Your Plex Server to New Hardware

Published 2026-10-16 · PlexBeam

Moving a Plex server to new hardware does not mean starting over. With a proper migration, you transfer your entire library — metadata, watch history, collections, user accounts, and settings — to the new machine. Users notice nothing except better performance. This guide covers the complete migration process.

What Transfers

Everything stored in the Plex application data directory transfers to the new server:

  • Library database: All metadata, match information, collections, playlists, and ratings.
  • Watch history: Every user's watched status and playback positions.
  • User accounts: Managed users, sharing settings, and permissions.
  • Server configuration: Transcoder settings, library paths, network settings, remote access configuration.
  • Custom plugins: HAMA, Audnexus, and other installed agents.
  • Custom scanners: Absolute Series Scanner and similar.

Pre-Migration Checklist

  1. Note your current library paths. Write down the full path to each library root on the old server. You will need these to configure the new server.
  2. Back up the Plex database. Run a fresh backup from Settings then Manage then Troubleshooting then Back Up Database.
  3. Record your Plex token. Find it in Preferences.xml — the value of the PlexOnlineToken attribute. You may need this for re-claiming the server.
  4. Note your Plex version. Install the same version on the new server first to avoid database upgrade issues during migration.

Migration Steps

Step 1: Stop Plex on the Old Server

Shut down Plex Media Server completely. On Linux: sudo systemctl stop plexmediaserver. On Windows: stop the Plex service. This ensures the database is in a consistent state for copying.

Step 2: Copy the Application Data Directory

Copy the entire Plex Media Server application data directory to the new server:

  • Windows: %LOCALAPPDATA%\Plex Media Server\
  • Linux: /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/
  • macOS: ~/Library/Application Support/Plex Media Server/

This directory contains the database, plug-ins, cache, and configuration. Copy everything. Use rsync, robocopy, or a similar tool that preserves permissions and handles large directories reliably.

Step 3: Transfer Media Files

Move or copy your media files to the new server. Options:

  • Same NAS: If media is on a NAS that both servers can access, no media transfer is needed. Just mount the NAS on the new server.
  • Direct copy: Use rsync or robocopy to copy media from old to new storage.
  • Physical drive move: If media is on separate data drives, move the drives to the new server physically.

Step 4: Install Plex on the New Server

Install the same version of Plex Media Server that was running on the old server. Do not start it yet — the installer creates a default data directory, but you will replace it with your copied data.

Step 5: Replace the Data Directory

Replace the newly created Plex data directory with the one you copied from the old server. On Linux, ensure the plex user owns the files:

sudo chown -R plex:plex /var/lib/plexmediaserver/

Step 6: Update Library Paths

If media file paths changed between the old and new server (different mount points or drive letters), update the library paths:

  1. Start Plex on the new server.
  2. Open the web UI and go to each library's settings.
  3. Edit the media folder paths to match the new server's directory structure.
  4. Plex re-scans and matches existing database entries to files at the new paths.

If paths are identical (same NAS mount points, same drive letters), no path changes are needed.

Step 7: Re-Claim the Server

The migrated server may need to be re-claimed on your Plex account:

  • Open the Plex web UI on the new server.
  • If prompted, sign in with your Plex account to claim the server.
  • Existing users and sharing settings should transfer from the database.

Step 8: Configure Remote Access

Remote access settings are tied to the server's network. On the new server:

  1. Go to Settings then Remote Access.
  2. Enable remote access.
  3. Configure port forwarding on your router to point to the new server's IP address.
  4. Verify remote access is working by checking the status indicator.

Cross-Platform Migration

Migrating between different operating systems (Windows to Linux, for example) works with the same process, but file paths always change:

  • Copy the application data directory to the equivalent location on the new platform.
  • Update all library paths to match the new platform's directory structure.
  • Fix file permissions for the new platform's Plex service user.

Docker Migration

For Docker-based Plex installations:

  1. Stop the Plex container on the old host.
  2. Copy the configuration volume to the new host.
  3. Copy media files or reconfigure NAS mounts.
  4. Create a new Plex container on the new host with the same environment variables and volume mounts pointing to the copied data.
  5. Start the container. Plex loads with the migrated database.

Post-Migration Verification

  • Browse each library and verify content is present and playable.
  • Check watch history for a known user — their recently watched items should be intact.
  • Verify collections and playlists are present.
  • Test remote access from outside your network.
  • Confirm hardware transcoding works (play a file that requires transcoding and check the dashboard for the hw indicator).

Troubleshooting

Library Shows Empty After Migration

  • Library paths do not match. Update the media folder paths in each library's settings.
  • File permissions prevent Plex from reading the media. Fix ownership and permissions.

Server Not Recognized by Plex Account

  • Re-claim the server through the web UI. Sign in with the Plex account that owns the server.
  • If the claim fails, delete the Preferences.xml file and restart Plex to generate a fresh one, then claim the server.

Users Cannot Connect

  • DNS or IP has changed. Update the port forwarding rule on your router.
  • Shared users may need to reconnect. The server name and identifier should transfer from the database, but network changes can require re-sharing.
← Back to Blog
More from LuxuriousComputers: LuxuriousComputers · Computer Repair · Remote Fix · Phone Repair · HVAC · Plex Support