Transferring an app to a new developer account or owner can preserve ratings and reviews when done through the platform's official transfer process, but it requires careful preparation of agreements, subscriptions, certificates, and listing details. Plan the timing, benchmark metrics, and verify everything after the move.
Use the official process
Both Apple and Google provide app transfer mechanisms with requirements and limitations, such as for apps with certain capabilities or subscriptions. Check current documentation and eligibility before planning.
Do not republish as a new app, which would lose ratings and rankings.
Prepare the checklist
Gather agreements, tax and banking details, certificates and keys, push notification setup, subscription and in-app purchase configuration, and third-party service links. Confirm both accounts are in good standing.
Coordinate timing with release schedules.
Benchmark before and after
Record rankings, ratings, conversion, and revenue before the transfer, then monitor closely afterward for changes. Verify the listing, metadata, localizations, and analytics integrations.
Prepare support for users who may notice changes.
Communicate and verify
Inform stakeholders and, if relevant, users about developer name changes. Test purchases, sign-in, and notifications after the transfer.
Update links, support emails, and policy pages.
Common mistakes with app transfer ASO
Publishing a copy as a new app is the worst mistake, since ratings and rankings do not move. Another is forgetting subscriptions, push certificates, or third-party keys until the transfer fails. Not benchmarking before the move makes problems hard to spot.
Skipping post-transfer testing of purchases and sign-in leaves defects live.
App transfer ASO: a worked example
Two companies agree an app acquisition. They check eligibility, gather agreements and keys, schedule the transfer outside a release window, record ratings and rankings, and test purchases and notifications immediately afterward.
They update support emails and policy links the same day.
How to do it, step by step
- Check eligibilityReview the platform's requirements.
- Gather configurationList agreements, certificates, keys, and services.
- BenchmarkRecord ratings, rankings, and revenue.
- Transfer officiallyUse the platform's transfer process.
- TestVerify purchases, sign-in, and notifications.
Before and after examples
Illustrative examples written for a generic app in this category, not client results. Swap in your own product, audience, and data.
Publish a new copy
Use the official transfer
Why it works: Copies lose ratings.
Start the transfer, then discover missing keys
A list of keys and services prepared first
Why it works: Prevents delays.
Assume it works
Test a purchase and a sign-in
Why it works: Catch problems early.
Action plan
- Confirm eligibility and requirements
- Do not republish as a new app
- Gather all configuration details
- Benchmark key metrics
- Test purchases and sign-in after transfer
- Update links and contacts
Metrics to monitor
- Ratings and rankings before and after
- Revenue continuity
- Post-transfer defects found
- Time to full verification
Record the baseline, release date, audience, markets, and external changes before interpreting movement. Rankings and conversion are useful signals, but a decision is stronger when activation, retention, and business value confirm that the page attracted the right users.
Frequently asked questions
Do ratings carry over in a transfer?
Official transfers generally preserve them, but verify current rules.
Can subscriptions transfer?
Policies exist; check current platform rules.
How long does it take?
It varies; allow buffer and plan carefully.
Keep reading
More in Strategy and Operations
Browse all 6 Strategy and Operations guides
