AudioMuse-AI - Provider Migration
AudioMuse-AI rewrites every track’s internal ID from your old media provider to the matching ID on a new one (Jellyfin, Navidrome, Emby, Lyrion…) so your analysis data, embeddings, and local playlists keep pointing at the right songs.
When to use this: you’ve switched the media server in front of the same music library and need AudioMuse-AI to follow along. For example, you replaced Navidrome with Emby but both point at the same files on disk.
Best results: both providers expose the library from the same mount path. The matcher’s most reliable tier is full file-path matching; metadata fallbacks work but are looser and can’t always disambiguate multi-disc albums or tracks with identical titles.
Not designed for: merging two different libraries, or migrating between providers that expose different sets of files. Tracks that don’t exist on the new provider will be deleted as orphans.
1 Back up your database
This tool rewrites every item_id in your database. Mistakes cannot be
undone without a backup. Download a full pg_dump from the
Backup & Restore
page first.
2 Choose the new provider
Select the media server you want to switch to and provide credentials.
3 Automatic matching
Match every track in your AudioMuse database against the new provider. You can re-run this as many times as you want (e.g. after fixing Navidrome's “Report Real Path” setting).
4 Manual album matching (optional)
This step is optional. Any albums you don’t match here will be treated as orphans and their tracks deleted when you execute. If that’s fine for you, skip straight to step 5. Otherwise, find the correct album on the new provider (tracks auto-fill by title) for any you want to keep.
5 Finalize & execute
Review the final counts and unlock the execute button.
6 Execution
Watch the migration run and see the final state.