Storefront transfer diligence for Steam, Apple and Google Play

Storefront transfer tools preserve some valuable continuity, but each platform excludes or changes important operational data. Steam preserves wishlists and followers but excludes historic financial access by default and requires new publisher API keys. Apple preserves the Bundle ID, ratings and updates while imposing dependency-specific work. Google transfers users and ratings but not every report, test group or linked service.

Before the transfer, download non-transferred reports, reconcile revenue, document refunds and liabilities, inventory keys and integrations, prepare the receiving account, and resolve policy or verification problems. Create a dependency owner for subscriptions, payments, cloud projects, analytics, multiplayer, achievements and signing credentials.

Run a post-transfer release drill. Confirm that the buyer can publish a build, receive payments, validate purchases, operate multiplayer and support users. The platform's Transfer complete message is a milestone—not proof that the acquired business is fully operational.