Your audience never sees it. A handover between production teams is invisible from the outside, right up to the week an episode doesn’t land. That is the real risk in switching podcast production companies, and it is the part almost nobody writes about. Ownership gets all the attention. Cadence is what actually slips.
I lead growth at a full-service podcast production agency, so I sit on the first call with shows that are unhappy somewhere else. Changing a podcast production company is rarely a technical problem. It is a scheduling problem wearing a technical costume. Below are the five questions I get asked most about it, in my own words, with the parts we have learned the hard way.
What people actually switch for
It’s almost never just the audio. Here’s an example of a client making a production provider move from this year, and what the first call sounded like.
Earlier this year, a popular lifestyle and entertainment podcast moved over to Resonate. On our first call, I asked them two things: what’s working in your podcast right now, and where do you feel bogged down, unsure, or unsupported?
The answer wasn’t really about the finished episodes. Those were…ok. The problem was everything it took to get there. They were writing extensive editing notes every week, and because they didn’t always get the same editor, they kept repeating the same style feedback. Communication lagged. Edits that should’ve taken a few days stretched past a week. For a weekly video show, that’s not workable.
The bigger issue was direction. They had real questions their production partner couldn’t answer:
- Are we booking the right guests?
- Are we covering topics our audience actually cares about?
- Do we even know who our audience is?
- How do we reach more people?
The show was succeeding, and they had no idea why. Some episodes took off on YouTube and others fizzled. They wanted to understand what was working so they could do more of it on purpose, not just hope lightning struck again.
What made this particular client make the switch was knowing they’d have a producer whose whole job is to manage and grow their show. Our producers sit down with clients every 90 days to go over the numbers. Nobody’s hiding from the metrics. Before any of that, we do a full audit of the existing show so we understand where it started, where it’s been, and where it could realistically go based on that client’s goals. Then we set benchmarks.
So yes, we edit audio and video. But that’s not what they solely hired us for.
Read that list again. Not one of those questions is about editing quality. The finished episodes were fine. The show was winning and the team could not say why. That’s the usual shape of a switch.
And this matters for planning, because it changes what the handover has to carry. If you leave over audio quality, you need files and a new editor. If you leave over direction, you need files, a new editor, and someone to rebuild the plan while the weekly show keeps going out. The second one is a bigger job.
The two paths: overlap or clean break
This is the choice that decides whether you miss a week. Here is what nearly got lost in that move.
Release cadence. Existing podcasters don’t always think about how they’ll keep publishing on schedule while a new team learns their show.
There are usually two paths. Some shows overlap, keeping their old provider for a few episodes while onboarding with the new production partner. Others pull all their assets, make a clean break, and try to keep pace without missing a week. The second one is riskier than it sounds. This show chose to make a clean break. Before the switch, we asked them for extra recording time so they could batch episodes and get ahead. We also had them gather all their creative assets up front, so we had every piece we needed on day one.
On our side, we gave our production team a heads-up that a big batch of episodes was coming. That planning let us keep their weekly releases on schedule while we worked in the background on a relaunch. For us, a relaunch can mean refreshing creative assets, changing up the show format, and introducing new messaging. Same show, same audience, just a sharper version of it, backed by strategy.
At Resonate, we aim to keep clients about a month ahead on content, so there’s room to breathe when life happens. If you’re planning a switch, I’d recommend having at least two or three finished episodes in the bank before you give notice. That buffer covers onboarding without your audience noticing a gap.
Two paths, and most people never hear that there is a choice. Overlap costs money for a month. A clean break costs nothing and risks your podcast release schedule. Pick on purpose, not by default.
The line I would underline is the last one. Two or three finished episodes in the bank before notice goes out. Not planned. Not recorded. Finished, approved, ready to publish.
Bank the buffer before you give notice
Here is how I would turn that into a plan with dates. The order being the whole trick.
- Count your gap. Work out how many finished episodes you need to cover onboarding. At least two or three episodes is what I recommend.
- Book the extra recording time first. One longer session can produce two or three episodes.
- Get those episodes finished, not just recorded. A recorded episode is not a published episode.
- Collect your assets while you are still a paying client. Requests get answered faster before notice than after it.
- Warn the incoming team that a batch is coming. A production team that expects ten files in one week plans for it. One that gets ten files as a surprise does not.
- Then, give notice.
We aim to keep clients about a month ahead for the same reason. A buffer is not about being organized. It is about having somewhere to put a bad week. People get sick. Guests cancel. A file comes back wrong. Let’s plan for it.
I call this the Continuity Buffer, and it has one rule. The buffer is built before the switch, never during it. Once notice is out, your old provider has no reason to hurry and your new one has no history with your show. That’s the worst moment to be starting from zero.
Two numbers, and they are not the same number. Before giving notice, I recommend at least two or three finished episodes. After the switch, about a month ahead is where I want a client sitting. The first is a bridge over onboarding. The second is how we run once the new team has the show.
| Path | What it costs | What it protects | Pick it when |
| Overlap for a few episodes | One extra month of your old fee | Your release day, with no buffer needed | Notice is already out, or you cannot get extra recording time |
| Clean break with a banked buffer | Extra recording time, and the work to finish ahead | Your release day and your budget | You can book one longer session before notice |
| Clean break with no buffer | Nothing up front | Nothing | Hard to recommend. The risk lands on your release day |
Run the relaunch in the background
The second half of that is the part I keep coming back to. Weekly releases in the foreground. The rebuild behind them.
Most teams do this the other way around. They pause the show to fix the show. Then the pause runs long, the habit breaks, and the relaunch has to win the audience back instead of just serving it.
None of that work needs to be public on day one. The feed keeps its weekly rhythm while the new look gets built, tested and approved. Then it ships on an episode you chose.
That only works if the buffer is real, because the relaunch work and the weekly work compete for the same people. If you want to know who is holding that line, read what a podcast producer does.
One anti-pattern to name here: the Silent Relaunch. New art, new format and new music all land in one week with no episode explaining it. Listeners notice a stranger in the feed. Tease the relaunch, give the listener something to be excited or curious about.
A continuity timeline for the switch
Here is the shape I would plan on for a weekly show. Adjust the weeks to your cadence.
| When | Your job | Your incoming team | Risk if you skip it |
| Four weeks before notice | Book extra recording time. Confirm who owns the hosting account. | Review the existing show and set goals | You find out the account is not yours at the worst moment |
| Three weeks before | Record the batch. Request source files and licenses. | Flag the incoming batch to production | Assets arrive late, after you stop being a client |
| Two weeks before | Approve the batch. Two or three episodes finished. | Build style notes from your approved episodes | The same feedback gets rewritten every week |
| Notice week | Give notice in writing. Confirm the handover date. | Take over publishing from the buffer | A gap in the feed while files move |
| Weeks one to four after | Publish from the buffer. Rebuild the buffer. | Run weekly output and start relaunch work | You are living week to week again |
| Around day 90 | Review the numbers against the goals you agreed at the start | Report on what changed | Nobody knows if the switch worked |
Moving a podcast to a new host often rides along with this, because many providers bundle hosting. If so, do the podcast migration on a week you are publishing from the buffer, never on a release day. Our look at podcast hosting platforms covers what the main options do.
The pre-notice ownership checklist
None of the above matters if you cannot take your show with you. Here is what I tell clients to get in writing before giving notice.
Written confirmation that you own your stuff, and a full handoff of it. That includes:
- Cover art and brand files (source files, not just a JPEG)
- Intro and outro audio
- Music, plus proof of license. If your provider licensed the music under their account, you may not be allowed to keep using it. Check this first.
- Raw and edited episode files
- Logins for your hosting platform, YouTube channel, and any streaming accounts
The big one: make sure your hosting account and RSS feed are in your name. If your provider owns the account your feed lives on, moving it gets messy, and you can lose subscribers in the process. Sort that out before anyone gives notice.
The music line is the one that surprises people. A license bought under a provider account can leave with the provider. Your back catalog stays up, but your next episode may need new music, and your intro stops matching. Check the license holder, not just the file.
Podcast feed ownership is the item with no workaround. Pacific Content makes this argument in a post on who owns your podcast, and it still holds. A feed at a URL you control never needs a redirect at all.
We do not re-argue the mechanics here, because other pages of ours already do. Working with a podcast production company holds a section on who holds the keys, meaning the hosting account, the Apple Podcasts Connect roles and the feed itself. It also holds a section on how to end an engagement without losing the show, with the feed-move steps and the terms to put in your agreement. The agency versus in-house framework holds who owns the files if you switch later, and how to hand over without losing your voice. And what a production company actually does holds the questions to settle before you sign. Those three go deeper than this page on ownership. Read them for the contract language.
Five questions for your current provider
Before you plan a switch, find out whether you need one. Five questions, and the hesitation tells you as much as the answer.
- Who owns my hosting account and RSS feed? If they hesitate, that’s your answer.
- What’s driving my best and worst episodes? A good partner can explain the why, not just send a download report.
- Will the same person edit my show every week? Consistency is what keeps you from rewriting the same notes forever.
- What’s your turnaround time, and is it in our agreement? “We’re usually pretty quick” isn’t a timeline.
- What’s the plan for the next 90 days? If nobody’s thinking about growth, you’re paying for editing and hoping for the rest.
Our 10 questions to ask a podcast agency is the longer version of this, built for vetting the next provider rather than testing your current one. It holds a ten-row scorecard with a good answer and a red flag beside each question. Use that one when you are shopping, and this one when you are deciding whether to shop.
How to tell it is not just a new logo
This is the objection I hear most from people who are unhappy but nervous.
“How do I know this won’t just be the same thing with a different logo?” Basically, they’re worried they’re getting lip service.
Honestly, I get it. I’ve been a customer for most of my adult life, and I’ve heard plenty of promises that didn’t survive the first invoice. So I don’t ask them to take my word for it. I show them.
I walk them through the actual people they’ll work with: a producer, a client success manager, and me, the person on the call. I show them our workflow and the web app we built to keep shows organized, so they can see how feedback, files, and deadlines are handled before they sign anything.
I also remind them we didn’t pop up last week. We’ve been in podcasting for going on 15 years. We’ve made our mistakes, learned from them, and built our process around what actually works.
What I take from that is a test you can run on anyone, including us. Ask to see the workflow before you sign, not after. Ask for the names of the people on your show. Ask what happens when you leave a note on an episode: where does it go, who reads it, how is it tracked.
A provider who can show you that has a process. A provider who describes it has a pitch. The difference shows up in week three, which is exactly when your buffer is keeping you safe.
What the feed move does and does not cover
Now the technical part, kept short, because the published guides handle it well. When people search how to switch podcast hosts, this is what they find.
Transistor, in its guide to switching podcast hosting platforms, says a 301 redirect on your old feed takes effect as soon as it is set, with no downtime for listeners. It also says Apple can take 24 to 48 hours to pick up a new feed. And it says analytics do not move between hosts, so you should export your old numbers first. That last point matters more than it sounds during a provider switch, because your new team needs a baseline.
Two separate questions get mixed up here. The first is when you can close the old hosting account, and Transistor says wait two weeks. The second is how long the redirect itself should live. Transistor sets no limit on that. The Audacity to Podcast, in its guide to moving a feed, says keep the 301 in place forever if you can, and at least 90 days if you cannot. I follow the longer advice. A redirect costs nothing to leave running.
They also disagree on directories. School of Podcasting says you do not need to resubmit to Apple or Spotify because the redirect handles it. Guides from hosting companies tell you to update the feed URL in each directory anyway. Both can be true. The redirect usually works, and checking takes five minutes.
One rule everyone agrees on. Episode GUIDs must not change. The Audacity to Podcast says a GUID that changes by a single character makes apps treat the episode as new and download it again. So a changed GUID can force a re-download of your whole back catalog, which makes your download numbers meaningless for that period. Ask your incoming host to mirror GUIDs before the podcast rss redirect goes live, and spot-check your oldest and newest episode after.
We do not reprint the Apple steps here on purpose. Our page on working with a production company already carries them, including what to do when you have lost access to the old feed. Switching podcast hosts without losing subscribers is a solved problem. Changing podcast hosting is the easy half of the day.
What I cannot tell you
Some of this is outside anyone’s control, and I would rather say so.
- I cannot tell you how your old provider will behave after notice. Most are professional. Some go quiet. Build the buffer as if yours will go quiet.
- I cannot promise zero subscriber loss. A correct redirect keeps followers, but every guide I read hedges on the edges, and so do I.
- I cannot tell you your license terms. Only the agreement and the license holder can.
- I cannot tell you whether a format change will land. We test, we read the numbers at 90 days, and we change course if it did not work.
- I can tell you what a missed week costs, because it is the one thing in this list you control.
If you want this run rather than described, it is part of our ongoing podcast management scope and the podcast management work we do. You can also book a call and we will map your switch against your release day before you give notice.
Conclusion
Protect the release day. Everything else in a switch can be fixed later, including the art, the format and the host. A gap in the feed is the one thing your audience sees.
So do the boring part first. Book the extra session, finish the episodes, collect the files, settle the account names. Then give notice. The switch becomes a scheduling exercise instead of a rescue.
Strategy-first. Production second. Growth always.
