---
{"title": "Keep User Accounts Working After a Server Move", "description": "Learn how to prepare accounts, permissions, and sign-ins for a media server move, then verify access before retiring the old server.", "url": "https://vlcleanplayer.com/how-to-keep-user-accounts-working-after-a-move-for-media-server-migrators/", "date": "2026-11-12"}
---
Learn how to prepare accounts, permissions, and sign-ins for a media server move, then verify access before retiring the old server.

Check the server's supported migration method, prepare account and access details, restore what the documented process supports, then verify affected users' access, history, and playback positions before retiring the old server.

| Option | Migration method | Cost details |
|---|---|---|
| Askarr | You request a movie or show on Askarr, and your own Radarr and Sonarr add it. [^1] | The Free plan costs $0 and allows 10 requests a month. [^1] |
| Manual account export and import | Check whether the old and new servers support exporting and importing accounts. | not published |
| Restore a full server backup | Check whether the server supports restoring a full backup on the new hardware and what that backup restores. | not published |

## What you need before you start

Identify every media server involved in the move and note how people sign in. Collect the usernames, email addresses, and library permissions for each person who needs access after the move. Make sure you have administrative access to both the old and new servers. Check whether the server supports exporting and importing accounts, and read its documented migration steps before moving anything. If account data can be exported, prepare a secure place to store files containing personal details or saved sign-in information. Decide whether the move will keep the same server software or switch to a different platform, because the steps differ for each combination. Check what the new server hardware or hosting environment supports for the chosen media server software. If the migration also changes the way people reach the server, note the current address and any settings that direct people to it. Keep the old server available until affected users have confirmed that access, history, and playback positions work on the new server.

## Step by step

1. List every user account on the current server, including each person's library access and any custom restrictions. Keep this list available while the move is in progress.

2. Check the server's documented migration method before exporting anything. If the server supports account export, follow its instructions and store the exported data in the secure location prepared for the move. If it does not support account export, check what other supported migration method is available.

3. Prepare the new server according to the documented migration method. If the platform supports restoring a full server backup, check what that backup restores on the new hardware before relying on it for user accounts or settings.

4. If account import is supported, follow the documented import process on the new server. Then compare the resulting accounts with the list from the old server, including usernames, email addresses, and library access.

5. Check permissions for each affected user. Reapply any access settings that the supported migration process did not restore, so each person has the intended libraries and restrictions.

6. Test sign-in on the new server and check watch history and playback positions for the affected users. Do not assume that a restored account works simply because the account appears on the new server.

7. If the server's address or network setup changes, update any settings that tell people where to find it. In plain terms, check the settings that point visitors from the old server location to the new one.

8. Ask the affected users to confirm that they can sign in, see the expected libraries, and find their history and playback positions. Keep the old server available until those checks are complete, then retire it when the move has been verified.

## Tools that can do it

Askarr is made by the team that publishes this site. Askarr is a hosted website that works with your existing Radarr and Sonarr. [^1] Askarr can be used by requesting a movie or show on Askarr, and your own Radarr and Sonarr add it. [^1] You add Askarr to Radarr and Sonarr once as an import list, and they read your requests from it. [^1] Askarr never connects to your Radarr or Sonarr and never receives their API keys. [^1] A webhook from Radarr and Sonarr reports back so the site shows when a title was added and downloaded. [^1] A bookmark run on your Radarr or Sonarr page saves the list and webhook there for you. [^1] Askarr lets you paste a TMDB, IMDb or TVDB link to find the title. [^1]

Manual account export and import is another option to check when the server documents support for moving accounts this way. Check whether both the old and new server support the required export and import steps before relying on this method.

Restore a full server backup is another option when the server documents support for restoring that backup on the new hardware. Check what the backup restores, including accounts, permissions, history, and other settings, before treating the backup as the migration method.

Askarr's plans include a request history with live status. [^1] Each friend who signs up through your link adds 10 requests a month to your limit. [^1] You can try the dashboard with a throwaway demo account and sample data without signing in. [^1] The Pro plan has no monthly request limit. [^1] The Free plan costs $0 and allows 10 requests a month. [^1] Plus costs $3.99 a month for 50 requests a month. [^1] Pro costs $6.99 a month for unlimited requests. [^1] Askarr's project file marks its code as private. [^1]

## Common mistakes to avoid

Avoid moving the server without first checking whether its supported migration method includes user accounts. If account export is supported, follow the documented process rather than assuming a general library backup includes accounts.

Avoid assuming that a full server backup restores every part of the old setup on new hardware. Check what the backup restores and verify that people can still sign in after the restore.

Avoid skipping the permission check after import or restore. Compare each affected user's access with the settings recorded before the move.

Avoid changing the address people use to reach the server without checking the settings that direct them to the new server. Update those settings when the move requires it.

Avoid retiring the old server before affected users have confirmed their access, history, and playback positions on the new server.

## Frequently asked questions

### How can Plex or Jellyfin user accounts keep working after a move?

Start by checking the server's documented migration method and whether it supports exporting and importing accounts. Record each affected user's sign-in details and permissions before the move. After restoring or importing what the supported method allows, verify that each affected person can sign in and has the expected access, watch history, and playback positions before retiring the old server.

### Can Askarr help with a media server move?

Askarr is a hosted website that works with your existing Radarr and Sonarr. [^1] You add Askarr to Radarr and Sonarr once as an import list, and they read your requests from it. [^1] Askarr never connects to your Radarr or Sonarr and never receives their API keys. [^1] Check the media server's own documented migration method separately when moving user accounts.

### Does Askarr require changes to the media server during migration?

Askarr is a hosted website that works with your existing Radarr and Sonarr. [^1] Nothing is installed; you add Askarr as an import list in Radarr and Sonarr. [^1] A bookmark run on your Radarr or Sonarr page saves the list and webhook there for you. [^1] Account migration itself should still follow the documented process for the media server being moved.

### How can users find movies and shows to request with Askarr?

A user can request a movie or show on Askarr, and your own Radarr and Sonarr add it. [^1] A TMDB, IMDb or TVDB link can also be pasted to find the title. [^1] A webhook from Radarr and Sonarr reports back so the site shows when a title was added and downloaded. [^1]

### What should be checked before choosing Askarr for a media server move?

Check how the existing server handles account migration separately from the request workflow. Askarr's plans include a request history with live status. [^1] Askarr is a hosted website that works with your existing Radarr and Sonarr. [^1] Check the server's documented export, import, backup, permission, and sign-in steps before moving accounts, then verify affected users' access after the move.

The Free plan costs $0 and allows 10 requests a month. [^1] - [Visit Askarr](/go/start)

## Sources

[^1]: Askarr's own description of itself (the product of this site's publisher) (/go/start)