Convert to/from Plex/Jellyfin

[BenjaminPrice]

Description

I switched from Plex to Jellyfin a number of years ago but kept running Overseerr out of laziness and not wanting to set up Jellyseerr since the integrations with Sonarr and Radarr worked regardless. Now that both are combined into Seerr, it would be great to migrate my users from being Plex users to being Jellyfin users, and to have all of the Jellyfin config available.

Desired Behavior

A clear migration path to convert my Overseerr/Plex config to Jellyseerr/Jellyfin config, within Seerr.

Additional Context

No response

Search Existing Issues

• Yes, I have searched existing issues.

Code of Conduct

• I agree to follow Seerr's Code of Conduct

[github-actions]

Possible duplicate detected

This issue may be a duplicate of the following (detected via semantic similarity + LLM review):

• Why is it mandatory to have Jellyfin, etc.? #2495 (69% match) — Why is it mandatory to have Jellyfin, etc.?
• Application insists on Jellyfin when I use Plex #2506 (68% match) — Application insists on Jellyfin when I use Plex
• [Feature Request] Need baseURL for reverse proxy support #97 (65% match) — [Feature Request] Need baseURL for reverse proxy support

A maintainer will review this. If this is not a duplicate, no action is needed.

[TheLastFrame]

In their release post they call Jellyfin, Emby & Plex an 'integration'. I wonder how I can disconnect that integration and switch to another one.

Kind had the same issue regardin not wanting to migrate from overseer the last couple years.

[fallenbagel]

In their release post they call Jellyfin, Emby & Plex an 'integration'. I wonder how I can disconnect that integration and switch to another one.

Kind had the same issue regardin not wanting to migrate from overseer the last couple years.

We are working on a script that allows proper migration from for example plex -> jellyfin/emby. Its currently possible to migrate your owner account your media server instance already by just regen settings.json but it will not migrate your users.

[TheLastFrame]

Awesome, thank you for the tip! That's actually perfect for my case, as my users never used it until now.

[fallenbagel]

Awesome, thank you for the tip! That's actually perfect for my case, as my users never used it until now.

unofficial migration steps for owner account:

• stop seerr
• backup settings.json
• delete setting.json
• restart seerr
• dont worry your data is safe as this only deletes settings, your data lives in db
• go through setup wizard with the new media server
• your owner account should now be updated ;)

^ the above is a workaround until we can provide a proper migration path

[TheLastFrame]

Thank you, that worked flawlessly.

The only drawback was, that I also needed to redo the Radarr/Sonarr setup and the Telegram Notifications.

[fallenbagel]

Thank you, that worked flawlessly.

The only drawback was, that I also needed to redo the Radarr/Sonarr setup and the Telegram Notifications.

Oh I forgot to mention, you can also copy back the radarr/sonarr block and notifications block directly from old settings.json

[fallenbagel]

But also:
#2539

[TheLastFrame]

Oh I forgot to mention, you can also copy back the radarr/sonarr block and notifications block directly from old settings.json

Funny, I actually looked into the old settings.json, but it was more or less empty. There was also a settings.old.json, and both of them were last changed yesterday when I did the migration. In the old-old file the data was still there - must have been lost in migration maybe?

[fallenbagel]

Oh I forgot to mention, you can also copy back the radarr/sonarr block and notifications block directly from old settings.json

Funny, I actually looked into the old settings.json, but it was more or less empty. There was also a settings.old.json, and both of them were last changed yesterday when I did the migration. In the old-old file the data was still there - must have been lost in migration maybe?

No i meant from the manual backup of settings.json you took. The settings.old.json is not a backup and you shouldn't rely on that. Thats something used to prevent any data loss during writes