By Mehdi HassanSomeone searching for how to leave a product they pay for has already done the hard part: they've decided they're unhappy. What stops them is rarely your feature list. It's the thought of moving data, retraining a team and paying for two tools during the overlap. This guide shows how to build a page that answers those fears first.
What is a switch from competitor page?
A switch from competitor page is a landing page for people who already use a competitor and are considering moving to you. It differs from a competitor comparison page, which helps someone weigh two options, and from an alternatives page, which serves people still browsing a category. The switching page assumes the decision is half made and focuses on the move itself.
It sits inside the same family as your SaaS feature pages and uses the same design system, but its argument is different. A feature page says "here's what you get". A switching page says "here's how you get here without breaking anything". That shift changes which sections lead and which proof you use.
Page | Visitor's state | Main question | Lead section |
|---|---|---|---|
Alternatives page | Browsing a category | What else is out there? | Shortlist of options |
Comparison page | Choosing between two | Which one is better for me? | Side-by-side table |
Switching page | Ready to leave a tool | Is moving worth the pain? | Migration plan and proof |
Why don't unhappy customers switch?
Unhappy customers stay because switching feels riskier than staying frustrated. The risk is mostly practical: losing data, losing time and taking the blame if the move goes badly. A switching page that ignores those fears and only lists features leaves the real objection untouched.
Switching objection | What they fear | What the page must show |
|---|---|---|
Data | Records, history or files get lost | What you import, how, and what can't move |
Time | The move eats weeks of their team's time | Who does the work and a realistic range |
Retraining | The team resists a new tool | Onboarding help and how familiar the workflow feels |
Contract overlap | Paying for two tools at once | Your terms for switchers, if you offer any |
Blame | The champion looks bad if it fails | Proof from teams that switched and a rollback plan |
Rank these by what you hear on sales calls. The objection your team answers most often should be the second section on the page, right after the hero.
What should a switching campaign page include?
A switching campaign page should include a hero that names the frustration, a migration plan, proof from switchers, an honest comparison and a low-risk next step. Keep the order fixed so you can reuse the template for each competitor you target.
- Hero: name the pain in the visitor's words and promise a safe move, such as "Moving from [tool]? We'll bring your data with you."
- The move, step by step: three to five steps from first call to fully live, with who does what.
- What comes across: a short list of what you import and what doesn't, stated plainly.
- Proof from switchers: quotes or stories from customers who moved from the same tool.
- What changes day to day: a short, factual comparison of the workflows that differ.
- Commercial terms: any switching offer you genuinely provide, and contract notes.
- FAQ and CTA: the remaining objections and one next step, such as a migration call.
How do you show migration help without overpromising?
Show migration help as a concrete process with named responsibilities, and give timelines as honest ranges tied to scope. "We'll move you in a day" is a promise that breaks the first time a customer has messy data. "Most teams with a standard setup are live within your first billing cycle; larger accounts are scoped on a call" is only useful if it's true for you, so use your own numbers.
Pros
- Hands-on migration help removes the biggest switching objection
- A clear import list prevents surprises after signup
- A named migration contact gives the champion someone to point to internally
Cons
- Free migration work costs your team real hours per account
- Promised timelines become support tickets when data is messy
- Overselling the ease of switching damages trust right after the sale
For example, suppose a project tool targets users of a larger rival
For example, suppose a project management tool builds a switching page for teams leaving a bigger competitor. The hero reads: "Leaving [tool]? Bring every project, task and comment with you." The next section lists four steps: export from the old tool, import with our importer, review the mapping with a migration specialist, invite the team.
Below that, a two-column list states what comes across (projects, tasks, assignees, comments, attachments) and what doesn't (custom automations, which you rebuild with help). A quote from a customer who made the same move follows, then the FAQ. The page never says the competitor is bad. It says the move is safe and shows how.
What proof works best for competitor customers?
The strongest proof for competitor customers is evidence from people who made the exact same switch. A short quote from a team lead who left the same tool is worth more than a famous logo. If you don't have those stories yet, ask recent switchers for one line about the move, and use that.
- Switcher quotes: one or two sentences about how the move went, with name and role.
- Before-and-after workflow: a factual description of what's faster or simpler now.
- Count of switchers, only if true: a real number of teams who moved from that tool.
- Review site excerpts: short, attributed quotes you're permitted to use.
Placement matters too. Put the first piece of switcher proof right after the migration plan, where doubt peaks. Check scroll depth data to make sure visitors actually reach it.
How should you talk about the competitor?
Talk about the competitor factually, briefly and with dates. Name the specific differences that matter to switchers, and avoid claims you can't support. The FTC's long-standing statement on comparative advertising treats truthful, non-deceptive comparisons as fair, which is the standard to hold yourself to.
Date your comparison ("as of October 2026") and review it every quarter, since competitors change. Avoid mocking language, which makes the champion feel foolish for choosing the old tool. The tone that converts is respectful: they made a reasonable choice then, and your product fits better now. Our collection of comparison page examples shows how strong SaaS brands handle this.
How do you measure a switch landing page?
Measure a switch landing page by migration calls booked and switchers who go live, not just by page conversion rate. A switching page sends fewer, more qualified visitors, so its numbers won't match a general landing page. Set up events for the primary CTA and for clicks on the migration plan and FAQ.
For context, Unbounce's conversion benchmark report gives a 6.6% median across industries and about 3.8% for SaaS, but those figures blend every page type. Compare your switching page to itself over time instead. Our guides to landing page conversion tracking and what counts as a good conversion rate explain how to set that up. If you test, start with the hero: our notes on testing headlines cover what to try first.
