How to move podcast from Megaphone to a new host

To move podcast from Megaphone, import and inspect the full show at your destination host before requesting a redirect. An Org Admin must contact Megaphone through Live Chat or email, provide the new RSS URL, and give 48 hours of notice. After Megaphone confirms the change, test the old feed, existing listings, and your next release.

You do not need to leave Megaphone to add Podder. Megaphone supports a custom analytics prefix through its podcast settings. Move only when another hosting or ad-operations requirement makes the destination a better fit.

Before you move podcast from Megaphone

Choose the destination and check it against the reason for leaving. Megaphone often sits inside a wider network workflow, so compare publishing permissions, user roles, ad markers, campaign operations, dynamic insertion, reporting, integrations, and support. Our podcast hosting company comparison is a starting point if the destination is not settled.

Identify the Megaphone Org Admin who can authorize the redirect. Megaphone's official instructions limit redirect requests to that role. Do this before the planned cutover, not after the destination import is waiting.

Gather the current Megaphone RSS URL, destination account, source audio where available, artwork, and access to claimed directory dashboards. Save the reports, campaign records, trafficking notes, and billing details your team needs. Public RSS can move published show information, but it does not carry private dashboards, user permissions, contracts, or ad operations.

Create a handoff record that both hosting teams can read:

The broader podcast host switching guide covers the checks shared by every move. This guide keeps the Megaphone request and verification work explicit.

1. Prepare advertising and private operations

List the parts of the show that do not live in its public RSS feed. These may include draft episodes, scheduled releases, user roles, campaign settings, ad markers, dynamic insertion rules, private feeds, and network reports. Assign an owner and destination for each item.

Do not assume an RSS importer will recreate the advertising setup. Confirm how the new host treats existing audio, markers, baked-in spots, and dynamically inserted material. If the organization has active campaigns, align the cutover with the people responsible for delivery and reporting.

Save a final Megaphone reporting snapshot before the move. Label every export with its date range and source. The destination will start its own series, and those values may use different processing rules.

2. Import the show at the destination

Keep Megaphone active while the destination imports the podcast. Create the show at the new host and provide the current public RSS URL. Let the catalog finish copying before asking Megaphone for the redirect.

Count the imported episodes and inspect the edges of the archive. Play a recent episode and an older one. Check titles, descriptions, publication dates, artwork, season and episode numbers, show-note links, audio duration, and enclosure behavior.

Fix skipped episodes and broken audio now. Megaphone is still serving the original feed, which gives both support teams a stable source for comparison.

Avoid publishing from both platforms. Keep Megaphone as the active publishing source until the destination catalog and operations are ready, then make one cutover.

3. Compare the Megaphone and destination feeds

Open both feeds in an RSS viewer. Compare show title, author, description, categories, language, artwork, and explicit-content setting. Then inspect episode titles, publication dates, descriptions, audio enclosures, and GUIDs.

Apple's official guide to changing hosting providers says GUIDs should not change during migration. It also asks creators to preserve metadata, audio, and season and episode numbers. If the destination assigns a new GUID to an old episode, a directory may treat that episode as a second release.

Keep the show identity stable during the cutover. A rebrand, artwork change, or archive cleanup can wait until a normal episode has distributed from the destination. That makes directory problems easier to trace.

For a plain explanation of the data being compared, what an RSS feed is shows which public records travel with the show and which account records stay behind.

4. Ask Megaphone to create the 301 redirect

Megaphone does not document a self-service redirect button. Its official redirect-to-a-new-host instructions tell an Org Admin to contact Megaphone through Live Chat or email.

Send the request at least 48 hours before the planned change. Include:

• the organization and podcast name
• the current Megaphone RSS URL
• the destination RSS URL
• the intended cutover time
• the Org Admin's contact details

Megaphone says it needs 48 hours of notice and the new feed URL. Keep the request focused, and ask for confirmation when the redirect is active.

Before sending, open the destination RSS address and confirm that it serves the intended show. Make sure it does not redirect back to Megaphone. A redirect loop would prevent apps and subscribers from reaching a stable feed.

Once Megaphone applies the redirect, publish future episodes from the destination. Do not return to Megaphone for a new release unless both hosts have agreed on a rollback plan.

5. Verify the old feed outside the dashboard

Open the old Megaphone RSS URL in a private browser window or inspect it with a redirect checker. It should resolve to the destination feed rather than a login page, website, or error response. Record the time, old URL, final URL, and result.

Check the show in Apple Podcasts, Spotify, and the listening apps that matter to your audience. Confirm that one listing remains, the catalog is complete, artwork is correct, and several old episodes play. Do not submit the destination feed as a new podcast, because that can create a duplicate listing instead of moving the current one.

Apple says a 301 redirect from the old hosting provider migrates followers, including listeners outside Apple Podcasts. Its Apple Podcasts Connect feed-edit route is an alternative when you no longer have access to the old feed, not an extra step for every successful host redirect.

A confirmation from support and a working browser redirect are separate pieces of evidence. Keep both in the migration record.

6. Publish one normal episode from the destination

After the old feed resolves correctly and major listings look stable, publish the next regular episode from the destination. Keep the usual schedule and format so an unusual release does not complicate the test.

Confirm that the new episode appears once in the main listening apps. Compare its title, duration, artwork, description, and audio. Check the destination dashboard for new activity without expecting its values to match Megaphone exactly.

Review your website and production systems too. Replace Megaphone players, direct media links, and automation inputs where needed. A feed redirect can move subscribers while a manually embedded player remains tied to Megaphone.

Keep Megaphone access while you finish these checks. If an episode is missing or duplicated, both the original and destination records help support identify where the paths diverged.

7. Close out the Megaphone side

Do not treat redirect confirmation as the whole migration. Before ending the old service or removing access, confirm:

• The old Megaphone feed resolves to the destination feed.
• The imported catalog is complete and playable.
• Existing directory listings remain intact and appear once.
• A new episode has distributed from the destination.
• Advertising and private-feed requirements have new owners.
• Reports, campaign records, and billing documents are saved.
• Website players and production automations use the intended routes.

Ask the Org Admin and ad-operations owner to approve the record. A host move affects more than the person who uploads episodes when Megaphone is part of a network workflow.

Analytics after the Megaphone move

The feed redirect does not transfer Megaphone's reporting history. Keep that history as a closed, labeled source and start the destination series on the cutover date. Downloads from two providers should not be added together unless their definitions and periods support that comparison.

If analytics is the only reason you considered moving, stay on Megaphone and use its custom-prefix control. Megaphone's official Custom Prefixes guide places it under the selected podcast's Settings > Megaphone Settings > Feed Prefixes. Enable the custom-prefix toggle, enter the exact value, and save. The saved prefix should appear before each enclosure URL in the RSS feed.

Our Megaphone prefix troubleshooting guide covers the feed and playback checks. Podder begins measuring new requests after installation; it does not import old Megaphone data.

Chartable is gone, and Podder is where its users landed. If Megaphone still meets your hosting and ad-operations needs, start Podder Analytics and install the custom prefix without moving the show.