Skip to content

Migrate to ElfHosted

If you've been running Plex, Jellyfin, Emby, or the Radarr / Sonarr stack on your own hardware, ElfHosted is a managed alternative that takes the hardware, electricity, uptime, and updates off your hands. This page covers the practical migration paths from the four most common home server platforms (unRAID, TrueNAS, Synology DSM, and a generic Docker host), what stays the same, what changes, and how to move without losing your library or your watch state.

Browse personal media stacks See pricing Start a $1, 7-day trial

When does migration make sense?

The triggers people actually quote when they migrate to ElfHosted:

  • Hardware is retiring or has retired. A NAS that's out of warranty, a mini-PC that's getting hot, a build you're tired of patching.
  • Electricity is climbing. A 24/7 home server typically costs 5-30/month in electricity, before you count any new hardware.
  • You're moving, downsizing, or travelling. A home server lives somewhere; if your life moves, the server has to move with it (or stay put and become someone else's problem).
  • Your home network is the bottleneck. Tight upload bandwidth, NAT problems, ISP CGNAT, or "every device on the LAN slows down when Plex is streaming".
  • You're tired of being on-call. Plex restarting at 3am, Sonarr breaking after an update, the DNS settings drifting, the SSL cert expiring. The hobby has turned into a part-time job.
  • You want hardware transcoding without buying it. A current-generation Intel CPU with QuickSync is great, but ElfHosted's Hobbit plans and above include hardware transcoding without you owning the hardware.

If none of these match you and your home setup is a joy, keep it. ElfHosted isn't for everyone.

What stays with you

The reassuring part of migrating to ElfHosted is that most of the things you've invested time in carry across:

  • Your Plex / Jellyfin / Emby account. Watch state, ratings, playlists, continue-watching, friend connections are all account-side, not server-side. The new ElfHosted server picks them up automatically once you claim or sign in.
  • Your library, if it lives on cloud storage. Already on Real-Debrid? Just attach the token. Already on Usenet via an NzbDAV-compatible provider? Just attach. Already on Hetzner Storage Box, Google Drive, OneDrive, or any rclone-compatible cloud? Configure rclone, point apps at the mount.
  • Your Sonarr / Radarr config and history. Both export their settings cleanly. Import on ElfHosted, point at the new download client (Decypharr for Real-Debrid, NzbDAV for Usenet), and you're back to the same library logic.
  • Your PlexPass / lifetime pass. Account-bound, not server-bound. ElfHosted Plex inherits the benefits.
  • Your custom indexers and Prowlarr config. Export from your old Prowlarr, import to the new one.

What changes

Worth being clear about what's different on ElfHosted:

  • You don't run the apps. The hardware, OS, container runtime, monitoring, and updates are handled. You configure apps the same way (through their UIs); you just don't have a shell on the host.
  • Storage is bring-your-own. ElfHosted hosts apps; the library lives in your storage (Real-Debrid, Usenet, Hetzner Storage Box, rclone-compatible cloud). Your monthly ElfHosted bill is the same whether the library is 200 GB or 20 TB.
  • A subscription replaces electricity + time. Monthly per-app or per-bundle, with a $1, 7-day trial on most products. See pricing for the structure.
  • Some platform-specific things don't carry over. unRAID community plugins, Synology DSM apps (Photos, Surveillance Station, Note Station), TrueCharts, dynamix utilities are platform-bound and have ElfHosted equivalents only where there's an open-source upstream we can run. Check the app catalog before assuming parity.

Migration paths by source platform

From unRAID

unRAID users typically run Plex / Jellyfin, Sonarr / Radarr / Prowlarr, qBittorrent or SABnzbd, and a mix of Community Apps. Most of that maps cleanly to ElfHosted:

