Migration — Sublyra Help Center

1. Why migration uses re-activation links

Shopify cannot rebuild a subscription contract without the customer's payment method — and no app may move stored card details between systems. So instead of pretending a silent switch is possible, Sublyra generates a one-click re-activation link per subscriber: they confirm payment once, and the subscription is recreated in Sublyra.

The importer supports Subi, Appstle, ReCharge and a generic CSV from any other app. Each supported source maps its own export's column names automatically — picking the right source is what makes the paste parse.

Where to find it: Sublyra admin → Settings → Migration importer.

Rather have it done with you? The White-glove migration add-on ($149 one-time) is a guided import with our team, and the Plus plan includes migration help. See Plans & billing.

2. Import step by step

1 Export your subscribers from the old app. Every subscription app has a CSV export of active subscriptions — grab it before you cancel anything there.

2 In Sublyra, open Settings → Migration importer and pick the source app. Give the batch a label if you like (e.g. "Subi export — August").

3 Upload the CSV file or paste its contents into the box. The first line must be the header row.

4 Click Preview import. Valid rows are tabled; rows with errors are listed with the reason and will be skipped. If the counts look wrong, fix the CSV and preview again — nothing is imported at this stage.

5 Click Import N subscribers. Rows are matched against your existing customers (by email, case-insensitively), each row's interval is matched to one of your selling plans where possible, and every valid row gets a re-activation link.

6 Download the links CSV and email it out — your email platform's mail-merge handles the per-subscriber link column. Each subscriber clicks their link, confirms payment once, and their subscription restarts.

Time the switch: send the re-activation emails, give subscribers a window to confirm, and only then wind down the old app. Subscribers who don't click simply stay where they are until they do.

3. The CSV format

For the named sources (Subi, Appstle, ReCharge) just export and paste — the column mapping is built in. For a generic CSV, the importer looks for these columns:

Column	Required?	Notes
`email`	Required	Matched against your existing customers, case-insensitively
`variant id`	Required	The Shopify variant the subscriber receives
`interval`	Optional	Used to match a local selling plan, so the link recreates a subscription rather than a one-time purchase
`quantity`	Optional	Units per delivery
`price`	Optional	Reference only — the price charged comes from your store's current pricing
`next billing date`	Optional	Reference for your outreach timing

A minimal generic CSV looks like:

email,variant id,interval,quantity,next billing date
jane@example.com,44839201792273,1 month,1,2026-09-01
mark@example.com,44839201825041,3 months,2,2026-09-15

Variant IDs are store-specific. If the export references variants from a different store, the rows will import but the links can't recreate the right product. Export from the same store you're migrating on, or map the IDs first.

4. After the import

Download links CSV — one row per valid subscriber: email, variant_id, interval, quantity, next_billing_date, reactivation_link.
Email the links out with your usual platform. The link is per-subscriber and one-click — they confirm payment once and the subscription is recreated.
Matched counts on each batch tell you how many rows corresponded to customers Shopify already knows — useful for gauging how much fresh checkout friction to expect.

5. Import history & deleting batches

Every import stays in the Import history card with its valid/skipped/matched counts — the audit trail of who was invited and when.

Deleting a batch voids its links. Delete removes the import record and its re-activation links should be considered dead. Only delete once the emails are out and you're confident nobody still needs their link.

6. FAQ

Can you migrate subscribers without emailing them?

No — and be suspicious of any app that claims otherwise. Shopify requires the customer's payment method to create a contract, and stored cards can't move between apps. The one-click re-activation link is the lightest legitimate version of that step.

My source app isn't listed. Can I still migrate?

Yes — pick Generic CSV and make sure the export has at least an email and a variant id column (rename the headers to match section 3 if needed).

Preview says "No data rows found". Why?

The first line must be the header row, and at minimum an email and a variant id column must be present. Check you pasted the whole file, headers included, and picked the right source app.

Do imported subscribers get charged twice — once by each app?

Only if both apps are live with overlapping subscriptions. Migrate, send the links, let subscribers re-activate, then retire the old app. The window where both run is under your control.

Related guides

Plans & billing — white-glove migration and the Plus plan
Troubleshooting — CSV parse errors and link issues
Analytics — watch re-activations land as new subscribers