How to Migrate Subscriptions from Recharge to SaltAI

Switching subscription platforms feels risky. You've spent months — maybe years — building up a base of loyal subscribers who pay automatically every week or month, and the idea of disrupting that revenue stream is enough to make most merchants put the migration in the "too hard" drawer indefinitely. But staying on a platform that no longer serves your business is just as dangerous, and Recharge's 2023 pricing overhaul left thousands of Shopify merchants paying significantly more for features they rarely use.

The good news is that migrating subscriptions doesn't have to mean lost revenue, confused customers, or a weekend of frantic support tickets. With the right preparation, a structured migration window, and a platform built natively for Shopify, you can move your entire subscriber base with minimal disruption. Merchants supplying high-volume clients — from retail giants to corporate accounts — have completed this process without a single missed billing cycle.

In this guide, you'll learn exactly how to export your subscriber data from Recharge, prepare your Shopify store for the switch, communicate proactively with customers, and go live on SaltAI Subscriptions with confidence. Whether you run a coffee subscription, a beauty box, or a wholesale replenishment service, the steps are the same. Let's get into it.

Understanding What You're Actually Moving

Before you touch a single export file, you need a clear picture of your current subscription data. Active subscriber count, billing intervals, product variants tied to plans, and next billing dates are the four data points that matter most during any migration. Log into your Recharge dashboard and navigate to Analytics > Subscribers to pull a live snapshot of all of these figures at once.

Pay particular attention to subscribers on legacy pricing or grandfathered discount codes. These are the accounts most likely to experience friction during migration if you don't map them manually in advance. Recharge stores discount information at the subscription level, not the order level, which means a standard export won't always surface these automatically — you'll need to cross-reference with your Shopify order history.

Also audit your subscription product catalogue. If you've ever renamed a product, changed a variant SKU, or archived and recreated a product in Shopify, there may be mismatches between what Recharge thinks the product is called and what actually exists in your store today. Catching these discrepancies before migration saves hours of post-launch debugging and prevents subscribers from being billed for a product that no longer exists in your catalogue.

Exporting Your Data from Recharge

Recharge provides a built-in data export tool under Merchants > Data Export, and you'll want to run three separate exports: Subscriptions, Customers, and Addresses. Download all three as CSV files and store them in a clearly labelled folder with the export date in the filename — this timestamp matters if you need to reconcile any billing discrepancies later. Don't rely on a single combined export; keeping the files separate makes the import process significantly cleaner.

Open the Subscriptions CSV and add a new column labelled "migration_status" with a default value of "pending" for every row. As you work through the migration, you'll update this to "mapped," "imported," or "flagged" depending on each subscriber's situation. This simple tracking method has saved merchants from double-importing subscribers or missing edge cases like paused subscriptions, which Recharge exports with a status of "PAUSED" rather than "ACTIVE."

Give special attention to payment method data. Recharge tokenises payment details through Stripe or Braintree, and those tokens cannot be transferred directly to another platform. This is the single most misunderstood aspect of subscription migration. SaltAI Subscriptions uses Shopify Payments tokenisation natively, which means customers with cards already saved in their Shopify accounts won't need to re-enter payment details — but subscribers whose cards live only in Recharge will need to update their billing information before their next charge date.

Preparing Your SaltAI Store Before Import

Install SaltAI Subscriptions from the Shopify App Store and complete the initial configuration before importing a single subscriber. This means setting up your selling plans, replicating your existing billing frequencies, and confirming that every product you plan to migrate is already assigned to the correct selling plan group. Trying to import subscribers to products that don't yet have active selling plans is the number-one cause of failed migrations.

In the SaltAI dashboard, navigate to Selling Plans and recreate each subscription interval you currently offer in Recharge. If you offer weekly, bi-weekly, and monthly options for a supplement range, create all three plans before the import. Take this opportunity to consolidate plans you've accumulated over time — many merchants discover they have eight or nine plans in Recharge when four or five would cover every active subscriber. Fewer plans mean a cleaner catalogue and a simpler customer portal experience.

