Migrate from Churnkey in 15 minutes.
Most of the work is already done — you're already on Stripe Connect, your customers don't need to do anything. The migration is recreating your settings, swapping the cancel-flow install, and pointing your manage button at Backstop's portal. We've kept the order in this guide so you can run both tools in parallel for two weeks before fully cutting over.
~15 min total · 8 steps · works with your existing Stripe Connect
Step 1 · 1 min
Sign up for Backstop free
In Churnkey
Don't cancel yet — keep Churnkey running while you set up. We want to compare apples to apples.
In Backstop
Sign in with email or Google. New workspaces start on a 14-day Pro trial (then free up to 10 campaigns/month), no credit card. You'll create a workspace next.
Sign up freeStep 2 · 2 min
Connect your Stripe account
In Churnkey
You already did this in Churnkey — connecting Backstop won't disconnect Churnkey, Stripe can authorize both at once. We never see your secret key.
In Backstop
From the workspace home, click Connect Stripe. OAuth takes ~30 seconds. The grant is read_write — recovery has to retry invoices, apply coupons, and pause/cancel/switch plans on your behalf — scoped to your account, encrypted at rest, and revocable from Stripe any time. Once connected, Backstop starts mirroring your customers and subscriptions in the background; no action required from your customers.
Step 3 · 5 min
Recreate your cancel flow
In Churnkey
Open Churnkey's flow editor and screenshot the survey questions, offer terms, and confirm copy. You'll paste these into Backstop.
In Backstop
Cancel flows → New flow → pick the 'SaaS Standard' or 'Annual Upsell' template. Edit the offer percent + duration to match Churnkey's. Adjust the survey copy. Publish — that gives you a live v1 in two clicks.
Open the builderStep 4 · 2 min
Set up email branding
In Churnkey
Copy your From name, accent color hex, and logo URL from Churnkey's email branding settings.
In Backstop
Settings → Email branding. Paste the same values. Live preview as you type. Custom send domain (Pro) takes another 5 min if you want it — DNS records guided.
Step 5 · 1 min
Wire up Slack/Discord notifications
In Churnkey
Copy your Slack incoming webhook URL from Churnkey's notifications page.
In Backstop
Settings → Notifications. Paste the URL, hit 'Send test'. Per-event opt-in (recovered, lost, cancel saved, cancel lost) so you control the noise.
Step 6 · 2 min
Install the cancel flow + point your manage button at the portal
In Churnkey
Find the Churnkey embed in your app code — usually a script tag + a data attribute on your cancel button — plus wherever you send customers to manage billing.
In Backstop
Pick one of three installs (Workspace → Cancel flows → Embed): (a) our one-line embed.js for an on-your-domain modal, (b) a no-SDK hosted redirect link, or (c) a paste-into-Cursor/Claude prompt that wires it for you. Then point your "Manage subscription" button at the Backstop portal — it replaces Stripe's billing portal (pause, cancel-into-save-flow, update card, switch plan). Customer experience stays familiar; you keep the save rate.
Step 7 · 2 min
Run side-by-side for 2 weeks
In Churnkey
Keep Churnkey live for two more weeks. Both tools mirror the same Stripe events without conflict. To avoid double retries or duplicate dunning emails on the same invoice, run recovery in only one tool at a time — keep recovery in Churnkey and test just the cancel flow in Backstop, or flip it the other way.
In Backstop
Watch the Recovery dashboard daily. Compare your save rate + recovery rate against Churnkey. Decide.
Open dashboardStep 8 · 0 min
Cancel Churnkey
In Churnkey
When you're convinced, cancel your Churnkey subscription via their billing page. They'll keep your data accessible for export per their TOS.
In Backstop
You're done — same loop, smaller bill. Hit reply on any Backstop email if anything looks off; we read every reply.
What doesn't transfer cleanly
Honest list — nothing here is a deal-breaker, but you should know:
- •Past campaign data stays in Churnkey — we don't pull historical recovery numbers from their API. Day-one stats start from the moment you connect Stripe to us.
- •Our smart retries are decline-code-aware rules, not ML. If you tuned custom retry policies in Churnkey, you can match them under Settings → Retry policy — soft and hard cadence, max attempts, and the cap window are all configurable per workspace.
- •Churnkey leans on AI/ML retry-timing models with more historical training data; our rules-based approach is simpler and more predictable. Run both in parallel during the trial and compare recovery rate on your own traffic before you decide.
Ready when you are.
Your 14-day Pro trial covers the full feature set — run side-by-side with Churnkey for two weeks before you switch. No credit card, no lock-in.