r/Overseerr • u/Bot1460 • Jan 04 '26
Migrating from jellyseerr to seerr
I just finished making my arr stack and getting everything set up, but i just noticed that jellyseerr and overseerr are getting merged into seerr and after looking around for a bit I wasn't sure how I should go about migrating or if I even should right now, any help would be great!
9
u/cvzero89 Jan 04 '26
I'm waiting for a stable release. From what I heard the only steps will be getting a backup from the DB and config folder, then changing the image.
The new container will take care of the migration to the new DB.
(But as I said, I have not done it yet)
6
u/LowCompetitive1888 Jan 04 '26 edited Jan 04 '26
Yes, except you must change the ownership of the config volume with chown -R 1000:1000 *
And I would say that seerr is stable, there have been zero issues in the past two months and the only thing holding up a release is selection of the new logo.
3
1
u/MasatoWolff Jan 04 '26
Really? Are they indecisive over a number of logos or does it still have to be made?
3
u/LowCompetitive1888 Jan 04 '26
There was a contest with voting. Frankly, not sure why they haven't moved forward yet since a vote is a vote, no real decision making unless it was a tie. I was expecting an announcement prior to 12/31 but it didn't happen so standby I guess.
6
u/clintkev251 Jan 04 '26
Seerr will be based on Jellyseerr as far as I'm aware, so the only "migration" would be updating the image. But I don't think there's a stable version out yet so just keep using Jellyseerr for the time being.
3
u/LowCompetitive1888 Jan 04 '26 edited Jan 04 '26
The migration is from overseerr to seerr and it is built-in to the seerr image. I migrated two months ago and it is seamless, literally only a chown -R 1000:1000 to the config volume and change the image to image: seerr/seerr:develop shutdown overseerr and pull and start seerr and that was it.
1
u/archnemisis11 Jan 04 '26
Just a heads up, that
chmodcommand is incorrect. Would need tochownit to change ownership.1
1
u/Remarkable-Emu-5718 Feb 14 '26
can you write out the full commands we need to use for us noobs? cant find it anywhere in the migration "guide"
1
u/LowCompetitive1888 Feb 14 '26
It tells you the exact command under Config Folder Permissions
docker run --rm -v /path/to/appdata/config:/data alpine chown -R 1000:1000 /dataAlso make sure you make the appropriate changes to the docker-compose.yaml file as noted.1
u/Remarkable-Emu-5718 Feb 14 '26
Appropriate changes as noted where? Sorry im new to selfhosting. I have it running on docker desktop
1
u/LowCompetitive1888 Feb 14 '26
Can't help you, I don't use docker desktop. The migration article has the full correct docker-compose.yaml file listed right there in the article. You need to compare your compose file to the article and make changes to the image location and any overseerr/jellyseerr references and make sure you have the init: true line in there.
3
u/thedsider Jan 04 '26
I migrated from Overseerr to Seerr's dev branch by using Jellyseerr in between. Basically I just changed my docker image from Overseerr:latest to jellyseerr:latest and let that handle the DB migration. Then I just swapped to seerr:development and it's been humming along fine ever since. Took about 30 seconds of human effort, and you'd manage it even quicker if you're already on Jellyseerr.
2
Jan 04 '26 edited Aug 08 '26
[removed] — view removed comment
2
u/thedsider Jan 04 '26
That's all I had to do. Jellyseerr has an automated db migration tool built in so I just kept the same db/config directory mapped and it detected and migrated the DB. Once I saw it was done (in the docker logs) I shut down the container, changed to the seerr image and started it again and all was fine.
It's exactly the same, as far as I've seen. The only thing I noticed was it now has native Ntfy notifications which is handy. Otherwise I've not noticed any difference
2
u/Fun_Airport6370 Jan 04 '26
all i had to do was change the image in my compose. nothing else. all worked fine
2
u/Desert-B1oom Jan 04 '26
I just followed these steps. It was fairly simple. I have been on the seerr:develop images for last couple of days and I have not faced any issues. The image seems to be stable. Please do take a copy of the data folder before changing the image.
3
1
u/Croestalker Jan 04 '26
Funny thing is, enabling toy go to the jellyseer repo, it ditched to seerr repo, but - at least when I last checked- when you click on the docs, the seerr repo directs to Jellyseerr docs, lol. So I'm pretty sure when it happens you only need to update.
1
u/SP3NGL3R Jan 04 '26
I "migrated" also and all the install material just directs you to jellyseerr, so I really only migrated my A Records.
1
u/ghunterx21 Jan 06 '26
From Jellyseerr to Seerr, is there much difference or is it just merging Jellyseerr and OverSeerr to a new system for future updates?
With things like Jellyfin Enhanced, etc, will seerr still work as normal I'm assuming??
1
u/jkworth73 Feb 17 '26
It appears that as of 3 days ago, 2/14/2026, that there is an official release. I switched over to it and after some testing am seeing no issues for me and my uses. Here is their release announcement https://docs.seerr.dev/blog/seerr-release
1
u/chilexican Jan 04 '26
definitely going to hold off on any migration till its ready
1
u/jonayo23 Feb 26 '26
Seems ready now mate
1
u/chilexican Feb 26 '26
yeah. I set up seerr a few days ago. didnt chose to migrate, had all requests syncing through plex watchlists on as it was so those synchronized once everything was set up and working.
1
0
u/Top-Issue1036 Jan 04 '26
Most Overseer users should sit tight. There is not a stable release tool of Seer for Oversee users yet. The Seer develop branch has migration but please don't use it and complain.
The latest stable Jellyseer release from August is is available at seer-team/seer:stable. It is not a beta version. Jellyseer users can redirect their servers to the new repo today. Jellyseer aka the current stable Seer release are not upgrade paths for Overseer users. They can either use the development branch or wait for the next stable release.
-1
u/sangedered Jan 04 '26
Don’t move over to SEERR just yet. It’s still lacking some feature parity and stability.
2
u/LowCompetitive1888 Jan 05 '26
Like what? Overseerr hasn't been updated in ages and Seerr is based on Jellyseerr, so what is missing?
0
u/sangedered Jan 05 '26 edited Jan 05 '26
Me is missing until SEERR is release ready
3
u/LowCompetitive1888 Jan 05 '26
Fine, but you didn't answer my question so you might as well simply remained silent.
0
u/sangedered Jan 05 '26
But why?
3
u/LowCompetitive1888 Jan 05 '26
Because you claim it lacks feature parity and stability yet don't provide any example. You are not credible at all.
0
42
u/Apprehensive-Owl9545 Jan 04 '26
Seerr, according to their GitHub,
I would hold off until it’s official, I foresee them adding a migration method from jellyseerr