How to move podcast from Anchor to a new host

To move podcast from Anchor, now called Spotify for Creators, import the show into your new host before changing the old feed. Compare the imported catalog, use Spotify for Creators on the web to redirect the old RSS feed, then verify that podcast directories and existing episodes still work. Keep the old account open while the redirect settles.

This process moves the public show through its feed. It does not move private Spotify analytics, account settings, subscription records, or third-party reporting history. Export anything you need before the cutover and keep a dated note of the change.

Before you move podcast from Anchor

Choose the destination host first. Check its publishing workflow, storage, team access, monetization controls, analytics, and support for any integrations you rely on. If you are still comparing options, use our podcast hosting company guide before starting an import.

Gather access to the Spotify for Creators account, the current RSS URL, your destination account, original audio files where available, artwork, and directory dashboards. Spotify's redirect control is available on the website, not in its mobile app, so plan to do the cutover from a browser.

If the show uses Spotify Subscriptions, disable them from the Monetize tab before moving. Spotify includes that warning in its official instructions for switching away with a 301 redirect.

Export the reports and records you want to keep. A public RSS feed contains published show and episode information, but it does not contain your full account history. Note the final reporting date so future comparisons do not blur two measurement systems together.

Create a small migration record:

If you want a fuller cross-host checklist, read how to switch podcast hosts. The steps below focus on the controls and restrictions specific to Spotify for Creators.

1. Import the show into the destination host

Open the new hosting account and use its import or transfer tool while the Spotify feed is still live. The importer will normally ask for the current RSS URL. Let it finish before redirecting anything.

Check the number and order of published episodes. Play the newest episode and at least one older item from the destination. Confirm that artwork loads and show notes keep their links. Drafts, scheduled episodes, private content, video, subscriptions, and host-specific web pages may require separate handling because they are not ordinary public-feed items.

Do not start publishing from both hosts. Keep Spotify for Creators as the active source until the destination catalog is ready, then make the cutover once.

2. Compare the old and new feeds

Open both RSS URLs and compare the show-level metadata. The title, description, author, categories, language, explicit setting, and artwork should describe the same show.

Then inspect several episodes. Check titles, publication dates, descriptions, audio enclosures, and GUIDs. Apple tells creators to preserve episode GUIDs during a hosting change because changed identifiers can create duplicate episodes and disturb analytics. Its hosting-provider change guide also recommends comparing the old and new feed before redirecting.

This is a poor time for a rebrand or archive cleanup. Move the existing show first. Change artwork, categories, or episode titles after the new feed has distributed successfully, so each problem has one likely cause.

For a quick refresher on what apps read from the feed, see what an RSS feed is.

3. Redirect the Spotify for Creators feed

Use Spotify for Creators in a web browser:

1. Log in and select the podcast.
2. Open Settings.
3. Find Redirect your podcast.
4. Paste the new host's RSS feed URL.
5. Select Redirect.

Copy the destination URL directly from the new host. A typo here sends the old feed to the wrong place, so compare the saved value with the new public feed before leaving the page.

Spotify says a 301 redirect keeps listeners receiving episodes on Spotify and other platforms. It also says completion can take up to seven days. Do not delete the Spotify for Creators account while that process is underway.

4. Verify the redirect outside your accounts

Open the old RSS URL in a private browser window or inspect it with a redirect checker. It should resolve to the destination RSS feed, not an account page, website homepage, or error page.

Play an old episode from the new host, then open the show in the podcast apps that matter to your audience. Confirm that the show appears once, the catalog is complete, and audio starts. The redirect should preserve the existing listing rather than create a second podcast.

Apple says major third-party hosts normally handle the feed change with their redirect, so routine editing in Apple Podcasts Connect is unnecessary. Its RSS feed URL guidance treats a manual Connect change as the alternative when the original feed cannot be redirected.

Record what you checked and when. A simple log is more useful than relying on a green status message inside either host.

5. Publish one normal episode from the new host

Once the redirect works and directory listings look right, publish the next regular episode only from the destination host. Use a familiar format and schedule so an unusual release does not complicate the test.

Check that the episode appears once in Spotify, Apple Podcasts, and the other apps your listeners use. Compare the title, duration, artwork, description, and audio. Verify that the destination host receives activity and that embedded players or links on your website no longer depend on the old host.

Search your site and production documents for old Spotify-hosted media or player URLs. Feed subscribers can move correctly while a manually embedded player remains tied to the prior account.

6. Keep the old account through the transition

Spotify recommends waiting at least one week after redirecting before deleting the account. Use that period to check the redirect again and confirm that a newly published episode distributed from the new host.

Do not treat account deletion as part of the redirect button. Finish the evidence checks first:

• The old RSS URL resolves to the new feed.
• Existing episodes appear once and play.
• The new episode reaches your main listening apps.
• Artwork and show metadata remain correct.
• Reports and account records you need have been saved.
• Website players and production links use the intended destination.

If any check fails, keep both accounts available while the hosts investigate. Closing the old account removes the easiest place to inspect the source feed and redirect setting.

Analytics after the move

Spotify-hosted Anchor feeds do not permit third-party analytics prefixes. Moving to a supported host can make a later prefix installation possible, but the migration itself does not install an analytics service or transfer Spotify data.

Treat the cutover and the prefix installation as separate dated events. The old Spotify reports remain one source. Podder begins a new series when requests start passing through its prefix at the destination. Our Anchor prefix troubleshooting guide explains why there is no supported hidden field or manual enclosure workaround on Spotify hosting.

After the feed, redirect, and new episode have all been verified, you can start a fresh measurement series with Podder Analytics on a compatible destination host.