Request a migration plan for your app subscriptions
Moving subscriptions away from native store infrastructure or another subscription platform involves more than changing an SDK.
You need to know where subscribers currently buy, how products are organized, and what customer and revenue data must remain visible after the move. This page explains the information to prepare, the platforms to declare, and the four steps that follow a request.
What to prepare before you request a plan
A migration plan is most useful when it is tailored to the app's current setup and timeline. The request form is designed for teams moving from native subscription infrastructure or another subscription platform. Before submitting, gather your company website, the public App Store URL, and a short description of your current subscription setup. In the free-text area, explain anything that could affect the move, such as additional stores, web billing, or a preferred timeline.
Form fields and what each one is for
First name: the requester's given name. Last name: the requester's family name. Email: the address for follow-up about the request. Company website: the public website for the business behind the app. App Store URL: the public listing for the app being migrated. Current subscription platforms: every platform where subscriptions are currently available, selected from the options below. Tell us more: additional context about the app, current setup, needs, or timeline.
Current platforms to declare
iOS App Store Google Play Store Web (Stripe) Web (Other) Alternative app stores
Select every option that applies. A team selling on both iOS and Android, for example, should select both store options rather than choosing only the larger one. Teams using web billing should distinguish Stripe from another web payment setup, and teams present in alternative stores should declare that separately so the plan accounts for each purchase channel.
What happens after you submit
Confirm your request: the team verifies the submitted details, asks a few questions, and schedules an introductory call. If the request cannot be accommodated, follow-up is sent by email with helpful resources.
Introductory call: the conversation covers follow-up questions based on the app and the team's current understanding of the needs.
Prepare your migration plan: the team prepares a plan tailored to the specific needs and timeline, drawing on experience from previous migrations.
Walk through your plan: both teams review the plan together, discuss questions or concerns, and agree on potential next steps.
Capabilities to consider in your plan
Manage Products: organize active products so releases do not depend on long cycles. Deploy Faster: in-app purchase deployment is presented as moving from months to hours. Cross-Platform View: one view of the business across all app stores. Analyze Business Metrics: user metrics in a dashboard with subscription-specific charts. Manage Customers: purchase histories and promotional subscriptions with customer-level controls. Segment Your Data: MRR, revenue, and active subscribers can be analyzed to see what is working.
Submission checklist
Before submitting, check that the email address is correct, the App Store URL opens the right listing, and every current subscription platform is selected. Add context in the free-text field if your timeline is fixed, if subscriptions are sold on the web as well as in stores, or if customer purchase history must be preserved. That detail helps the introductory call focus on your app rather than on basic setup questions.
Frequently asked questions
Why use this migration approach?
It is presented as a suite of tools built specifically for app businesses, with product, customer, analytics, and cross-platform subscription management in one place.