How to move podcast from Acast to a new host

To move podcast from Acast, prepare the complete show at your destination host before redirecting the feed. Export the Acast listening and revenue records you need, arrange an ad-free import if the show uses Acast Ads, then use Show redirection to point the old feed at the new RSS URL. Verify directories before requesting account deletion.

Acast treats the feed redirect, plan cancellation, and account deletion as separate actions. The redirect moves podcast distribution. It does not transfer your Acast dashboard, revenue history, team settings, advertising setup, or third-party analytics data.

Before you move podcast from Acast

Pick the destination and confirm that it supports the publishing and monetization work your show needs. Compare storage, private content, team permissions, dynamic advertising, analytics, and integrations. Our podcast hosting company comparison can help if the destination is not settled.

Keep the Acast feed live while the new host imports it. Gather the old feed URL, destination account, original audio where available, show artwork, and access to every directory dashboard where the podcast is claimed.

Acast's official redirect and account guide adds two important preparations. If you use Acast Ads, contact Acast so dynamic ads can be disabled and your new host can import an ad-free feed. Acast also tells creators to export listening and revenue data before redirection because access to that data is lost afterward.

Build a short handoff record before changing anything:

For the general checks that apply to any provider, keep how to switch podcast hosts open beside this Acast-specific process.

1. Prepare the feed for import

If the podcast uses Acast Ads, ask Acast to disable the dynamic ads before you run the destination import. This avoids copying ad-filled versions into the new host's permanent episode files. Wait for confirmation rather than assuming an account toggle has removed every dynamic insertion.

Review other Acast-only features separately. Drafts, scheduled episodes, private feeds, subscriber access, campaign settings, team roles, and hosted web pages may not live in the public RSS feed. Decide which items need a manual copy, a new configuration, or an archive.

Export the reporting records you need now. Save the reporting range and export date with each file. Those labels will explain why the old series ends and the destination series begins on different systems.

2. Import the podcast at the destination

Create the show at the new host and use its import tool with the active Acast RSS URL. Let the process finish while Acast still serves the complete feed and audio.

Count the imported episodes and inspect different parts of the archive. Play a recent episode and an older one. Check show notes, artwork, publication dates, season and episode numbers, and audio duration. If the importer skipped an item, fix it before applying the redirect.

The destination cannot be another Acast RSS feed. Acast's redirection flow expects a feed hosted elsewhere, so confirm the new URL and hosting provider before continuing.

3. Compare the feeds before redirection

Compare show-level fields in the Acast and destination feeds. The title, author, description, categories, language, explicit-content setting, and artwork should remain consistent during the move.

Check episode GUIDs as well as visible titles. Apple's hosting-provider migration guidance says the new host should preserve GUIDs, metadata, audio, and season and episode numbers. A changed GUID can make a directory treat an imported episode as a new item.

Delay rebranding and archive cleanup until the destination has distributed a normal episode. Keeping the content stable makes a duplicate or missing episode easier to trace.

If the feed mechanics are unfamiliar, what an RSS feed is explains which public records move through RSS and which account records stay behind.

4. Set Acast's show redirect

Once the destination feed is complete:

1. Open the show in Acast.
2. Go to Settings.
3. Open Show redirection.
4. Check I have prepared my show for import and redirection.
5. Paste the destination RSS feed URL.
6. Save the redirection.

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

Publish every future episode from the destination host after the redirect. Alternating between Acast and the new host can create conflicting catalogs and make directory checks inconclusive.

5. Update Spotify for Creators

For an externally hosted podcast, Spotify asks you to update the RSS URL and hosting provider after changing hosts. Its RSS and hosting-provider instructions give this route:

1. Log 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 new RSS URL, confirm the new provider, and submit.

This directory update is separate from Acast's redirect. It tells Spotify which host now owns the externally hosted show.

Apple normally follows a major host's 301 redirect without a routine feed edit in Apple Podcasts Connect. Check the listing and use Apple's manual feed change only when the old feed cannot provide the redirect.

6. Verify the listener path

Open the old Acast RSS URL outside your signed-in session. It should resolve to the destination feed, not an Acast account page or a missing-page response.

Then inspect the show in the listening apps that account for your real audience. Confirm that the show appears once, existing episodes remain in order, artwork is correct, and audio plays. Do not submit the destination feed as a new show because that can create a duplicate listing.

Publish the next ordinary episode from the destination host. Check that it appears once in Spotify, Apple Podcasts, and the other apps you track. Confirm the title, notes, duration, and audio file. The destination analytics should begin recording new activity, but that does not mean the Acast history moved.

Review your website and production systems too. Replace old Acast embeds or media links where needed, and update any automation that expected an Acast URL.

7. Handle cancellation and deletion separately

Acast says the redirect does not automatically cancel or delete the account. Choose the account action only after the feed and directory checks pass.

Acast's current guidance says to submit account deletion two weeks after redirecting. That delay gives directories time to follow the feed change. Before requesting deletion, confirm:

• The old Acast feed resolves to the destination feed.
• The imported catalog is complete and playable.
• Spotify shows the new feed and hosting provider.
• Apple and other important directories retain one listing.
• A new episode has distributed from the destination.
• Listening and revenue exports are stored with their dates.
• Old embeds and integrations have been reviewed.

If one item fails, retain access to both hosts while support traces the problem. Redirecting first and deleting later preserves your diagnostic options.

Reporting after the Acast migration

Acast does not support show-level third-party RSS analytics prefixes. Its stats intermediary policy distinguishes those services from advertiser tracking pixels and says Acast does not support prefix intermediaries.

That means the host move and a later analytics installation are two different jobs. Podder does not migrate the Acast feed, episodes, listening reports, or revenue records. After the destination host completes the import and Acast provides the redirect, a compatible host can add the prefix for future requests.

Use the saved Acast exports as a closed historical source. Mark the destination cutover and any prefix installation date in your reporting notes. Acast analytics guide can help you label the old host metrics before access ends.

Once distribution is stable at a compatible host, you can start a new Podder Analytics measurement series.