Moving Podcast Hosts: The Migration Checklist

Switching hosts without losing subscribers is a 301-redirect problem. Here's how to do it safely.

The landscape

When it comes to the mechanics of a zero-subscriber-loss host migration, the details matter. Here's what the evidence and practitioner experience point to:

• Subscribers follow the RSS URL — a host migration is a feed-redirect problem: your old feed URL must 301-redirect to the new one.
• Export everything first: episode audio files, show metadata, and crucially the subscriber stats you want to compare post-move.

What actually works

When it comes to the mechanics of a zero-subscriber-loss host migration, the details matter. Here's what the evidence and practitioner experience point to:

• The redirect must be permanent (301), left in place indefinitely — directories and apps periodically re-check the old URL for months.
• Don't change GUIDs in migration — episode GUIDs changing republishes episodes and resets stats in some directories.

Putting it into practice

When it comes to the mechanics of a zero-subscriber-loss host migration, the details matter. Here's what the evidence and practitioner experience point to:

• iTunes podcasting tags support itunes:new-feed-url as a hint — update your feed AND set the redirect.
• Test with the redirect checker before switching anything live — a broken redirect orphans your entire subscriber base.

Key takeaways

• Subscribers follow the RSS URL — a host migration is a feed-redirect problem: your old feed URL must 301-redirect to the new one.
• Don't change GUIDs in migration — episode GUIDs changing republishes episodes and resets stats in some directories.
• Test with the redirect checker before switching anything live — a broken redirect orphans your entire subscriber base.

Ready to put this into practice? PodKrafter turns research into broadcast-ready podcast episodes — start free.