Migration guide

Whether you come from Overseerr or Jellyseerr, you don't need to perform any manual migration steps, your instance will automatically be migrated to Seerr. This migration will run automatically the first time you start your instance using the Seerr codebase (Docker image or source build or Kubernetes, etc.). An additional migration will happen for Overseerr users, to migrate their configuration to the new codebase.

Docker​

Refer to Seerr Docker Documentation, all of our examples have been updated to reflect the below change.

Changes :

• Renamed all references from overseerr or jellyseerr to seerr.
• The container image reference has been updated.
• The container can now be run as a non-root user (node user); remove the user directive if you have configured it.
• The container no longer provides an init process, so you must configure it by adding init: true for Docker Compose or --init for the Docker CLI.

Config folder permissions​

docker run --rm -v /path/to/appdata/config:/data alpine chown -R 1000:1000 /data

Unix​

Summary of changes :

---
services:
  seerr:
    image: ghcr.io/seerr-team/seerr:latest
    init: true
    container_name: seerr
    environment:
      - LOG_LEVEL=debug
      - TZ=Asia/Tashkent
      - PORT=5055 #optional
    ports:
      - 5055:5055
    volumes:
      - /path/to/appdata/config:/app/config
    healthcheck:
      test: wget --no-verbose --tries=1 --spider http://localhost:5055/api/v1/status || exit 1
      start_period: 20s
      timeout: 3s
      interval: 15s
      retries: 3
    restart: unless-stopped

docker run -d \
  --name seerr \
  --init \
  -e LOG_LEVEL=debug \
  -e TZ=Asia/Tashkent \
  -e PORT=5055 \
  -p 5055:5055 \
  -v /path/to/appdata/config:/app/config \
  --restart unless-stopped \
  ghcr.io/seerr-team/seerr:latest

Windows​

Summary of changes :

---
services:
  seerr:
    image: ghcr.io/seerr-team/seerr:latest
    init: true
    container_name: seerr
    environment:
      - LOG_LEVEL=debug
      - TZ=Asia/Tashkent
    ports:
      - 5055:5055
    volumes:
      - seerr-data:/app/config
    healthcheck:
      test: wget --no-verbose --tries=1 --spider http://localhost:5055/api/v1/status || exit 1
      start_period: 20s
      timeout: 3s
      interval: 15s
      retries: 3
    restart: unless-stopped

volumes:
  seerr-data:
    external: true

docker run -d \
  --name seerr \
  --init \
  -e LOG_LEVEL=debug \
  -e TZ=Asia/Tashkent \
  -e PORT=5055 \
  -p 5055:5055 \
  -v seerr-data:/app/config \
  --restart unless-stopped \
  ghcr.io/seerr-team/seerr:latest

Build From Source​

Refer to Seerr Build From Source Documentation, all of our examples have been updated to reflect the below change.

Install from scratch by following the documentation, restore your data as described in Backups, and then start Seerr. No additional steps are required.

Kubernetes​

Refer to Seerr Kubernetes Documentation, all of our examples have been updated to reflect the below change.

Changes :

• All references to jellyseerr have been renamed to seerr in the manifests.
• The container image reference has been updated.
• The default securityContext and podSecurityContext have been updated to support running the container without root permissions.

Summary of changes :

image:
  repository: fallenbagel/jellyseerr
podSecurityContext: {}
securityContext: {}

image:
  repository: seerr-team/seerr
podSecurityContext:
  fsGroup: 1000
  fsGroupChangePolicy: OnRootMismatch
securityContext:
  allowPrivilegeEscalation: false
  capabilities:
    drop:
      - ALL
  readOnlyRootFilesystem: false
  runAsNonRoot: true
  privileged: false
  runAsUser: 1000
  runAsGroup: 1000
  seccompProfile:
    type: RuntimeDefault

Third-party installation methods​

Nix​

Waiting for https://github.com/NixOS/nixpkgs/pull/450096 and https://github.com/NixOS/nixpkgs/pull/450093

AUR​

See https://aur.archlinux.org/packages/seerr

TrueNAS​

Refer to Seerr TrueNAS Documentation, all of our examples have been updated to reflect the below change.

Unraid​

Refer to Seerr Unraid Documentation, all of our examples have been updated to reflect the below change.

Seerr will automatically migrate your existing Overseerr or Jellyseerr data on first startup. No manual database migration is needed.

1. Stop the existing container In the Unraid Docker tab, stop your Overseerr (or Jellyseerr) container. ⚠️ Do not remove the container or delete the appdata folder yet ⚠️

2. Copy existing data to Seerr appdata Open the Unraid terminal and copy your existing appdata folder into the new Seerr appdata directory:

cp -a /mnt/user/appdata/overseerr /mnt/user/appdata/seerr

(For Jellyseerr users, replace overseerr with jellyseerr in the paths).

3. Set permissions and install Seerr Follow the Unraid Installation Guide, starting from step 2 — this covers setting the correct folder permissions and adding the Docker container. The guide offers two permission methods (Seerr Default and Unraid Default), each with trade-offs — read the descriptions before choosing.

4. Start the new Seerr app Start the newly created Seerr container. Check the container logs to confirm the automatic migration completed successfully.

5. Remove the old app Once you have confirmed Seerr is working properly and your data has successfully migrated, you can safely Remove the old Overseerr (or Jellyseerr) container from Unraid.