Guide for migrating from Adapty, Qonversion, Glassfy, or other subscription SDKs to Superwall

How do I migrate to Superwall from another subscription provider?

If you're currently using a subscription management provider like Adapty, Qonversion, Glassfy, or another SDK and want to migrate to Superwall, here's what you need to know.

Will My Existing Subscribers Keep Their Access?

Yes. Superwall reads subscription status directly from the device's App Store (iOS) or Google Play (Android) records. This means:

Existing subscribers are automatically recognized when you switch SDKs
No manual migration of subscription data is required
Users won't experience any interruption to their access

When a user opens your app with the new Superwall SDK, their active subscriptions are detected automatically, regardless of which SDK was used to originally make the purchase.

What Gets Migrated Automatically

Data	Migrated?
Active subscription status	✅ Yes - read directly from the device
Entitlement access	✅ Yes - based on active subscriptions
Cross-device sync (same Apple ID/Google account)	✅ Yes

What Does NOT Migrate

Data	Migrated?
Historical analytics and metrics	❌ No
Paywall designs and configurations	❌ No - must be recreated in Superwall
A/B test history and experiment data	❌ No
Custom user attributes from previous SDK	❌ No - must be re-set via Superwall SDK

Re-setting Custom User Attributes

Superwall reads subscription state directly from Apple and Google, so transaction history does not need to be migrated. Your own user metadata can be added as user attributes. The original transaction ID is a stable key that bridges a returning subscriber back to their record in your backend.

The flow:

Read the original transaction ID on device

On iOS, use StoreKit 2's Transaction.currentEntitlements and read transaction.originalID. On Android, use the Play Billing purchaseToken.

import StoreKit

func fetchOriginalTransactionID() async -> String? {
  for await result in Transaction.currentEntitlements {
    guard case .verified(let transaction) = result else { continue }
    return String(transaction.originalID)
  }
  return nil
}

Look up the user in your backend

Send the original transaction ID to your backend, which returns a stable userId and any metadata you want exposed to Superwall (plan tier, signup date, referrer, etc.).

Identify, then set attributes

Call identify first so the attributes attach to the right user.

Superwall.shared.identify(userId: userId)
Superwall.shared.setUserAttributes([
  "plan_tier": "pro",
  "signup_date": "2024-01-15",
  "referrer": "appstore_search"
])

setUserAttributes merges with existing attributes rather than replacing them. Pass nil for a key to remove it.

A few things to watch for:

Always call identify before setUserAttributes, otherwise attributes attach to the anonymous user.
On a fresh install before a restore, currentEntitlements may be empty.
Sandbox and production original transaction IDs differ.
With Family Sharing, the original transaction ID belongs to the original purchaser, not the family member.

Run this on app launch (after StoreKit hydrates), after a successful purchase, and after a restore. It is safe to call every launch since identify is idempotent.

Migration Steps

Remove your current subscription SDK from your project
Follow the Superwall installation guide for your platform

Troubleshooting

Subscription status not detected

If an existing subscriber isn't being recognized:

Have them tap "Restore Purchases" on any paywall
Ensure they're signed into the same App Store/Google Play account used for the original purchase
Check that the subscription hasn't expired

How do I migrate to Superwall from another provider?