Tutorial · Research edition
How to Move a Podcast to a New Host Without Breaking the Feed
Migrate a podcast host by preserving episode GUIDs and metadata, validating the new RSS feed, applying a 301 redirect, checking directories, and retaining a rollback record.
Moving a podcast is an identity migration, not a folder copy. Listeners follow the old RSS URL, directories identify episodes through GUIDs and enclosure information, platforms maintain separate claims and analytics, and the old host controls the redirect that connects them to the new feed.
A safe migration imports first, compares old and new feeds, preserves episode identity, redirects only after validation, and keeps the old service available long enough to observe the change.
Build the migration manifest
Export original and published audio, artwork, transcripts, show/episode metadata, analytics where permitted, directory account list, current RSS XML, episode count, GUIDs, enclosure URLs, publication dates, explicit flags, seasons, and ownership records.
Capture the old feed response and screenshots of important settings. The manifest is the comparison baseline and rollback evidence.
Import without redirecting
Create the new host account and import the show while the old feed remains authoritative. Compare episode count, order, titles, descriptions, artwork, audio duration, file accessibility, dates, seasons, and explicit flags.
Apple specifically instructs creators to compare feeds and preserve unique episode GUIDs. A GUID should not change when metadata or enclosure location changes; altered GUIDs can produce duplicate episodes or analytics disruption.
Validate the new RSS feed
Confirm valid RSS, public accessibility, required tags, at least one episode, artwork, unique GUIDs, correct enclosure MIME/type and URLs, and expected metadata. Test with Apple Podcasts Connect or an RSS viewer before moving listeners.
Publish a controlled change only if needed, then verify it reaches the new feed and media URL without exposing the migration prematurely.
Apply and test the 301 redirect
After the import passes, configure the old host's migration field to redirect the old RSS URL permanently to the new one. Apple and Spotify both describe 301-based host changes; Buzzsprout's documented inbound migration also requires testing the redirect.
Request the old feed URL from more than one network or tool, confirm the redirect chain terminates at the exact new feed, and verify it does not loop or land on a website page.
Directory verification matrix
A feed redirect is the main transport, but platform ownership and settings still need inspection.
- Apple Podcasts: feed URL, followers/play state continuity, episode duplication, GUIDs, artwork, recent analytics.
- Spotify for Creators: update or confirm the new RSS link and hosting provider in Settings when required.
- YouTube RSS ingestion: confirm the source feed, avoid duplicate episodes, and remember re-uploaded RSS audio is not updated automatically.
- Other directories: latest episode, artwork, show URL, category, and redirect response.
- Website/player/newsletter: replace hard-coded old feed or host links.
Overlap, rollback, and cancellation
Keep the old account active for the provider's current recommended overlap. Buzzsprout currently recommends at least two weeks when moving in and at least three weeks when moving away; other providers may specify longer, and Apple emphasizes the permanent redirect rather than one universal cancellation date.
During overlap, publish from one authoritative host only. Monitor redirect health, new episode propagation, support messages, downloads with definition changes noted, and media errors. Cancel only after the manifest is complete, redirect is stable, directories agree, and the current provider procedure permits it.
Sources and verification
Claims were checked against the following first-party documentation on August 5, 2026. Product capabilities can change; verify current documentation before buying or changing a production system.
Frequently asked questions
Will changing podcast hosts lose subscribers?
A correct permanent RSS redirect is designed to carry feed requests to the new host. Preserve GUIDs, test the redirect, verify directories, and keep the old host during the documented overlap.
Why must episode GUIDs stay the same?
Directories use GUIDs as persistent episode identifiers. Apple warns that changed GUIDs can create duplicate episodes and disrupt analytics.
When can the old host be canceled?
Only after the redirect is stable, feeds and directories match, new episodes propagate, assets and analytics are exported, and the old provider's current overlap guidance is satisfied.