Practical guide

A podcast migration plan that preserves the show

Last materially reviewed 2026-09-19

Quick answerImport, validate and redirect are separate steps; keep the original available until the supported checks pass.
What to know

Setup checklist: inventory before importing

List the old feed, episode count, recent release, artwork, directory entries and any private or video elements. Retain original media and export reporting you may need later. Use this as a comparison record, not as a claim that every host imports every field. Note who has authority to change the original feed and who will approve the result before listeners are redirected.

What to know

Check the imported catalogue

Compare the destination with your inventory before switching distribution. Inspect more than the latest episode: include an old episode, unusual artwork or a long description where relevant. Check dates, titles and the media that listeners will receive. Keep differences visible and resolve them through the supported process rather than repeatedly importing the same show in the hope that a missing item will eventually appear.

What to know

Treat redirection as the cutover

Importing creates the destination copy; redirecting tells existing feed consumers where to go. Confirm the precise old-to-new pair before saving a redirect. Do not create a loop or redirect the wrong show because two feeds have similar names. Follow the current host-specific instructions and preserve confirmation. Directory updates can take time, so an immediate screenshot of one app is not the entire acceptance test.

What to know

Close only after verification

Keep a dated record of the redirect, current episode delivery and directory checks. Transistor’s migration guidance says historical analytics do not move with the feed, so retain that evidence separately. Do not cancel the old service simply because the import button reported success. Verify the old provider’s retention and redirect rules, then close the old arrangement only when the approved migration checks and necessary exports are complete. A planned overlap is easier to manage than recovering a prematurely unavailable source.

Continue when useful

Next: How to check a podcast-feed redirect

Check the exact old feed and intended destination before assuming listeners followed the move.

Open How to check a podcast-feed redirect →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Transistor import and migration guidance — Merchant documentation · support.transistor.fm · Merchant-controlled · checked 2026-09-19
  2. Prepare a feed before importing — Merchant documentation · support.transistor.fm · Merchant-controlled · checked 2026-09-19
  3. Apple: change the feed URL and preserve episode identity — Standards and certification reference · podcasters.apple.com · Publisher independence not verified · checked 2026-09-19