Preparing to Migrate
Welcome to Libsyn! If you already have a podcast show hosted on Audioboom and are looking to migrate to Libsyn instead, you have come to the right place. This tutorial will walk you through everything you need to know and do to seamlessly migrate your show and audience.
To break this down, there are a few steps that must be completed:
- You will need to sign up for a hosting account at Libsyn
- Your content will then need to be copied over to into that hosting account
- Proper redirects will need put in place for Apple Podcasts and the other directories and apps that support them
- For those directories that need manually updated, they will need to be contacted to update the feed URL.
The actual work can take just a day or two to complete in total. However, it can take up to 3-4 weeks for all directories and subscribers to update, so keep this in mind as you time when you want to begin this process and when you wish to close down your Audioboom hosted podcast.
Step 1: Sign up at Libsyn
To sign up for a Libsyn hosting account, please visit:
Once signed up, you should be able to log into your Libsyn account. At this point, we can copy your content into Libsyn.
Step 2: Copying Content to Libsyn
To get started, please contact the Libsyn Support team:
Provide the team with:
- Your show slug or the email used on signup
- Your current RSS feed URL
The support team will take a look at your current feed, make sure there are no issues, and import your content into your Libsyn show. They will let you know once that process is complete (how long this takes once the process is started depends on how much content you have on your show).
Step 3: Setting Up Redirects
Apple Podcasts requires 2 things to happen in order to properly update the feed URL they pull from and to update your subscribers.
They require a 301 redirect to be put in place at the old host. This points the old feed URL to the new Libsyn feed URL.
They also require a special new feed URL tag to be added to the new feed.
The two combined tell their system (their database and their applications) that your show has moved, and where it moved to. They will update to pull from the new location, and your subscribers will also update as soon as they next refresh your feed.
This also will update other apps that either pull from Apple Podcasts OR follow 301 redirects. A few examples (not an exhaustive list) of directories and apps that will follow the 301 redirect include:
- Apple Podcasts
- Google Podcasts
- Many others!
*Stitcher will follow the redirect while it remains online, but will not fully update their database so if the redirect ever goes offline, Stitcher will stop working. It is recommended that the feed URL either be updated in their Partner Portal or they be contacted directly to have the feed URL updated.
Setting Up a 301 Redirect in Audioboom
Unfortunately, Audioboom does not offer the ability to configure a 301 redirect inside its interface. Instead, you can contact Audioboom's team directly using their request form:
Provide them with your Audioboom feed URL and the Libsyn feed URL the Libsyn Support team provides you and request a 301 redirect be put in place.
Important Note: It is recommended the redirect remain in place for up to 4 weeks to ensure all your subscribers get a chance to update. For that reason, you may need to maintain your Audioboom account to make sure all changes take full effect.
The Libsyn team will add the New Feed URL tag to your RSS feed for you when they migrate your content.
Step 4: Addressing Directories that Need Manually Updated
As mentioned earlier, some directories will not follow the standard redirects in order to update.
In those cases, the directory will need to be contacted to have the feed URL updated manually. Those include:
- And others
If your show is already submitted to any of these directories, discuss this with your Libsyn Support agent. They will help you configure those destinations inside Libsyn and get those updated where appropriate.
Getting Additional Help
Have questions? Contact our support staff at firstname.lastname@example.org.