Too hard to switch: how to handle it on a cold call
Agree that switching is work. Then ask what the current setup costs them each month, and size the change against that number rather than against zero.
- “It would be too much hassle to switch.”
- “We have years of data in the current system.”
- “Nobody here has time for a migration.”
- “We only just rolled out what we have.”
- “The team would never go for another change.”
Karen says a version of this one in the first minute. Hear it on a free three-minute call, scored, no account.
Agree with them. Switching is work, and saying otherwise costs credibility. Then ask what the current setup costs them each month, in time or money. Once they put a number on it, size the change against that number instead of against zero. This works because the prospect is comparing the effort of switching with doing nothing, and doing nothing looks free. Your job is to make the current cost visible, in their words.
What they actually mean
Sometimes the fear is real. The last migration took four months and the person on the phone carries the scars. Sometimes "too hard to switch" is a stand-in for "happy enough", and the switching cost is the first excuse to hand. And sometimes they signed a contract six months ago and are locked in whether they like the tool or not.
The honest version will tell you what went wrong last time and will answer the cost question, even roughly. The brush-off stays vague. "It's just a lot", with no detail, and no figure for what the current setup costs them. When someone will not estimate the cost of what they have, they are not weighing a switch, and the call is closer to happy with what we have than to a real objection about effort.
Three ways to handle it
Agree, then ask the monthly cost
Use this first. The agreement is sincere and the question does the work.
You are right, switching is work. Roughly, what does the current setup cost you each month, counting the time people spend on it?
Ask about the last switch
Use this when they mention a previous migration. It turns fear into a list.
What went wrong last time? I would rather know now than find out in week three.
Size the change against their number
Use this once they have given you a cost. Put the two figures side by side.
So that is about two days a month across the team. The switch is about a week, once.
Against that, does it still look like a lot?
An exchange that works
Prospect: Honestly, it would be too hard to switch. Everything is in the current tool.
Rep: Agreed, switching is work. Rough guess, what does the current one cost you each month, counting people's time?
Prospect: Hard to say. The managers spend a day a week sitting in on calls because the tool does not tell them anything.
Rep: So four manager days a month, every month, to get what the tool should be giving you.
Prospect: When you put it like that.
Rep: The switch is about a week of one person's time, once. I would like to show you the setup next to your four days. Twenty minutes on Tuesday?
Prospect: Tuesday afternoon works.
Rep: Tuesday at three. I will send the invite.
A coach scores this well on discovery and objection handling. The rep agreed without flinching, asked one question that produced a number, repeated it back, and only then put the switch next to it.
The mistakes that lose the call
| What reps say | Why it fails |
|---|---|
| "Our migration is really easy" | Nobody believes it, and it argues with the prospect's own experience of the last one. |
| "You're losing so much by not switching" | States the cost before the prospect has named it. Their number is the only one that counts. |
| "We can import all your data" | Answers a question nobody asked. The fear is almost always about people and habits, not data. |
| "Most of our customers switched from your tool" | Lands as a dig at the decision they made. |
| Dropping the subject and listing features | Leaves the objection standing. It comes back at the end with more weight. |
Each of these tries to shrink the switch. The approach that works leaves the switch the same size and makes the status quo bigger. It is a different fix from too expensive, and both appear in our list of common cold-call objections.
Say this, not that
| Instead of | Say |
|---|---|
| "It's actually really simple to migrate" | "You are right, it is work. What does the current setup cost you each month?" |
| "You'd save loads of time" | "So that is four days a month. The switch is about a week, once." |
| "Our onboarding team handles everything" | "What went wrong last time? I would rather know now." |
| "Don't worry about the switch" | "Against four days a month, does a week still look like a lot?" |
Questions people ask
- What do you say when a prospect says it's too hard to switch?
- Agree that switching is real work, then ask what the current setup costs them each month in time or money. Once they give you a number, size the switch against that number. Most reps make the mistake of sizing it against nothing.
- How do you handle switching cost objections on a cold call?
- Do not promise an easy migration. Ask about the last switch and what went wrong, then ask what the current tool costs them every month. The comparison that wins is one week of effort once against a recurring cost they named themselves.
- Should you mention data migration when a prospect worries about switching?
- Only if they raise it. Most switching fear is about people and habits, not data. Answer the question they asked, which is usually whether the change is worth the disruption.
Updated 1 Oct 2026. The position on this page is the one our coach scores against.