unRAID app / pattern ElfHosted equivalent
Plex docker container Plex (managed, claim via ElfBot)
Jellyfin / Emby docker Jellyfin / Emby (managed)
Sonarr / Radarr / Prowlarr Same apps, managed
qBittorrent + Real-Debrid bridge (rdt-client, etc.) Decypharr (qBittorrent-API-compatible Real-Debrid client, replaces RDTClient)
SABnzbd / NZBGet for Usenet NzbDAV (SABnzbd-API-compatible, plus on-demand article streaming)
Overseerr / Jellyseerr / Ombi Seerr (current canonical request manager), or its predecessors
Tdarr / Unmanic transcoding Not currently in the catalog. Best handled before migration if you're doing format conversion
dynamix / Unassigned Devices / community plugins unRAID-specific, no equivalent (platform features)

Storage: your unRAID array is the trickiest part of the migration. Three paths:

  • Move the library to a Hetzner Storage Box, attach to ElfHosted. Often the cleanest cut-over for users who don't want to keep the home server running.
  • Keep the array, expose it to ElfHosted via WebDAV / SFTP. Works, but you're now paying for both ElfHosted and the unRAID box's electricity, and your home upload bandwidth is still in the loop.
  • Switch to Real-Debrid or Usenet content. If your library is mostly content you can stream from a debrid or Usenet provider, this is the simplest cut-over: you stop self-hosting the library and use the streaming-as-storage model. See Plex + Real-Debrid + Aars or Plex + Usenet + Aars.

Common gotcha: hard-coded paths inside Sonarr / Radarr root folders. unRAID typically uses /mnt/user/Media/Movies style paths; ElfHosted uses /storage/.... After importing config, fix the root folders and re-scan.

From TrueNAS

TrueNAS Core (FreeBSD jails) and TrueNAS SCALE (Kubernetes / TrueCharts apps) both map similarly to ElfHosted, with TrueNAS SCALE being closer in shape since both are Kubernetes-based.

TrueNAS app / pattern ElfHosted equivalent
TrueCharts Plex / Jellyfin / Emby Plex / Jellyfin / Emby (managed)
TrueCharts Sonarr / Radarr / Prowlarr Same apps, managed
qBittorrent + scripts for Real-Debrid Decypharr
SABnzbd / NZBGet NzbDAV
Photoprism, Immich, Nextcloud Immich in catalog; Photoprism / Nextcloud check the catalog
ZFS snapshots TrueNAS-side feature; on ElfHosted, ElfBot handles config backups, your storage layer handles your library

Storage: ZFS pools don't migrate to ElfHosted directly. Three paths:

  • Move the data to a Hetzner Storage Box, attach to ElfHosted.
  • Keep the ZFS pool at home and expose it via SMB or SFTP. Same caveat as unRAID: you're still paying for the home box.
  • Switch to Real-Debrid / Usenet. Same logic as the unRAID case.

Common gotcha: TrueCharts uses opinionated paths like /var/lib/.../media. After exporting Sonarr / Radarr settings to ElfHosted, fix the root folder and quality profile paths.

From Synology DSM

Synology DSM is the most platform-locked of the four. DSM is its own ecosystem with first-party apps. The container parts (Container Manager / Docker) migrate cleanly; the DSM-native apps don't.

Synology DSM feature ElfHosted path
Plex Media Server (DSM package) Plex (managed). Move config; libraries auto-rebuild from Plex account
Container Manager: Sonarr / Radarr / Prowlarr Same apps, managed. Export โ†’ import
DSM Photos Immich is the closest catalog equivalent; not 1:1
DSM Drive / Cloud Sync [Nextcloud / Seafile / rclone] depending on need; check the catalog
Surveillance Station No equivalent (Synology-specific)
Note Station / Office No equivalent (Synology-specific)
Synology Hyper Backup ElfBot handles config backups; storage backups are your responsibility per the storage you choose

