How to migrate from Spotify to Navidrome
Technical infrastructure migrations vary a lot depending on the tool — these are the general steps that apply to most cases.
- 1
Export your configuration and data from Spotify
Check Spotify's documentation for exporting projects, configuration and integrations — the exact format depends on the service, but almost all offer some export path for paid accounts.
- 2
Prepare the Navidrome environment
Deploy Navidrome in a staging environment first (not production) and replicate the base configuration before moving any real data.
- 3
Migrate in pieces and validate each one
Move one project or integration at a time instead of all at once, checking that each piece works in Navidrome before moving on to the next.
- 4
Update integrations that depended on Spotify
Any external service (CI/CD, webhooks, SDKs) that pointed at Spotify needs to be reconfigured to point at your new Navidrome instance.
Before cancelling Spotify
Before cancelling Spotify, confirm no production service still depends on it by checking recent access logs.
Ready to deploy Navidrome?
Full profile with license, tech stack and ready-to-copy docker-compose.
View Navidrome's profileThese steps are a general guideline — the exact export menu can vary depending on Spotify's plan and version.