You signed up with Recharge when subscriptions were new. Three years later your subscriber base is 20,000+, your team likes the AI-driven retention features in Stay AI better, and you want to migrate. The problem: this is a customer-facing data migration with payment tokens, recurring charges, customer expectations, and zero tolerance for a botched cutover.
This is the playbook. It assumes you have a Shopify store with 5,000+ active subscribers on Recharge and you're moving to Stay AI. The same outline works for migrations between any two major subscription platforms (Skio, Smartrr, Bold, custom on Stripe), but the specifics differ per platform.
Why brands switch (and when they shouldn't)
The legitimate reasons to migrate off Recharge:
- Stay AI's AI-driven retention (intelligent dunning, churn prediction, automated upsell) materially outperforms Recharge's at your scale
- Recharge's pricing has crept up faster than your subscriber growth + Stay AI's pricing is meaningfully better at your tier
- Recharge's checkout integration is causing conversion drop you've isolated to checkout friction
- Stay AI's customer portal UX matches your brand voice better
- Your team is hitting platform-feature ceilings (specific workflows Recharge doesn't support)
The reasons to NOT migrate:
- "Stay AI looks cooler". UX preferences alone don't justify a customer-facing migration
- "Their salesperson promised lower churn". migration costs operationally; the actual lift needs to be real + measured, not promised
- "Our developer wants to try something new". developer preference is the worst reason to disrupt 20,000 customers
- You're below 1,000 active subscribers. the migration cost dominates the platform-difference value at this scale
Migrations are recoverable mistakes but expensive ones. Triple-check the business case before committing.
Pre-migration: what you need before week 1
A clean migration needs these in place BEFORE the official kickoff:
| Item | Why it matters | Who owns it |
|---|---|---|
| Signed contract with Stay AI + agreed migration support level | Without this Stay AI's engineering team can't allocate time | Founder + COO |
| Current Recharge data export + audit | You need to know what you're moving | Tech lead + Recharge support |
| Payment processor confirmation (Stripe / Razorpay / Shopify Payments) on token portability | Some processors don't allow token transfer between platforms; you must know upfront | Tech lead + payment processor support |
| Customer communication plan + draft messaging | You'll send 3-5 customer-facing emails during migration; they need to be ready before cutover | Brand lead + customer service lead |
| Roll-back plan | If cutover fails, what's the recovery path? Recharge is the fallback for 30 days | Tech lead + COO |
| 30-day "stay hot" agreement with Recharge | Recharge stays operational during the grace period | Account manager + COO |
The payment-token portability check is the gate. If your payment processor + your contract with Recharge doesn't allow token transfer, customers will need to re-enter their card on Stay AI. That collapses migration completion from 95+ percent to 40-60 percent. Confirm portability before signing the Stay AI contract.
Week 1: discovery + scope lock
Audit your Recharge setup
Export to a spreadsheet:
- Active subscribers (with their cadence, product, last charge date, next charge date)
- Paused subscribers (with pause reason if available)
- Cancelled subscribers from the last 90 days (for win-back targeting later)
- Active workflows (welcome flow, post-purchase flow, dunning flow, cancellation save-flow, swap workflows)
- Active discount codes + their rules
- Klaviyo / Postscript integrations (the events flowing through them)
- Custom code in the customer portal (themes, custom CSS, JavaScript hacks)
- API integrations (3PL pulls, accounting system pulls, custom dashboards)
Decide what migrates and what gets rebuilt
Most things migrate. Some get rebuilt from scratch in Stay AI:
| Element | Migrate or rebuild | Why |
|---|---|---|
| Subscriber list | Migrate | Core data; do not lose this |
| Payment tokens | Migrate (if processor allows) | Customer experience disaster otherwise |
| Active workflows | Rebuild | Stay AI's flow definitions don't map 1:1 to Recharge's |
| Klaviyo integration | Reconnect | Stay AI sends slightly different events; flows need re-mapping |
| Customer portal customisation | Rebuild | Theme + JS hacks don't port; rebuild leaner in Stay AI |
| Discount codes | Migrate the active ones, retire expired | Spring cleaning opportunity |
| Cancellation save-flow | Rebuild | This is where Stay AI's AI-driven offers earn the migration |
Confirm the scope with all stakeholders
Marketing lead, customer service lead, tech lead, founder, accounting (for revenue continuity), Recharge account manager, Stay AI account manager. Everyone signs off on the scope before week 2.
Week 2-3: parallel setup
Stay AI gets configured in parallel with Recharge still running.
Set up the Stay AI account
- Connect Shopify
- Configure products + selling plans (cadence options)
- Configure payment processor
- Configure shipping zones + rates (matching Recharge's setup)
- Configure tax (GST for India, VAT for UK / GCC)
- Set up workflows (welcome, post-purchase, dunning, cancellation save-flow)
- Set up customer portal (use Stay AI's native portal; defer custom theme work to post-cutover)
- Test transactions full-scope with a real card on a real product (refund the test order)
Set up Klaviyo / Postscript integration
- Reconnect Klaviyo to the Stay AI account
- Re-create the lifecycle flows pointing at Stay AI events
- Test each flow with a test subscriber
- Schedule the flow cut-over (Recharge flows pause when Stay AI flows go live)
Set up monitoring + alerting
Subscriber-count, charge-success-rate, charge-failure-rate, customer-service ticket volume. all monitored daily during the migration window. Anomalies trigger same-day investigation.
Week 4: customer communication starts
The first email (T-14 days before cutover)
Subject: We're upgrading our subscription experience. Here's what's changing.
Body: explain the upgrade in plain language (no jargon, no "leveraging cutting-edge technology"). Tell customers:
- The change is happening on [specific date]
- Their subscription continues uninterrupted
- Their next charge will be on [their existing schedule]
- Their card on file stays the same
- Their portal URL is changing (or staying the same with a different look)
- What to do if something looks wrong
The second email (T-7 days)
Reminder. Same content, slightly shorter. Add: "We've prepared a help article on what's changing. [Link]"
The third email (T-1 day)
"Tomorrow we're switching. Your subscription is unaffected." Set expectations for any cosmetic differences they'll notice (portal looks different, email-from address changes, etc.)
The fourth email (T+1 day, post-cutover)
"The switch is done. Here's where to find your account." Include the new portal link, the customer service email + chat, FAQ link, contact form for issues.
The fifth email (T+14 days, post-cutover)
"Two weeks in. Tell us what you think." Survey link. This is your migration NPS signal.
Week 5: data migration + cutover
The technical sequence (cutover day, typically a Tuesday morning)
| Time | Action | Owner |
|---|---|---|
| T-24 hours | Recharge: stop new subscribers (storefront points new sign-ups to Stay AI starting now) | Tech lead |
| T-12 hours | Final subscriber data export from Recharge | Tech lead |
| T-6 hours | Stay AI imports subscriber data + payment tokens | Stay AI engineering + your tech lead |
| T-2 hours | Verification: subscriber count matches, charge schedules match, a sample of 50 subscribers checked manually | Tech lead + customer service lead |
| T-0 (cutover) | Recharge: charges paused (active subscribers do not get charged via Recharge anymore) | Tech lead |
| T-0 | Stay AI: charges activated (Stay AI takes over the charge schedule) | Stay AI engineering |
| T+2 hours | Storefront: subscription product pages point at Stay AI checkout (new + existing subscribers) | Tech lead |
| T+4 hours | Klaviyo: Stay AI events replace Recharge events; flows fire from new source | Marketing lead |
| T+6 hours | Customer service: monitor inbound queue; have 2x normal staffing | Customer service lead |
| T+24 hours | First-day metrics: subscriber count = pre-cutover count, charges processing as expected, ticket volume manageable | All hands |
The cutover happens during business hours so the team is available to handle issues, NOT overnight when problems compound silently.
Week 6: stabilisation + Recharge sunset
What to watch in week 6
- Charge success rate (target: matches pre-migration baseline within 2 percent)
- Customer service ticket volume (target: returns to baseline within 5 days)
- Active subscriber count (target: matches pre-migration count, drift below 2 percent)
- Failed charge recovery (Stay AI's dunning should be working; recovery rate matching or beating Recharge's prior performance)
- Klaviyo flow execution (every triggered flow firing as expected)
Issues you should expect
- 5-10 percent of customers will get confused by the new portal + email customer service. Have FAQ + chat ready.
- A small number of payment tokens won't transfer cleanly (typically 1-3 percent). These customers need to re-enter their card. Outbound email + phone outreach.
- Klaviyo flows may double-fire for a few hours during cutover. Pause the affected flows for 24 hours if needed.
- Reporting numbers will look strange for the first week (some metrics off by 5-15 percent vs Recharge equivalents). This is normal; the reports are now sourced from Stay AI and the calculation differs slightly.
Sunset Recharge (T+30 days)
After 30 days of stable Stay AI operation:
- Final reconciliation: confirm Recharge balances are zero, no orphaned subscribers, no pending charges
- Export final historical data from Recharge for your records
- Cancel the Recharge subscription
- Document the migration in your team's runbook (what worked, what hurt, what you'd do differently)
How long does the whole thing actually take?
For a brand with 5,000-15,000 active subscribers:
- Pre-work + signed contracts: 2-3 weeks
- Active migration weeks 1-5: 5 weeks
- Stabilisation weeks 6-8: 3 weeks
- Recharge sunset week 9: 1 week
Total: roughly 11 weeks from "decided to migrate" to "Recharge cancelled". Plan for 13-14 weeks to absorb the slippage that always happens.
Common failure modes
| Failure | Cause | Fix |
|---|---|---|
| Payment tokens don't transfer | Processor doesn't support cross-platform token portability | Confirm BEFORE signing Stay AI contract; force-prompt customers to re-enter card if necessary |
| Charge schedules drift after cutover | Time-zone or cutoff-time mismatch in the import | Verification step at T-2 hours catches this; reschedule failed charges in Stay AI's portal |
| Klaviyo flows double-fire | Old Recharge integration not fully disabled when new Stay AI integration activates | Pause Recharge flows for 24 hours before activating Stay AI flows |
| Customer service overwhelmed | Underestimated inbound ticket volume | Pre-staff 2x normal for cutover week; pre-write FAQ + email templates |
| Active subscriber count drops 10+ percent | Failed payment migrations + customer confusion | Outbound outreach to non-charging customers within 7 days; offer a small recovery discount |
| Storefront broken for new subscribers | Theme code still pointing at Recharge endpoints | Pre-stage the Shopify theme changes; flip at cutover; have rollback theme ready |
Production checklist
Migrating from Recharge to Stay AI (or any similar pair):
- Business case validated + signed off (not driven by vendor sales or developer preference)
- Payment-token portability confirmed with the payment processor in writing
- 30-day "stay hot" agreement with Recharge signed
- Audit + scope lock complete by end of week 1
- Stay AI account configured + tested full-scope by end of week 2
- Klaviyo / Postscript flows rebuilt + tested by end of week 3
- Customer communication sequence drafted + approved by end of week 3
- Cutover day plan documented hour-by-hour with named owners
- Customer service staffed 2x normal for cutover week
- Stabilisation metrics tracked daily for 14 days post-cutover
- Final reconciliation + Recharge sunset at T+30 days
- Internal post-mortem: what worked, what hurt, what would change next time
References + linked context
- Dcrayons commerce reference architectures: Enterprise D2C Subscription Architecture, Enterprise D2C on Shopify
- Lifecycle marketing reference: Enterprise Lifecycle Marketing
- Dcrayons glossary: oms, tacos
Subscription platform migrations are recoverable mistakes but expensive ones. If you're considering the switch and want a 30-minute sanity check on your specific situation, reach out via the contact form.
