Migrating from Emby to Jellyfin
Direct database migration from Emby (of any version) to Jellyfin is NOT SUPPORTED. We have found many subtle bugs due to the inconsistent database schemas that result from trying to do this, and strongly recommend that all Jellyfin users migrating from Emby start with a fresh database and library scan.
The original procedure is provided below for reference however we cannot support it nor guarantee that a system upgraded in this way will work properly, if at all. If anyone is interested in writing a database migration script which will correct the deficiencies in the existing database and properly import them into Jellyfin, we would welcome it however!
While it is technically possible to migrate existing configuration of Emby version 3.5.2 or earlier, due to subtle and weird bugs reported after such attempts we do not recommend this migration. Emby versions 3.5.3 or 3.6+ cannot be migrated. Thus we recommend creating a new Jellyfin configuration and rebuilding your library instead.
Windows users may take advantage of the
install-jellyfin.ps1 script in the Jellyfin repository which includes an automatic upgrade option.
This procedure is written for Debian-based Linux distributions, but can be translated to other platforms by following the same general principles.
Upgrade to Emby version 3.5.2, so that the database schema is fully up-to-date and consistent. While this is not required, it can help reduce the possibility of obscure bugs in the database.
sudo service emby-server stop
Move your existing Emby data directory out of the way:
sudo mv /var/lib/emby /var/lib/emby.backup
Remove or purge the
sudo apt purge emby-server
jellyfinpackage using the installaton instructions.
sudo service jellyfin stop
Copy over all the data files from the Emby backup data directory:
sudo cp -a /var/lib/emby.backup/* /var/lib/jellyfin/
Correct ownership on the new data directory:
sudo chown -R jellyfin:jellyfin /var/lib/jellyfin
sudo service jellyfin start