Multi-channel AI outreach is liveSee it in action
Migration & Switching

The Migration Support Script That Eliminates Switching Anxiety

The biggest barrier to switching tools is rarely features or pricing — it is fear of disruption. Prospects worry about data migration, team retraining, and the risk of downtime during transition. A short, direct video that maps out exactly what the migration looks like, what your team handles, and how long it actually takes transforms the conversation from risk assessment to implementation planning.

When to use this script

Use this script after a prospect has expressed interest but stalled due to concerns about the complexity or risk of switching from their current solution. It also works proactively when you know your ICP typically uses a specific legacy platform.

AEs selling to prospects currently locked into a legacy platform or long-term contractSales engineers addressing technical migration concerns from IT or engineering stakeholdersSDRs targeting companies whose job postings or review activity signal frustration with a current tool

What does the Migration / Switching Support script look like?

Script Template
Opening

Hey {{prospect_name}}, I want to address something directly — I know one of the reasons {{company_name}} hasn't moved forward yet is the question of what it actually takes to migrate from {{current_tool}}.

Body

I've walked dozens of {{industry}} companies through exactly this transition. Here's what it actually looks like for a team your size: week one, we handle all data migration from {{current_tool}} with zero manual work from your team. Week two, we run a training session for {{team_size}} people that takes about two hours. By week three, {{company_name}} is live and running. The full downtime is typically {{downtime_estimate}}. And if anything goes sideways, we have a rollback option that takes less than an hour.

Closing

{{prospect_name}}, the migration is the part most people worry about the most and remember the least. It's genuinely the easiest part of this process. Would it help to have a 30-minute call with our implementation team to walk through your specific setup?

How can I make the Migration / Switching Support script work better?

Name the Fear Before They Raise It

Proactively acknowledging migration anxiety is more persuasive than waiting for the objection. It signals that you've done this before and have thought about their specific concern — which is itself a trust signal.

Use Specific Timeframes, Not Vague Promises

Saying 'week one we handle X, week two we do Y' is far more credible than 'it's easy and fast.' Prospects who can visualize a calendar-week migration plan feel far more comfortable committing.

Offer a Rollback Safety Net

Mentioning that a rollback option exists if things go wrong removes the binary feel of the decision. 'You can always go back' is one of the most powerful objection-resolvers in a migration conversation.

What are the variations of the Migration / Switching Support script?

The Contract Overlap Version

For prospects locked into a current contract with time remaining.

Tweak: Address the contract directly: '{{prospect_name}}, I know you still have {{months_remaining}} months left on your {{current_tool}} contract — let's talk about how to time the migration so there's no dead period and how we handle the cost overlap.'

The IT Stakeholder Version

For technical evaluators whose primary concern is data security and system integrity.

Tweak: Lead with technical specifics: '{{prospect_name}}, I want to share our migration runbook specifically for transitioning from {{current_tool}} — it covers data mapping, API handoffs, security protocols, and the rollback procedure so your IT team has everything they need upfront.'

The Team Adoption Version

For managers worried about user adoption and change management.

Tweak: Focus on people, not systems: '{{prospect_name}}, the technical migration is handled by us — but I know what you're really worried about is whether your team will actually use the new tool. Here's how we've solved adoption at {{reference_company}}.'

What performance can I expect from this script?

72%
Of stalled deals that cite migration risk close after receiving a migration support video
2.4x
Faster deal progression when migration timeline is communicated proactively
91%
Customer satisfaction rate with migrations managed by a dedicated implementation team

Frequently asked questions

When is the right time to send a migration support video?

Send it as soon as migration complexity is raised as a concern — in a reply, on a call, or via intent signals. Waiting too long lets the objection calcify into a decision to stay with the current vendor.

Should I downplay or address migration risks honestly?

Address them honestly. Overpromising on migration ease destroys trust when the reality is messier. Acknowledging realistic challenges while explaining your support process is far more credible and effective.

What if my product genuinely has a complex migration process?

Be transparent and show that the complexity is manageable. Break it into steps, show what your team handles versus what the customer handles, and reference companies who successfully made the transition with similar complexity.

How do I handle a prospect who is under contract with a competitor?

Don't ask them to break the contract — ask them to start planning now so the transition is seamless when the contract expires. Offer a low-commitment pilot or integration test that can run in parallel during the overlap period.

Can migration support videos be used after the deal closes?

Absolutely. A post-sale migration kickoff video from the implementation lead reinforces confidence in the decision and accelerates the technical onboarding by giving the customer a human face to the process.

Remove the Last Obstacle Between Your Prospect and a Decision

Outvid lets your team send personalized migration support videos to every hesitant prospect — walking them through the process in their context, with their current tools named, at scale.

We use cookies

We use essential cookies to keep the platform running, and optional cookies to improve your experience and measure usage. Privacy Policy