Migrating from ReCharge to Another Shopify Subscription App

ReCharge is one of the oldest subscription platforms on Shopify, which is both why many stores are on it and why migrating off it needs care: it predates Shopify’s native subscription APIs, and older installations can be configured in ways newer apps are not.

This is a general guide to the shape of that migration. Specifics depend on your configuration and on what both vendors will support, so treat vendor confirmation as a required step rather than an optional one.

Establish your configuration first

The decisive question: are your subscriptions native Shopify subscription contracts, or held in ReCharge’s own system?

Newer installations generally use Shopify’s native contracts. Older ones may not. You can get a strong signal by checking whether subscription contracts appear in your Shopify admin against the customer record — if they do, they are Shopify objects.

Ask ReCharge support directly to confirm, in writing, and ask the same of the app you are moving to. The answer determines whether this is a configuration migration or a re-authorisation event.

If contracts are native

The good case. The contracts, payment methods and schedules live in Shopify. Migration means:

• Recreating plans and pricing in the new app
• Pointing the new app at existing contracts
• Rebuilding anything that depended on ReCharge-specific data

Subscribers are generally unaffected.

If they are not

You are asking customers to re-subscribe. Plan it as a campaign, not an operation:

• Give plenty of notice and a clear reason
• Make re-subscribing one click, with their configuration pre-filled
• Consider an incentive for re-authorising promptly
• Expect and budget for churn

The dependencies that break

Checkout customisations. Older ReCharge setups sometimes route through their own checkout. Moving to an app that uses Shopify checkout changes the customer’s path, your analytics, and any scripts attached to the old one.

Metafields. ReCharge writes metafields that your fulfilment rules, shipping logic or reporting may consume. Inventory those before migrating — grep your Flow automations, shipping rules and any custom theme code for references.

Portal links. Old emails contain links to the ReCharge portal. Those will break. Decide whether to redirect them.

Webhooks and integrations. Anything subscribed to ReCharge webhooks — a 3PL, an ERP, an email platform — needs repointing.

Order tags. Downstream automations keyed on ReCharge’s tags need updating before the first renewal on the new app, not after.

The sequence

1. Export everything: active subscriptions, next charge dates, plans, discounts, addresses
2. Confirm the contract model with both vendors in writing
3. Inventory metafield and webhook dependencies
4. Pause new signups on ReCharge
5. Migrate a test batch and let one renew
6. Reconcile counts and next-charge dates
7. Migrate the rest, keep ReCharge installed for one cycle
8. Watch renewals for two weeks

The number to verify above all others

Next charge date, per contract. Not a sample — all of them.

Dates moving is the failure that customers notice immediately and that turns a technical migration into a support event.

The general migration guide · Checklist