How to move podcast from RedCircle to a new host

To move podcast from RedCircle, opt out of the RedCircle Ad Platform, remove Audio Blocks, and save your analytics before importing the show at a new host. After checking the destination feed, use RedCircle's Redirect Podcast flow. Keep the old show in place for at least four weeks while you test the redirect, directory listings, and a new episode.

RedCircle does not support Podder's analytics prefix. A compatible destination can install Podder for future requests, but the move will not carry RedCircle's private analytics into Podder or the new host.

Before you move podcast from RedCircle

Choose the destination and confirm that it fits the whole show, not only its analytics requirement. Compare publishing tools, team permissions, private content, monetization, dynamic insertion, reporting, integrations, and support. Use our podcast hosting company comparison if you still need to select a provider.

RedCircle's official move-away instructions call out three preparations. Opt out of the RedCircle Ad Platform, remove Audio Blocks, and download or save analytics before starting the move. Removing dynamic material prevents inserted ads from becoming part of files copied to the destination.

Gather the current RedCircle RSS URL, destination account, original audio files where available, show artwork, and access to claimed directory dashboards. Save billing and campaign records as well as analytics. A public RSS import does not bring private reports, earnings, plan details, team settings, or campaign state with it.

Create a compact migration record:

Keep the wider podcast host switching guide beside this RedCircle-specific process.

1. Remove dynamic advertising from the source

RedCircle warns that leaving RAP or Audio Blocks in place can bake ads into the copied content. Confirm the change against several episodes rather than assuming one account-level action changed every release.

List other RedCircle-only features that will not travel through RSS. Private arrangements, campaign settings, team permissions, scheduled episodes, drafts, plan benefits, and hosted pages need a separate decision. Assign each item to a person, destination, or archive.

Download or save the analytics you need. Label the records with their source, date range, and export date. RedCircle states that analytics do not transfer between hosting platforms, so the saved records will remain the historical baseline.

2. Import the complete show at the destination

Keep the RedCircle feed public while the new host imports it. Create the destination show and provide the active RedCircle RSS URL. Do not remove or redirect the source podcast yet.

Count the imported episodes, then inspect a recent release, an older release, and items from different parts of the archive. Play each selected episode. Check title, description, publication date, show-note links, artwork, season and episode numbers, audio duration, and enclosure behavior.

Listen for ads that should have been removed. If an inserted spot appears in a destination file, stop and correct the RedCircle source or replace that file before redirecting. Do not let a flawed import become the only copy used by directories.

Rebuild only the publishing and monetization controls that the destination supports and your show still needs.

3. Compare both RSS feeds

Open the RedCircle and destination feeds in an RSS viewer. Compare show title, author, description, categories, language, artwork, and explicit-content setting. At episode level, compare titles, publication dates, descriptions, audio enclosures, and GUIDs.

Apple's official hosting-provider migration guide says GUIDs should remain unchanged. It also asks creators to keep metadata, audio, and season and episode numbers consistent. If an old episode receives a new GUID, a listening app may treat it as a second release.

Delay rebranding and archive cleanup. First move the same show and publish one normal episode from the destination. Changing the artwork, feed address, and episode identity together makes duplicates or missing items harder to trace.

What an RSS feed is explains why the published catalog can move while RedCircle's private analytics and account state remain behind.

4. Redirect the RedCircle podcast

Once the destination feed is complete and stable, use RedCircle's documented route:

1. Log in to RedCircle and select the podcast.
2. Select the three dots next to the podcast title.
3. Choose Remove Podcast from the menu.
4. Select Redirect Podcast to continue.
5. Complete the required text fields with the destination RSS URL.
6. Read and select the agreement box.
7. Select the red Redirect button.

Before confirming, paste the destination feed URL into a browser. RedCircle specifically warns you to confirm that the new feed does not redirect back to RedCircle. A loop would leave apps unable to settle on either feed.

Copy the RSS address from the destination host. Do not use its public website, an episode page, or a directory listing. Compare the value with your migration record before selecting Redirect.

RedCircle says the redirect remains indefinitely while you do not permanently delete the show from its platform. Keep the redirected show during verification.

5. Verify the listener path

Open the old RedCircle RSS URL outside your signed-in session. It should resolve to the destination feed, not a RedCircle account page, website, or error response. Record the old URL, final URL, result, and test time.

Then inspect the show in Apple Podcasts, Spotify, and the other apps that matter to your audience. Confirm there is one listing, existing episodes remain in order, artwork is correct, and audio plays. Do not submit the destination feed as a new show. The redirect is meant to move the current listing and subscriber path.

Apple says a 301 redirect from the old host migrates followers, including those outside Apple Podcasts. Its manual Apple Podcasts Connect feed edit is available when the old feed cannot provide a redirect. With a working RedCircle redirect, verify the listing instead of creating another submission.

Keep a dated directory log. A working old-feed test is necessary, but listening apps can update on their own schedules.

6. Publish one test release from the destination

After the redirect works and the main listings look stable, publish the next regular episode only from the destination. Use the normal release format and schedule.

Check that the episode appears once in your important listening apps. Compare title, duration, description, artwork, and audio. Confirm that the destination receives new activity. Listen long enough to check the parts of the episode where RedCircle's Audio Blocks previously appeared.

Review your website and production systems. Replace RedCircle players, direct media links, and automation inputs where necessary. Subscribers can follow the feed redirect while a manually embedded player still depends on the old account.

Keep the RedCircle login and destination access available if a check fails. Both providers may need the original and imported records to diagnose a missing or duplicated item.

7. Wait before deleting the RedCircle show

RedCircle recommends waiting at least four weeks, about 30 days, after the redirect before permanently deleting the show. Deletion and redirection are different actions. Deleting too soon removes the long-lived redirect that old subscribers and slower directories may still request.

Use the waiting period to confirm:

• The old RedCircle feed continues to resolve to the destination.
• Existing episodes appear once and play.
• A new episode distributes from the destination.
• The important directory listings remain attached to the existing show.
• Analytics, campaign records, and billing details are saved.
• Website embeds and production automations use the intended destination.

If you purchased a Growth or Pro plan, RedCircle says to cancel it before renewal. Handle the plan separately from the podcast redirect and permanent deletion. Preserve the redirect until the verification period and your own checks are complete.

Analytics and the RedCircle limitation

RedCircle's official third-party prefix guide supports only named providers on Pro or higher. It lists Spotify Ad Analytics or Podsights, Podtrac, Podscribe, Claritas, and Magellan. The page says no other prefix URLs are supported, so Podder cannot be installed on a RedCircle-hosted feed.

Do not select another provider and paste a Podder URL, edit episode enclosures by hand, or create a second modified feed. Our RedCircle prefix troubleshooting guide explains the allowlist and the native reporting option.

A host move can make a later Podder installation possible if the destination supports custom prefixes. Keep RedCircle as the labeled historical source, mark the host cutover, and mark the prefix installation as a separate event.

Chartable is gone, and Podder is where its users landed. After the show is stable on a compatible destination, start a fresh Podder Analytics series.