Storage: Synology volumes are exposed via SMB / NFS / WebDAV. Three paths:

  • Move data to a Hetzner Storage Box (often cheaper than continuing to run the Synology, especially if it's an older model).
  • Keep the Synology and expose via WebDAV / SFTP. Synology's WebDAV server is solid; this works but adds round-trip from datacenter to home.
  • Switch to Real-Debrid / Usenet for media; keep the Synology for non-media data (photos, documents, backups) until you've decided whether to migrate that too.

Common gotcha: Synology Photos has no clean ElfHosted equivalent. If photos are the main thing keeping the Synology, plan that piece separately. Immich is the usual destination.

From a generic Docker / Linux host

If you're already running everything as Docker containers on a Linux host (a VPS, a mini-PC, a home Docker-Compose setup), the migration is mostly conceptual: ElfHosted runs the same images, just managed.

Docker pattern ElfHosted equivalent
docker compose up -d plex jellyfin sonarr radarr prowlarr A bundled stack from the store, provisioned in minutes
Bind mounts: /srv/media:/data Bring-your-own storage attached as /storage/...
Custom containers If they're in the ElfHosted catalog, use them directly. If not, ask in Discord; the team adds apps based on user requests
Traefik / Nginx Proxy Manager + custom domains Handled. Every app gets a *.elfhosted.com URL with TLS, with optional custom domains
Watchtower / auto-updates Handled
Healthcheck.io / Uptime Kuma Per-app health monitoring is included

Storage: bind mounts are the part you actively migrate. Most users move to a Hetzner Storage Box (cheaper than home electricity at most sizes), or switch to a Real-Debrid / Usenet model.

Common gotcha: docker-compose users often mix dev and prod containers on one host. ElfHosted is for the prod media stack; if you have dev containers (databases, custom apps), keep them somewhere else or check whether they fit the catalog.

Storage migration paths

Storage is the part of migration that needs the most thought, because it's the part that doesn't carry over automatically.

Where your library lives now Migration path
Real-Debrid (already) Attach the token. Zero migration.
Usenet via NzbDAV-compatible provider Attach. Zero migration.
Rclone-compatible cloud (Google Drive, OneDrive, Dropbox, etc.) Configure rclone on ElfHosted, point apps at the mount. Zero data movement.
Local NAS / on-disk at home Move to a Hetzner Storage Box (recommended), or expose via SMB / WebDAV / SFTP and accept the round-trip.
Mixed (some cloud, some local) Hybrid path: cloud parts attached natively, local parts exposed via SFTP. Plan the cut-over per library.

The pragmatic recommendation: if your library is on Real-Debrid or Usenet already, migration is a one-day task. If it's on local disks, plan for either a Storage Box (clean cut-over) or a streaming-as-storage switch (Real-Debrid or Usenet); keeping a home NAS and paying for ElfHosted is the worst-of-both-worlds path.

Cost comparison

A typical home server vs ElfHosted, for a Plex + Aars + Real-Debrid setup:

Cost Home server ElfHosted
Hardware (NAS or mini-PC) 300-1,500 up front $0
Electricity 5-30 / month included
ISP / static IP / port forwarding 0-10 / month not your problem
Hardware transcoding licence PlexPass: $5/month or $120 lifetime included on Hobbit and above (still need PlexPass for Plex)
Updates and monitoring your time included
Uptime when you travel depends on your home network 24/7 datacenter
Real-Debrid subscription 4-10 / month same (BYO Real-Debrid)
Cloud storage (if used) varies varies (you're paying it either way if you use cloud storage)

For most users, ElfHosted's all-in subscription costs the same as the electricity on a home server, before you count any of the other line items. See pricing for the full structure.

Migration timeline

A realistic timeline for moving a Plex + Sonarr + Radarr + Real-Debrid setup:

  1. Day 0, subscribe. Pick a bundle, start the $1 trial. Apps provision within minutes.
  2. Day 0, attach storage. Real-Debrid token, NzbDAV / Usenet provider, or rclone config. If you're switching from local disks, this is when the Storage Box order goes in.
  3. Day 0-1, migrate app config. Export Sonarr, Radarr, Prowlarr settings from old install. Import on ElfHosted. Fix root folders to ElfHosted's /storage/... paths. Claim Plex server via ElfBot.
  4. Day 1-3, validate. Run new and old setups in parallel. Trigger a few searches in the new Sonarr / Radarr, check that Plex sees the library, verify a couple of streams from each major client (TV, phone, web). Compare watch state.
  5. Day 3-7, cut over. Once you've validated the new setup, shut down the old one. If you're on the trial, this is also when you decide whether to keep the subscription.
  6. Week 2, decommission. Power down the home server, archive the data drives if you're not using a Storage Box, sell or repurpose the hardware.

The whole thing takes a few hours of active work spread across about a week. You don't need to take downtime; old and new run in parallel until you cut over.

Frequently asked questions

Can I run a hybrid setup, with some apps at home and some on ElfHosted?

Yes. Common hybrid pattern: keep your existing NAS at home for photos / documents / backups, run Plex / Jellyfin and the Aars stack on ElfHosted, and either expose the NAS to ElfHosted via SFTP (if your media is on the NAS) or switch to Real-Debrid / Usenet for media (if you don't want round-trips). This gets you out from under the 24/7 media-server uptime burden without abandoning your existing storage.

How long does the migration actually take?

Real-Debrid or Usenet libraries: a few hours (mostly waiting for app configs to import and verifying things work). Local-disk libraries: depends on how much data you're moving. A Hetzner Storage Box order takes a day or two to provision, then data movement is bounded by your home upload speed.

Will my Plex Pass / lifetime pass work?

Yes. PlexPass is bound to your Plex account, not to a specific server. Claim the ElfHosted server against your account and PlexPass benefits (hardware transcoding, Remote Play, all the others) carry across.

Can I migrate my Sonarr / Radarr download history?

Yes. Sonarr and Radarr both support clean Settings โ†’ System โ†’ Backup โ†’ Restore flow. Export from the old, import to the new. The history (what's been grabbed, what's been imported) carries across. The download client config will need to be updated to point at the new Decypharr (for Real-Debrid) or NzbDAV (for Usenet).

What if I want to migrate back?

ElfHosted is built for portability: storage is bring-your-own (so your library is yours), config is exportable (Sonarr / Radarr / Prowlarr export their settings), and the underlying apps are open-source images you can run anywhere. Cancel the subscription, pull your config exports, point your own setup at the same storage. The friction is in setting up the home server again, not in getting your data out.

Can I keep my local NAS for non-media things?

Of course. ElfHosted is specifically the media-stack-and-app-hosting half. If your NAS is doing photos, document storage, and backups, that's a different workload and an ElfHosted migration doesn't touch it.

What about apps that aren't in your catalog?

Check the app catalog first; it's grown to 100+ apps and likely covers what you need. If it doesn't, ask in Discord. ElfHosted adds new apps based on user demand; if there's an open-source upstream and a clear use case, it usually gets in.

Will my Sonarr / Radarr root folders break after import?

The root folder paths will need to change. Home setups typically use /mnt/user/Media/Movies (unRAID), /mnt/Pool/media (TrueNAS), or /volume1/media (Synology). ElfHosted uses /storage/.... After importing, change the root folders in Sonarr / Radarr to the ElfHosted paths and re-scan; the library imports will recover automatically.

Can I trial ElfHosted while my home server is still running?

That's the recommended path. Run both side-by-side during the $1, 7-day trial, validate that everything works, then cut over. If something doesn't work the way you expect, you've still got the home server as a fallback while you debug.

What about the data on my Real-Debrid account that's already organized? Does it import as-is?

Yes. Real-Debrid is account-side, not server-side. Once you attach your token to ElfHosted, the same Real-Debrid library is visible to Decypharr and the apps you've configured. Nothing to re-organize, nothing to re-download.

Is my watch state / continue-watching preserved across the migration?

Yes for Plex (account-bound). For Jellyfin and Emby, watch state is server-side; if you back up the old database before migrating, you can restore it on the new server. Without a backup, watch state resets, but library structure and metadata rebuild automatically.

Start your $1, 7-day trial See pricing