Also configure your customer portal settings now, before any subscribers are live. Set your cancellation flow, pause options, and swap policies. Customers who log in after migration will see the SaltAI portal immediately, and a half-finished portal with placeholder text destroys the professional impression you've worked hard to build. Test the portal yourself using a test subscriber account so you see exactly what your customers will see on day one.

Running a Test Migration First

Never migrate your entire subscriber base in a single batch without running a controlled test first. Select a group of 10 to 20 active subscribers — ideally colleagues, friends, or highly engaged customers who have agreed to be part of a beta — and import their subscriptions manually using SaltAI's import template. Verify that billing dates are correct, that product variants resolve properly, and that each test subscriber can log into the customer portal and see their subscription details.

Run the test at least five business days before your planned full migration date. This buffer gives you time to identify mapping errors, fix selling plan assignments, and — if necessary — contact SaltAI support for guidance on edge cases. Rushing this stage is where migrations go wrong. A coffee brand with 4,000 subscribers that skips test migration risks discovering a billing date offset error only after thousands of customers have been charged on the wrong day.

Document every issue you encounter during the test and how you resolved it. This becomes your migration runbook — a live reference document that you or a team member can follow step by step during the full import. If you're migrating a large subscriber base, consider running the full import in batches of 500 to 1,000 subscribers rather than all at once, which allows you to catch and fix any issues before they affect your entire base.

Communicating the Migration to Your Customers

Proactive communication is what separates a smooth migration from a wave of support emails. Send your first notification email 14 days before the migration date, explaining that you're upgrading your subscription system to improve the customer experience. Keep the tone positive and focus on what's getting better — faster portal loading, easier swap options, better delivery date control — rather than dwelling on technical platform details that most subscribers won't care about.

Send a second email 3 days before that includes direct instructions for any subscribers who need to update their payment method. Be specific: include a screenshot of exactly where the payment update button lives in the new portal, and provide a direct link to their account login page. Customers who receive vague "please update your details" emails without clear instructions are far more likely to cancel than customers who receive step-by-step guidance with visual support.

Finally, send a same-day notification on migration day confirming that everything has moved successfully. Keep this email short — three sentences maximum — and include your customer support contact details prominently. Expect a small spike in support volume for 48 to 72 hours regardless of how well you've communicated. Having a prepared FAQ document that your support team can copy-paste from will dramatically reduce response time and keep subscribers feeling looked after during the transition period.

Going Live and What to Monitor in Week One

Your first week post-migration is a monitoring exercise more than anything else. Set up a simple daily check routine: log into SaltAI, review the Upcoming Charges report for the next seven days, and confirm that subscriber counts, billing amounts, and product assignments all look correct. Any anomaly spotted now — a subscriber billed twice, a product that failed to resolve, a discount code that didn't carry over — can be corrected before it compounds into a larger problem.

Monitor your failed payment rate closely. A healthy subscription operation typically sees a failed payment rate of 3 to 6 percent. If you see a spike above 10 percent in week one, it's almost always caused by payment token migration issues rather than underlying card problems. SaltAI's dunning management tools will automatically retry failed payments, but for high-value subscribers you may want to reach out personally rather than relying solely on automated retries.

Track customer portal login rates as a proxy for subscriber confidence. If a significant portion of your migrated subscribers log in during week one to check their account, that's a positive signal — it means they received your communications and feel engaged. Low login rates may indicate your migration emails landed in spam folders or weren't opened, which is worth investigating before your next billing cycle kicks in across the full subscriber base.

Conclusion

Migrating from Recharge to SaltAI is a structured process, not a gamble. Export carefully, map your data thoroughly, test before you commit, and communicate early and often with your subscribers. The merchants who experience difficult migrations are almost always the ones who skipped preparation steps in the interest of speed.

The key takeaways are simple: audit your data before you export, recreate your selling plans before you import, and run a test migration with a small group before touching your full subscriber base. With those three principles in place, the technical process is entirely manageable.

Done right, migration leaves you with a leaner subscription stack, lower monthly platform costs, and a customer portal that's deeply integrated with the Shopify experience your subscribers already know.

Try SaltAI Subscriptions free at saltai.app — no credit card required.