Migrating from Appstle Subscriptions: What to Check

Appstle builds on Shopify’s native subscription APIs, which makes migrating away from it substantially easier than migrating off an app with its own payment vault: the contracts are Shopify objects and they stay where they are.

That removes the hardest problem. It does not remove all of them.

Confirm the specifics of your own installation with both vendors — configurations vary, and this is a guide to the shape of the work rather than a substitute for that confirmation.

What stays

• Subscription contracts — Shopify objects, unaffected
• Vaulted payment methods — held by Shopify
• Order history — ordinary Shopify orders
• Customer records

Because of this, subscribers generally do not need to re-authorise, and most will not notice.

What you rebuild

Plans and selling plan groups. Recreate frequencies, discounts and billing policies in the new app. Check carefully that discount types match — a “10% off” and a “fixed price ₹1,349” can produce the same number today and diverge the moment you change the base price.

Tiered and tenure-based discounts. If you use discounts that escalate with cycle count, verify the new app calculates tenure the same way, and that existing subscribers land on the right tier rather than resetting to cycle one.

Build-a-box configuration. Item counts, eligible products, price banding and the choice deadline all need recreating, and the deadline behaviour is worth testing explicitly.

Portal customisations. Branding, available actions, and which actions subscribers may take.

Email templates and triggers. Including the renewal reminder, which in India is a compliance requirement rather than a nicety. Pre-debit notifications.

Order tags. Downstream automations key off these. Map old tags to new before the first renewal.

Metafields. Inventory anything reading Appstle metafields — fulfilment rules, shipping logic, reporting, custom theme code.

The things that catch people

Bundle and box configurations rarely map one-to-one between apps. Budget time to rebuild rather than expecting an import.

Loyalty or reward rules tied to subscription tenure need their state migrated, not just their configuration. A subscriber on cycle nine should not restart at cycle one and lose their tier.

Minimum-term commitments. If subscribers agreed to a minimum number of cycles, that obligation has to carry over or you have quietly changed the terms of an existing agreement.

Sequence

1. Export active subscriptions with plan, frequency, next charge date, discount, cycle count
2. Rebuild plans in the new app and compare prices line by line
3. Inventory metafield, tag and webhook dependencies
4. Pause new signups on Appstle
5. Migrate a test batch including your own subscription; let one renew
6. Reconcile — counts, next charge dates, discount amounts, cycle counts
7. Migrate the rest; keep Appstle installed for one billing cycle
8. Monitor renewals for two weeks

Verify after

• Every contract’s next charge date is unchanged
• Discount amounts on the next renewal match the previous one
• Cycle counts carried over, so tenure-based benefits are intact
• The portal works, on a phone
• Renewal emails fire

General migration guide