Menu
ContentsMove from Jellyfin

  1. Getting started

    1. What Kryspal Media is
    2. System requirements
    3. Install with Docker
    4. First-time setup
    5. Upgrade and back up

  2. Libraries

    1. Create and manage libraries
    2. File and folder naming
    3. Flexible file layout
    4. Metadata and NFO
    5. Tags
    6. Images
    7. strm and cloud drives
    8. StrmTool settings
    9. Subtitles
    10. Intro and outro
    11. Search tips
    12. Actors and people
    13. Duplicate videos

  3. Playback

    1. Web player
    2. Third-party players
    3. Remote access

  4. Members and devices

    1. Members
    2. Parental controls
    3. Devices and simultaneous streams

  5. Plugins

    1. Plugin center
    2. Plugins
    3. Third-party plugins

  6. Move from another server

    1. Move from Emby
    2. Move from Jellyfin

  7. Licenses and plans

    1. Compare plans
    2. PRO features in detail
    3. MAX features in detail
    4. Buy, activate and move a license
    5. Offline grace and expiry

  8. Troubleshooting

    1. Logs and reporting a problem

Move from Jellyfin

You can import libraries, members, metadata, artwork and watch history from an existing Jellyfin server. The steps and options are the same as moving from Emby; this page lists only the differences.

On this page
  1. Differences from Emby
  2. Steps
  3. Keep using your third-party players

Differences from Emby#

  • Only Jellyfin 12 is supported. Older versions (10.x, 11.x) are not. Upgrade the source to Jellyfin 12 first.
  • Choose Jellyfin as the source server type. The connection check compares the product name of the source. If you pick the wrong type (for example Emby as Jellyfin), you are told right away that the other server is not the selected type, instead of failing halfway.
  • API key. In Jellyfin's dashboard, open API Keys and create an administrator key. Enter Jellyfin's address (for example http://192.168.1.10:8096) without /emby or any other path. The key is only used to connect and is not stored.
  • What comes over is the same as Emby: libraries and path mapping, members and avatars, metadata and images (as-is), cast and crew, watched state and resume position, favorite videos and people.
  • What does not come over is also the same: passwords (imported accounts start disabled until you set a password and enable them), plugins and their settings, playlists, and collections (rebuilt from NFO files and scanning). Jellyfin plugin settings are not imported.
  • Path mapping. Jellyfin records the paths it sees. You write the rules the same way as for Emby.
  • Time. About the same as a full import from Emby; see the "Move from Emby" page.

Steps#

  1. Go to System → Migration import in the admin console. Choose Jellyfin as the source server type, then enter the address and API key.
  2. Follow steps 2 to 5 and the sections after them in the "Move from Emby" page: preview, path mapping, choose libraries, members and import method, then start.

Keep using your third-party players#

After the import, to keep using your third-party players:

  1. Go to System → Settings and set Third-party player compatibility to "3rd-party players for Jellyfin".
  2. In the app, replace the server address with the new server and sign in with the new password.

Players that are already connected must sign in again after the mode changes. See the "Third-party players" page.