Move a podcast with stable episode identities, verified media, a durable feed redirect and a documented listener test before retiring the old host.
Export the current RSS feed, original media, artwork, analytics reports and any available ad-marker or subscription records. Create an episode inventory keyed by original GUID, including title, publication date, enclosure URL, byte size and duration. Record directory ownership and services that may need separate migration; analytics and billing data may not transfer with RSS.
Import into the new host without creating a duplicate directory listing. Compare every old episode against the imported GUID and metadata, then check that each media URL is reachable. Sample playback across older and newer episodes, including files with chapters or inserted advertising. Investigate missing or altered items before changing the public feed.
Inspect actual responses for the new RSS and media URLs using your browser or HTTP client. Confirm the required media access, content type and real byte lengths. Paste a single redacted response block into the header parser when helpful; it does not fetch URLs. Compare transfer plans using the host’s documented units, billing period and measured delivery assumptions.
Use the old host’s migration process to redirect the old feed URL to the new one. For a self-hosted Apple migration, follow Apple’s 301 and new-feed-url instructions. Check the old URL’s actual redirect destination and the new feed response. Preserve original episode GUIDs and avoid redirect loops or resubmitting an existing show as a new listing.
Use an app that already followed the old feed and another fresh test subscription. Verify the current episode catalog and playback, then confirm that the next normally scheduled episode reaches both. Check each directory’s feed status and monitor failures. Preserve the old service until these checks and the provider’s migration conditions are satisfied.
Record the final feed URL, redirect evidence, directory status and ownership. Confirm archive availability, subscription or ad-service transitions and any remaining billing obligations with the providers. Retire the old hosting resources only when the redirect remains supported and the acceptance checks pass. Download the migration note and keep independent media and analytics backups.
Build and download the GUID-based inventory and migration acceptance record.
Review one pasted response block for feed redirects and media delivery fields.
Compare one period of explicitly defined transfer volume and linear hosting charges.
Loading your checklist…
Apple’s self-hosted migration instructions require a feed redirect and update tag to remain for at least four weeks. Existing episode GUIDs must remain stable.
Spotify documents redirecting away from its hosting service and a separate account-closure timing recommendation. Check the actual provider conditions instead of applying a universal 48-hour rule.
Keep these task-specific records with the tested version and review date.
| Record | Include | Verify |
|---|---|---|
| Identity | Original GUID → imported episode | No missing or duplicate identities |
| Delivery | Old/new feed responses and media checks | Redirect and playback work |
| Services | Analytics, ads, subscriptions and billing | Each dependency has its own owner and transition |
A feed redirect does not copy historical analytics, contracts, payment accounts or subscriber billing.
Download the original records while you still have access to the old host.