What is Podcast Migration?
Podcast migration is the process of moving your show from one hosting provider to another while maintaining subscribers, download history (where possible), and directory listings. Proper migration requires careful planning to preserve your audience.
Migration Checklist
Pre-Migration
- Export/document all episode metadata
- Download original audio files if needed
- Note all current directory listings
- Check new host's import capabilities
- Verify GUID handling
During Migration
- Import all episodes to new host
- Verify RSS feed is correct
- Preserve all GUIDs exactly
- Set up 301 redirect on old host
- Test redirect is working
Post-Migration
- Verify directories show episodes
- Monitor for any issues
- Keep old host active for redirect period
- Update any direct feed links you control
What to Preserve
| Element | Importance | How to Preserve |
|---|---|---|
| GUIDs | Critical | Must be identical |
| Episode URLs | Important | Redirect handles this |
| Metadata | Important | Import/re-enter |
| Analytics | Varies | May not transfer |
| Reviews | Critical | Directory maintains |
Migration Risks
| Risk | Consequence | Mitigation |
|---|---|---|
| GUIDs change | Mass re-downloads, reset progress | Verify GUID preservation |
| No redirect | Lost subscribers | Set redirect before canceling |
| Missing episodes | Incomplete catalog | Verify all episodes imported |
| Metadata loss | Incorrect display | Manual verification |
Migration Timeline
| Phase | Duration | Activities |
|---|---|---|
| Planning | 1-2 weeks | Research, export data |
| Import | 1 day | Move content to new host |
| Verification | 1 week | Test everything |
| Transition | 2-4 weeks | Both hosts active |
| Completion | 1+ month | Safe to reduce old plan |
Why It Matters
Migration done right is invisible to listeners. Migration done wrong can devastate your audience. The stakes are high enough to warrant careful planning.
Why proper migration matters:
-
Subscriber retention: Bad migration = lost subscribers who may never return.
-
Download continuity: Proper migration maintains your download trajectory.
-
Directory standing: Reviews, ratings, and chart history should persist.
-
Professional reputation: A botched migration looks unprofessional to listeners.
Migration horror stories:
| What Went Wrong | Consequence |
|---|---|
| Canceled old host first | All subscribers lost |
| GUIDs changed | Every episode re-downloaded, progress lost |
| Redirect not set | 50% audience drop overnight |
| Metadata mismatched | Confused directory listings |
When to migrate:
| Reason | Migration Priority |
|---|---|
| Cost savings | Plan carefully, not urgent |
| Missing features | Plan carefully |
| Better analytics | Worth migration effort |
| Service issues | Migrate promptly but carefully |
| Host shutting down | Urgent but still do it right |
The migration investment: Proper migration takes time and attention. Don't rush it to save a few days of hosting fees—the potential cost of errors far exceeds any savings.
How to Use This in Dispatch
Use our migration tools to import your existing podcast and set up proper redirects:
Import process:
- Go to Settings → Migration
- Enter your current RSS feed URL
- We parse and import all episodes
- Review imported content for accuracy
- Publish to activate your new feed
What we preserve:
- Episode titles, descriptions, metadata
- GUIDs (critical for preventing re-downloads)
- Publication dates
- Audio files (downloaded and re-hosted)
- Show-level metadata
After import:
- Set up 301 redirect on your old host
- Verify redirect with our testing tools
- Monitor your analytics for any issues
- Keep old host active for redirect (at least 1-3 months)
Migration support: Contact support if you encounter any issues during migration—we can help troubleshoot GUID mismatches, redirect problems, or import errors.