How to move podcast from Libsyn to a new host

To move podcast from Libsyn, import the complete show into the destination host while the Libsyn feed is still active. Compare the old and new RSS feeds, add Libsyn's permanent redirect, then check your major listening apps and publish one normal episode from the new host.

A redirect changes where apps fetch the podcast. It does not copy the catalog, move private dashboard data, or repair an incomplete import. Finish those jobs before pointing the old feed anywhere.

Before you move podcast from Libsyn

Choose the destination based on the work your show needs after the move. Compare storage, private feeds, team access, publishing controls, advertising tools, support, and analytics. If you are still deciding, use our podcast hosting company comparison to narrow the list.

Keep the Libsyn account and feed live during the import. Collect the current RSS URL, original audio files where available, show artwork, and logins for Apple Podcasts Connect, Spotify for Creators, and any other directory dashboards you use.

Libsyn support for Podder's analytics prefix is still in progress. Do not move only because you expect an immediate Libsyn installation. A new host should solve a real publishing or measurement requirement, and it should explicitly support third-party analytics prefixes if that is part of your plan.

Record the handoff before changing either account:

The broader podcast host switching guide covers the checks shared by every provider. The steps below focus on Libsyn's redirect and feed behavior.

1. Import the Libsyn catalog at the destination

Open the destination account and run its podcast import tool with the active Libsyn RSS URL. Let it finish before you touch Libsyn's redirect settings. The importer needs the old feed and audio files to remain reachable.

Count the imported episodes. Inspect the newest release, an older release, and any trailer or bonus episode. Play each file and compare its title, publication date, duration, description, season number, and episode number.

Handle account-only material separately. Drafts, scheduled episodes, private feeds, team permissions, ad campaigns, Libsyn destination settings, and hosted pages may not appear in the public RSS feed. Copy or rebuild what you still need rather than assuming the importer can see it.

Do not continue if the destination catalog is short or an audio file fails. Fix the import while Libsyn remains the clear source.

2. Compare the old and new RSS feeds

Open both RSS URLs in a feed viewer. At show level, compare the title, author, description, categories, language, explicit-content setting, and artwork. Keep these fields stable until the move is proven.

At episode level, compare GUIDs as well as the visible text. Apple's hosting-provider migration guidance says episode GUIDs should remain unchanged. Apple also recommends keeping metadata, audio, and season and episode numbers consistent. A new GUID can cause an imported episode to appear as another episode in a listening app.

If feed XML is unfamiliar, read what an RSS feed is before the cutover. Leave the XML changes to the hosts, and make sure you know which address belongs to Libsyn and which one belongs to the destination.

Delay any rebrand, artwork replacement, or archive cleanup. A stable catalog gives you fewer possible causes if a directory displays duplicates or misses an episode.

3. Set Libsyn's RSS redirect

Libsyn's official redirect documentation says to complete the destination import first. Once the new feed is ready:

1. Open the show in Libsyn.
2. Select Settings.
3. Choose Redirects from the sidebar.
4. Paste the destination RSS feed URL into the RSS redirect field.
5. Save the setting and confirm the change.

Copy the URL from the destination host's RSS control. Do not paste its public website, an episode page, or a directory listing.

Libsyn says this setting redirects all Libsyn-generated feeds for the show. That includes feeds created for feed-based destinations, so review the destination carefully before confirming it.

Libsyn also instructs creators moving away to place the itunes:new-feed-url tag in the new feed, pointing to that same new RSS URL. Ask the destination host to confirm whether its migration tool manages this tag. Do not add the tag to the old feed by hand.

4. Test the old Libsyn URL

Open the old Libsyn RSS URL in a private browser window. It should resolve to the destination feed rather than a login page, website, or error response. Check any Libsyn-generated feed URLs recorded before the move because Libsyn states that its redirect applies to all of them.

Then inspect the show in the listening apps that account for your audience. Confirm that the existing listing remains, the catalog appears once, artwork is correct, and several episodes play. Do not submit the destination feed as a brand-new show. That can create a second listing instead of moving the first one.

Apple says a host-provided 301 redirect usually handles the feed change without another edit in Apple Podcasts Connect. If you no longer have access to the old feed, Apple's guide provides a manual update route. That fallback should not replace a working Libsyn redirect.

5. Update Spotify for Creators

Spotify separately asks externally hosted shows to update the RSS link and hosting provider after changing hosts. Follow Spotify's current host-update instructions:

1. Sign in to Spotify for Creators and select the podcast.
2. Open Settings.
3. Review the current RSS feed and hosting partner.
4. Select Update.
5. Enter the destination RSS URL.
6. Confirm the new hosting provider and submit.

This updates Spotify's record. Keep the Libsyn redirect because subscribers and other directories may still request a Libsyn URL.

6. Publish one controlled test episode

After the redirect works and your main listings look correct, publish the next regular episode from the destination. Use the normal schedule and format. A routine release makes it easier to spot a migration problem.

Check that the episode appears once in Apple Podcasts, Spotify, and the other apps you monitor. Compare its title, duration, artwork, show notes, and audio. Confirm that the destination host receives requests for the new episode.

Review your website and production tools too. Replace Libsyn players, media links, or automations that still depend on the old account. A feed can redirect correctly while an embedded player remains tied to Libsyn.

Keep the reporting systems separate. Export the Libsyn history you need, label it with an end date, and start the destination host's series at the cutover. The RSS move does not combine two analytics systems.

7. Close Libsyn only after verification

Libsyn says its RSS redirect remains online even if you close the hosting account. That policy reduces the need to retain a paid plan only for the redirect, but it does not remove the need to test before cancellation.

Confirm each item first:

• The old Libsyn feed resolves to the destination RSS feed.
• Imported episodes appear once and play correctly.
• Spotify shows the new feed and hosting provider.
• Apple and your other important apps retain the existing listing.
• One new episode has distributed from the destination.
• Libsyn reports, billing records, and original files are saved.
• Old embeds and production links have been reviewed.

If a check fails, keep both accounts accessible while the hosts trace it. The redirect is difficult to diagnose after the source account and your notes have disappeared.

Podder does not import Libsyn's hosting data or historical reports. Once the podcast is stable on a compatible destination such as Buzzsprout, Transistor, Podbean, Spreaker, Captivate, Simplecast, Castos, Blubrry, SoundCloud, Megaphone, Art19, OmnyStudio, or PodOps, you can start Podder Analytics as a new measurement series.