Migrating from Supercast
Supercast and Benecaster do the same job — private podcast RSS delivery with subscriber authentication — which makes this one of the cleanest migrations you can do. There’s no audio hosting complication: Supercast users already serve audio from a podcast host. The migration is purely about moving subscriber access.
What You’ll Need
- A Supercast subscriber export (CSV) from your Supercast dashboard
- The Migration Wizard — one wizard handles all supported platforms including Supercast. Included free with Growth, Pro, Multi-Show, and Studio; available separately for Starter.
- Your Benecaster show and tiers set up before you begin
The Migration Flow
- Export your subscriber list from your Supercast dashboard as a CSV
- In your WordPress admin, go to Benecaster → Subscribers → Import and upload the CSV
- If the wizard recognizes the format, it pre-fills the column mappings for you — confirm them and continue. If it doesn’t, it asks you to match your columns to Benecaster’s fields once, which takes a minute
- Map your Supercast plan names to your Benecaster subscription tiers
- Set a grace period — how long subscribers can access their old Supercast feed while transitioning over
- The wizard creates Benecaster accounts and private feed URLs for each subscriber and sends the migration email sequence
See Grace Periods Explained for guidance on how long to set the window, and Migration Dashboard for tracking progress and re-sending to non-completers.
Explicit-Content Field
Supercast exports carry no explicit-content field, so imported episodes are left on Inherit from show and take whatever your show’s Explicit setting says.
Benecaster does not guess a value here. Defaulting imported episodes to “clean” because the source said nothing would be inventing a fact — and on a show marked explicit it would silently override the entire imported catalogue the wrong way.
Check the show-level Explicit value before publishing. Set it in Shows → Settings → Feeds; it is what your whole imported catalogue reports to Apple Podcasts and other directories. If the show is mostly explicit with a few exceptions, set the show to Yes and mark those episodes No individually.
See Show Settings and Creating Episodes.
Feed URLs
Supercast feeds are served from Supercast’s domain. Your subscribers’ existing feed URLs will stop working when your Supercast account closes. The migration email sequence sends each subscriber their new Benecaster feed URL — they update it once in their podcast app and they’re done.
If you’re using a custom domain for your Supercast feed — for example, feed.mypodcast.com pointing at Supercast’s infrastructure — you can preserve feed URL continuity so subscribers never need to update anything. See Preserving Your Feed URL with a Custom Domain below.
Preserving Your Feed URL with a Custom Domain
This applies only if your Supercast feed is currently served from a domain you control — a subdomain you set up with a CNAME record pointing at Supercast. If your feed URL is on feeds.supercast.tech, skip this section.
How to check: Look at the RSS feed URL your subscribers currently use. If it’s something like feed.mypodcast.com/..., that’s a custom domain you control. If it’s feeds.supercast.tech/..., it’s Supercast’s domain and this section doesn’t apply.
If you have a custom domain:
- Confirm your Benecaster show’s feed is accessible at the correct path on your WordPress site
- Before closing your Supercast account, update the CNAME record for your feed subdomain to point at your WordPress site instead of Supercast
- Allow time for DNS propagation (typically a few minutes to a few hours depending on your TTL)
- Test that your Benecaster feed resolves correctly at the custom domain before proceeding
- Run the subscriber migration — your subscribers’ existing URLs continue working automatically, no action required on their end
Do the DNS update before you close your Supercast account. Once Supercast is closed there’s no graceful window — update DNS first, verify it resolves to your Benecaster feed, then close the account.
See Also
Need this built rather than just documented? See our services →