Migration
Move from Emby or Jellyfin.
Import libraries, members, watch history and favorites in one go. Your current server keeps running, and your media files are never touched.
Before you start
- Kryspal Media is running and you can sign in to its admin console. The install guide arrives with the first release (Release soon).
- Your current Emby or Jellyfin server is running and reachable from the new one.
- The new server can read the same media files. They appear under /media in the container; add a path mapping in step 4 so the old server’s paths point there.
- Create an API key on the old serverIn Emby or Jellyfin open the dashboard, go to API Keys, and create a key. Use a key made by an administrator.
- Open the import pageIn the Kryspal Media admin console go to System, then the Migration import tab. If this is a fresh install, the setup wizard also offers “Migrate from Emby” or “Migrate from Jellyfin”.
- Connect and previewChoose Emby or Jellyfin, enter the server address (for example
http://192.168.1.10:8096) and the API key, then press Preview. - Choose what to importPick the libraries, and which parts to bring: library settings, metadata, people and images. Choose members, and whether to import their watch history and favorites. If the old server sees different paths than the new one (typical with Docker), add a path mapping and preview again.
- Start and watchPress Import. Progress shows per library, with time left. You can pause, resume or cancel, and follow it in the Task center. What was already written is kept if you cancel, and you can run it again later to finish the rest.
- Read the reportWhen it finishes you get a report of what was created, updated, skipped or failed, with reasons. You can download it.
- Set member passwordsPasswords cannot be migrated. Imported members start disabled until you set a password under Members. Library access and permissions come along.
- Point your player at the new serverAdd the new server address in your player. Keep the old server around until you are happy.
Good to know
- Your media files are never moved, renamed or written to. The old server is only read.
- Libraries that already exist under the same name are reused, not duplicated.
- Collections you made by hand are not imported; movie collections are generated from NFO or online data.
- Items missing data are queued for scraping after the import.
Something went wrong? The report lists each failure with a reason, for example a file that is not found at the new path. Fix the mapping and run the import again; it picks up where it left off.