円滑な引き継ぎとナレッジトランスファーの計画

Whether you sell, hand off, or step back from an indie app, a clean handover protects the deal and your reputation.

• Buyers pay more for documented, low-risk assets
• New maintainers ship faster with clear context
• You avoid endless post-sale support calls

Start with a complete inventory of every asset tied to the app.

• Source code repositories
• App Store & Play Console accounts
• Backend services, domains, certificates
• Third-party API keys and subscriptions

A one-page architecture overview answers: what runs where, and how data flows.

Keep it plain so a non-author can follow it.

Never paste live secrets into plain docs. Use a secrets manager or a shared vault and transfer access at closing.

List which secrets exist and where they live, not the values.

Write a runbook so anyone can build and ship a release without you.

Include exact commands, signing steps, and store submission notes.

App Store and Play handle transfers differently.

• App Store: use App Transfer (no in-app purchase blockers, no pending agreements)
• Play: open a transfer request with both Console account emails

Transfer infrastructure ownership cleanly.

• Move domains via registrar transfer codes
• Reassign cloud project billing
• Hand over DNS and email forwarding

Users must not notice the change. Plan for:

• Support inbox migration
• Privacy policy / data controller update
• Push notification credentials transfer

Track progress with a simple checklist you can run through with the buyer.

Offer a bounded transition window (for example 30 days) of email support. Put it in writing so expectations are clear and your time is protected.

After transfer, revoke your own access to repos, accounts, and secrets. This protects both parties and finalizes the separation.

A clean handover de-risks any exit. You learned to build an inventory, document architecture, write a release runbook, transfer store/domain/backend ownership, protect secrets, offer a bounded support window, and finally revoke your own access.