Move a Podcast Host Without Duplicating Episodes: Preserve Every GUID
To move an established podcast to a new host without losing subscribers, import the complete archive, preserve every existing episode GUID, and verify the new feed before permanently redirecting the old RSS URL. This sequence lets podcast apps follow the feed change without treating the imported catalogue as a set of replacement episodes.
Keep the old hosting account active throughout the cutover. The safe order is to capture the source feed, import and compare it, activate the redirect, check directory listings and subscriber delivery, transfer monetization, and delay account deletion until the handoff is proven.
1. Capture the source feed before making changes
Record the public RSS URL and save a copy of its XML. Export any analytics, payout records, subscriber data, and media files that the host permits you to retain; these account-level records are separate from the episode metadata exposed through the public feed.
Build an inventory of the show title, author, description, artwork, categories, owner email, episode count, publication dates, audio enclosure URLs, and GUIDs. Note trailers, bonus items, paid episodes, and scheduled releases separately so nothing is omitted or published from both hosts.
Pause routine edits at the old host while comparing the feeds. If an episode must be released during the migration, designate one host as the publisher rather than creating parallel copies with potentially different identifiers.
2. Import first and audit every episode identifier
Run the destination host’s importer while the source feed and media files remain available. Do not proceed when only part of the archive has arrived. Compare the oldest and newest episodes, trailers and bonus items, plus samples from the middle of a large catalogue.
Check titles, publication dates, descriptions, season and episode numbers, explicit-content settings, and playable audio enclosures. Then inspect the raw feeds and match each imported item to its source by GUID. The value must remain identical, including capitalization and punctuation; moving to a new hosting domain is not a reason to replace it with a new identifier.
If the destination changes GUIDs during import, stop before redirecting. Ask the provider to repeat the import with the source identifiers or confirm that the values can be corrected. Rebuilding the catalogue manually is safe only if the original identifiers can be retained.
3. Redirect the verified feed, not an unfinished import
Once the audit passes, configure the old public RSS address to return an HTTP 301 permanent redirect to the exact destination feed. Request the old URL directly and confirm that it resolves to valid podcast XML rather than a dashboard, login page, website homepage, or directory mirror.
Apple’s feed-change guidance tells self-hosters to return a 301 response from the old feed, place the <itunes:new-feed-url> tag in the new feed, and keep both active for at least four weeks; it also warns that changing original GUIDs may create duplicate episodes, distort Analytics data, or affect a show’s status in Apple Podcasts, while an episode without a GUID is identified by its enclosure URL, which must remain unique and unchanged.
A third-party host may create the redirect on your behalf. Even then, test the public source URL independently and retain a record of the destination. Do not submit the migrated feed as an unrelated new show when the aim is to continue the existing listing.
4. Check listings and delivery through existing subscriptions
Inspect the show’s existing pages in Apple Podcasts, Spotify, and every other directory that contributes meaningful listening or revenue. Look for one continuing listing, the complete catalogue, current artwork and description, playable audio, and no duplicated episodes.
Use ordinary listener accounts in more than one podcast app to check an existing subscription. Publish the next planned episode from the new host only, then confirm that it reaches that subscription. A correct import proves that the archive exists at the destination; delivery of a post-migration episode tests the redirect and the live publishing path.
If a directory has not refreshed, leave the redirect unchanged while investigating its feed status. Republishing the archive or repeatedly replacing the destination can introduce additional identifiers and make the problem harder to isolate.
5. Move monetization as a separate workstream
Public RSS continuity does not automatically transfer advertising campaigns, private feeds, paid-member entitlements, dynamic insertion settings, tax records, or unpaid balances. Inventory each revenue system and decide where campaigns, ad markers, paid episodes, and subscriber access will operate after the cutover.
Set one cutoff for monetized publishing so the two hosts do not serve conflicting versions. For shows leaving Spotify for Creators, Spotify’s migration instructions require importing episodes before redirecting and disabling Spotify Subscriptions when applicable; they also state that the redirect can take up to seven days and recommend waiting at least one week after initiating it before deleting the account.
Other providers may handle ads, memberships, and account closure differently. Confirm their terms before cancelling a paid product, because a public-feed follower and a paying member may receive content through different systems.
6. Delay deletion until the handoff is proven
Do not cancel the source plan merely because the destination dashboard reports a successful import. Keep access to the old feed address, redirect controls, media files, and administrative account during the verification window. If maintaining the redirect requires a paid overlap, treat that cost as part of the migration.
Before closing the account, recheck the 301 response, a representative sample of GUIDs, directory listings, delivery of a newly published episode, paid-member access, outstanding payouts, and exported records. Obtain a clear answer from the old host on whether account cancellation removes or shortens the redirect.
Delete the source account only when the redirect will remain available and the live checks have passed. An imported catalogue is merely a copy until unchanged episode identifiers and the old feed’s route to the new destination establish continuity.
Also read:
Subscribe to our newsletter
Get the latest Web3, AI, and crypto news delivered straight to your inbox.