Migrate from Sonarr and Radarr to HolyArrs
Move a Docker Sonarr and Radarr setup to HolyArrs 1.1.0 with its read only importer: what carries over, what stays behind, keys to retype and the rollback.
How do you migrate from Sonarr and Radarr to HolyArrs?
To migrate from Sonarr and Radarr to HolyArrs, run HolyArrs next to your old containers, then let its importer read your old apps. The import only reads them. The HolyArrs docs say nothing in the old apps changes, and your media files never move. Next you type in the keys the importer leaves behind, run both setups side by side for a while, and stop the old containers once HolyArrs does the job. If it does not, you stop HolyArrs and start the old containers again.
This guide is for a reader who already runs Sonarr and Radarr in Docker Compose, often with Prowlarr, Bazarr and Seerr, and who has already read how HolyArrs compares with the classic arr stack. It pins holyarrs/holyarrs:1.1.0, released on 12 November 2026. The latest release on 14 November 2026 is 1.1.4; 1.1.3 had already superseded 1.1.0 on 13 November. Every menu label below comes from the HolyArrs README or documentation at that tag; docs.holyarrs.com describes the latest release.
Know how young the project is
HolyArrs is one app that replaces Sonarr, Radarr, Lidarr, Bazarr, Prowlarr and Seerr. It is licensed AGPL-3.0, and the source is at github.com/HolyArrs/HolyArrs.
It is also very new. Release 1.1.0 appeared on 12 November 2026, followed by 1.1.1 to 1.1.3 on 13 November and 1.1.4 on 14 November, so releases land several times a day.
That pace is the reason this guide runs the two setups side by side. You keep a working stack until HolyArrs has proved itself on your own library. Treat it as a new project, not as a finished replacement.
Back up the old apps before you start
The importer only reads, but back up first. In Sonarr, open System, then Backups, and press Backup Now. Do the same in Radarr. Then copy each app's config folder off the server. Backing up a Docker Compose stack covers a full copy of the volumes.
While you are in each app, note its API key. In Sonarr and Radarr it sits under Settings, then General, in the Security section. The importer needs that key, or a backup zip from the app. It accepts zips from Radarr, Sonarr, Lidarr, Prowlarr and Bazarr, with a limit of 1 GB per copied file.
One command to avoid on the old stack: docker compose down -v. The -v flag removes the named volumes declared in the Compose file, and anonymous volumes attached to the containers. If your Sonarr config lives in a named volume, that flag deletes it, and your rollback goes with it. Use docker compose stop when you want the old apps off. The difference between down and stop matters here.
Pin the image tag instead of using latest
HolyArrs publishes images on Docker Hub as holyarrs/holyarrs, for amd64, arm64 and armv7. The README describes two kinds of tag. latest is the newest release, and it moves. A version tag such as 1.1.0 is one exact version, and it never moves.
The README's own compose example uses holyarrs/holyarrs:latest. Change that line. With a pinned tag, an update happens only when you edit the file. With a project that ships several releases a day, that control matters. Check the tags page before you copy the compose file, because a newer tag may exist by the time you read this.
Use one data folder so imports do not copy media
A hardlink is a second name for a file that already exists on disk. It takes no extra space, and it is made instantly. Hardlinks only work inside one filesystem, and Docker treats each mount as its own. So if HolyArrs sees downloads at /downloads and movies at /movies, every import copies the whole file, even when both folders sit on the same disk.
The HolyArrs folders page uses one parent folder, mounted at the same path in HolyArrs and in your downloader:
/srv/data mounted as /data in HolyArrs and the downloader
├── downloads
│ ├── torrents
│ └── usenet
└── media
├── movies
├── tv
└── musicThis is the same idea as the hardlink-friendly arr stack folder layout. If your old stack already uses it, keep it. Your downloader's compose service needs - /srv/data:/data too, and its save folder should be /data/downloads/torrents or /data/downloads/usenet.
One trap: separate NAS shares, or separate datasets under /srv/data, are separate filesystems. Files still copy between them. Use plain folders inside one share. If something is wrong, HolyArrs shows a No hardlink warning on the Library folder in Settings > Library folders.
Write the HolyArrs compose file
Give HolyArrs its own directory and its own compose project. Then the old stack's file is never touched, and the rollback is one command.
sudo mkdir -p /srv/holyarrs/config
sudo chown -R 1000:1000 /srv/holyarrs
cd /srv/holyarrs
sudo nano compose.yamlname: holyarrs
services:
holyarrs:
image: holyarrs/holyarrs:1.1.0
container_name: holyarrs
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
volumes:
- /srv/holyarrs/config:/config
- /srv/data:/data
ports:
- 127.0.0.1:6262:6262
restart: unless-stoppedPUID and PGID set the user and group HolyArrs runs as. Find yours with id youruser, then use the uid and gid values. Leave them out and the defaults are 1000 and 1000. Use the same numbers your old containers use. HolyArrs never changes the owner of media or download folders, so this user needs write access to /srv/data already. How PUID and PGID work in Docker explains the mapping. Match the chown line to your own PUID and PGID.
/config holds the databases, settings, master key, backups and logs. The docs say to keep it on a local disk, not on a network share.
The port line binds to 127.0.0.1 on purpose. Until you create the owner account, whoever opens HolyArrs first becomes the owner. Docker's own docs also warn that published ports bypass ufw, because Docker routes the packets before the ufw rules apply. So on a public VPS, a plain 6262:6262 line would put a setup page with no password on the internet. The HolyArrs docs say not to forward 6262 at all. Use a VPN or an HTTPS reverse proxy instead. Which arr stack ports to expose covers the same rule for the old apps.
Start it, then check it:
sudo docker compose up -d
sudo docker compose ps
sudo docker exec holyarrs /holyarrs doctordocker compose ps should list holyarrs as running. If the container keeps restarting, docker exec cannot reach it. The docs give docker compose run --rm holyarrs doctor for that case.
First login: create the owner account
There is no default password. From your own computer, open an SSH tunnel to the server, then open http://localhost:6262 in your browser:
ssh -L 6262:127.0.0.1:6262 you@your-serverFirst run asks for an owner name and a password of at least 8 characters. The owner can change that minimum later, anywhere from 4 to 64, under Settings > Sign-in and security. First run also asks for your Library folders. With the layout above they are /data/media/movies, /data/media/tv and /data/media/music. After you sign in, a Coming from other apps? prompt leads into the import.
How do I reset a forgotten HolyArrs password?
If you forget the owner password, run this on the server while HolyArrs is running:
sudo docker exec -i holyarrs /holyarrs reset-ownerType the owner name and the new password on separate lines, then press Ctrl+D. The reset signs out every device. It also turns off the owner's two-factor sign-in, and it removes every owner API key. Anything that used one of those keys needs a new key afterwards.
Members and admins cannot use this command. The docs tell them to ask the owner. The HolyArrs docs describe only these two routes, and no email reset. Repeated wrong sign-ins are slowed down, so guessing a password is slow. If you also need to get back into the old apps, see resetting a Sonarr or Radarr password.
Run the import
HolyArrs must reach each old app over the network. Your old stack and the new holyarrs project are separate compose projects, so each has its own default network. The name sonarr will not resolve from inside the HolyArrs container. Use the server address and port you already open Sonarr on in your browser, or attach both projects to one shared Docker network.
Sign in as the owner or an admin. Then follow the five steps documented for 1.1.0:
- Open Settings > Import from other apps. The README at 1.1.0 still calls it Settings > Move from other apps. Five steps appear at the top.
- Read: press Add an app for each old app, and enter its address and API key, or choose From a backup and enter the zip's path inside the container. Turn on the local network switch for an app on your own server or home network.
- Choose: switch on the groups you want.
- Try it: HolyArrs checks first and shows Nothing changes yet. Settle every row under Needs a choice.
- Import: press Import and confirm. You can leave the page while it runs.
The last step, Done, shows the result for each group. Read the not moved list. Every skipped item is on it, with a reason.
Some titles may show as not found. That happens when the old app saw a folder under a different path, for example /movies while HolyArrs sees /data/media/movies. The fix is a path rule under Advanced in Choose, then import again. The longest matching rule wins, and nothing is added twice.
What the importer carries over from Sonarr and Radarr
From the Sonarr and Radarr migration page, these come over:
- Library folders for movies and shows.
- Movies and shows, matched by TMDB or TVDB id. Files stay where they are, and nothing is searched for during the import.
- Quality profiles, each matched to the closest Pick rules preset, Standard or 4K. This is not a one-to-one copy, so check the result.
- Exclusions, as the Never-add list.
- Indexers, as Sources, added paused.
- Download clients, as Downloaders, added paused. They use a separate
holyarrscategory, so they never pick up downloads that belong to the old apps. - Remote path mappings, naming patterns where a pattern has a match, and notifications as Alerts, which stay off until you enter the link or password.
These stay behind: hand-made custom formats, tag-scoped wait rules, release word rules, language profiles, tags, Sonarr import lists, metadata writers and download categories. History is not read at all. In the pinned 1.1.0, custom formats that match TRaSH already come over. Rebuild hand-made custom-format logic in Pick rules by hand.
That describes the pinned 1.1.0. From 1.1.1, Sonarr and Radarr custom formats and quality profiles come over as Pick rules with their exact scores, and tags on Pick rules decide which Sources a title uses.
What happens to Prowlarr, Bazarr and Seerr
Prowlarr. Torznab, Newznab and RSS indexers become Sources. They arrive paused and blocked from the home network. Indexer API keys are not imported, so you type each key again and resume each Source. Prowlarr's app links, sync profiles, indexer proxies and any notification kinds HolyArrs lacks stay behind. Sources that came from Prowlarr still search through Prowlarr, so keep the Prowlarr container running. How Prowlarr connects to the other apps shows what that link looked like on the old side.
Bazarr. Your default language profile becomes Default subtitle languages. Podnapisi and Gestdown become Subtitle sites. Other subtitle sites and their accounts stay behind. Your existing subtitle files sit beside the media, and the import never moves media files, so they stay where they are. In the pinned 1.1.0, Subtitle sites and subtitle search are off by default; enable subtitle_sites through HOLYARRS_FLAGS to use them. They start turned on from 1.1.1.
Seerr and Overseerr. People come over turned off until you invite them. They become members with matching permissions and their weekly request limit. Passwords stay behind. Admins arrive as members unless you switch on Keep as admin, and the owner maps to you only if This is me is on. Waiting and approved requests become Requests for the right person. Finished and turned-down requests are only counted, not copied. The requests import runs last, so it can match requests to titles that are already in HolyArrs.
Issue #334 was fixed in 1.1.1 on 13 November 2026. In the pinned 1.1.0, people imported from Seerr either get a second, empty account or are refused when they sign in with Plex, depending on who is allowed to join, because the import does not save their sign-in link. From 1.1.1, imported people keep their Plex, Jellyfin or Emby link and turn on at their first sign-in that way. If you imported them on 1.1.0, update and run the import again to add the link before you send invites.
Type in the keys the import left behind
The import's read never holds a key, password, token or cookie, even when a backup has them in plain text. The address and API key you type to read an old app are kept separately in the encrypted store until the import finishes without failures or you remove that read. Everything that needs a secret arrives paused or off:
- Settings > Sources: type the key, then resume.
- Settings > Downloaders: type the password or key, then resume.
- Settings > Alerts: type the link or mail password, then turn it on.
- Settings > Users and roles: send invites.
Sources and Downloaders also arrive with May reach the local network turned off. A qBittorrent or Prowlarr container on your own server or home network needs it on. The docs include container names under this switch, so test each Downloader after you resume it.
With many indexers, the secrets file is faster. Download the template from the import secrets page, save it as /srv/holyarrs/holyarrs-secrets.yaml, and fill in the services you use. It uses spaces only, never tabs. A Prowlarr key fills every indexers entry on the same address that has no key of its own. Make an owner API key with the admin scope in Settings > API > API keys, and put it in the file's holyarrs block with the address http://127.0.0.1:6262. Set allow_local_network: true on each service block that uses a local address or container name. Then lock the file and mount it read-only by adding this line under volumes::
- /srv/holyarrs/holyarrs-secrets.yaml:/run/secrets/holyarrs.yaml:rosudo chmod 600 /srv/holyarrs/holyarrs-secrets.yaml
sudo docker compose up -d
sudo docker exec holyarrs /holyarrs import-secrets -file /run/secrets/holyarrs.yaml -dry-runThe file must belong to the container's PUID user so that user can read it with mode 600.
The docs say the dry run prints one would set line per item and changes nothing. An unknown key, or a file over 256 KB, stops the whole import before anything is saved. When the dry run looks right, run the same command without -dry-run. Then remove the mount line, run sudo docker compose up -d again, and delete the file, because it holds every secret in plain text:
sudo shred -u /srv/holyarrs/holyarrs-secrets.yamlThe secrets file covers qBittorrent and SABnzbd. NZBGet, Transmission and Deluge are not supported yet, so type those passwords by hand.
Does HolyArrs handle music requests, like a Seerr for Lidarr?
Yes, at the artist level. Find the artist in Search, switch to Music, press Ask, then pick all albums or tick the ones you want. Music has its own weekly request limit. A music request counts as ready when every track of the requested albums is in. This section comes from the docs. The feature was not tested for this guide.
Two limits apply. The docs say only the owner and admins see music search, and the README says music in Explore is still being built. If you keep Seerr running and point it at HolyArrs, it gets shows and movies only. HolyArrs can answer Seerr as if it were Sonarr and Radarr, through a small old-app API. That API is off by default and covers Shows and Movies. The docs describe nothing for a Lidarr side.
Run both, then retire the old containers
While both setups run, both can search and grab the same release. The simplest order is to keep the HolyArrs Sources and Downloaders paused while Sonarr and Radarr still run. When the HolyArrs library looks right, stop the old apps, then resume the Sources and Downloaders in HolyArrs.
In the old stack's directory, stop only the services HolyArrs replaces. Your service names may differ:
sudo docker compose stop sonarr radarr bazarr
sudo docker compose psLeave Prowlarr running if your Sources came from it. Leave Seerr running if you still point it at HolyArrs. Keep the stopped containers and their config for a few weeks. A stopped container uses no CPU or RAM, and it is your rollback.
How do you roll back to Sonarr and Radarr?
There are two levels of rollback.
Inside HolyArrs, Undo this import removes only what that import added, newest first. Titles leave the Library, but their files stay. Changes you made after the import are kept and listed in the undo report.
To go back to the old stack completely, stop HolyArrs and start the old containers:
cd /srv/holyarrs && sudo docker compose stop
cd /path/to/old-stack && sudo docker compose start sonarr radarr bazarrThis works because the import only read the old apps, and you never ran down -v. This full rollback was not tested for this guide. It rests on the docs' statement that nothing in the old apps changes. Anything HolyArrs downloaded in the meantime is not in the old apps' history, so check those titles after the switch back.
To roll back HolyArrs itself to an older version, set the older tag in compose.yaml and run sudo docker compose up -d. This finishes the rollback only if the update did not change the stored data. Otherwise, select Put back the data from before the update on the page the older version shows, then enter the one-time code from sudo docker logs holyarrs. HolyArrs restores the pre-update backup and stops; the compose file's restart policy starts it again. Without the page, run sudo docker exec holyarrs /holyarrs restore --pre-update, then sudo docker restart holyarrs. Changes made after the update are absent from the restored backup; the newer data is kept under backups/before-restore-<time>/. Never remove /config during an update. A normal update is an edit of the tag, then sudo docker compose pull and sudo docker compose up -d. HolyArrs never installs new versions by itself.
FAQ
How do I reset the HolyArrs password if I forgot it?
Run docker exec -i holyarrs /holyarrs reset-owner on the server while HolyArrs is running. Type the owner name and the new password on separate lines, then press Ctrl+D. The reset signs out every device. It also turns off the owner's two-factor sign-in and removes every owner API key. Members and admins cannot use it, so they ask the owner. The docs describe no email reset.
Does HolyArrs import my Prowlarr indexer API keys?
No. Indexers arrive as paused Sources with no keys. You type each key and resume each Source, or you fill in the optional secrets file and run /holyarrs import-secrets. Sources that came from Prowlarr still search through Prowlarr, so keep the Prowlarr container running.
Will the HolyArrs import move, copy or rename my media files?
No. The migration docs say media files are never moved, renamed, copied or deleted, and the import only reads the old apps. Copies happen later, when HolyArrs imports new downloads across separate mounts. Mount one parent folder such as /srv/data at /data in HolyArrs and in your downloader, and those imports become hardlinks for torrents or instant moves for Usenet.
Do my Sonarr quality profiles and custom formats carry over?
Quality profiles carry over, but each one becomes the closest Pick rules preset, Standard or 4K. It is not an exact copy. In the pinned 1.1.0, only custom formats that match TRaSH carry over; hand-made custom formats, release word rules, language profiles and tags stay behind and appear on the not moved list with a reason. Rebuild hand-made custom-format logic in Pick rules by hand. That describes the pinned 1.1.0; from 1.1.1, custom formats and quality profiles come over as Pick rules with their exact scores.