Planning a Clean Handover & Knowledge Transfer
Learn how to document, package, and transfer everything a buyer or new maintainer needs so your indie mobile app can change hands smoothly.
Planning a Clean Handover & Knowledge Transfer is a free Indie Hacker Mobile Apps lesson on CoddyKit — lesson 4 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Indie Hacker Mobile Apps learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Why Handover Matters
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
The Handover Inventory
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
Documenting the Architecture
A one-page architecture overview answers: what runs where, and how data flows.
Keep it plain so a non-author can follow it.
# App Architecture
- Mobile: React Native (iOS + Android)
- Backend: Node API on Render
- DB: Postgres (Supabase)
- Auth: Firebase Auth
- Payments: RevenueCat -> App Store / PlayCredentials & Secrets
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.
# Secrets checklist (values in 1Password vault 'App Handover')
- APP_STORE_CONNECT_KEY
- PLAY_SERVICE_ACCOUNT_JSON
- OPENAI_API_KEY
- STRIPE_SECRET_KEYBuild & Release Runbook
Write a runbook so anyone can build and ship a release without you.
Include exact commands, signing steps, and store submission notes.
# Release runbook
yarn install
yarn build:ios
yarn build:android
# Upload .ipa via Transporter
# Upload .aab via Play Console internal trackTransferring Store Accounts
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
Domains, Email & Backend
Transfer infrastructure ownership cleanly.
- Move domains via registrar transfer codes
- Reassign cloud project billing
- Hand over DNS and email forwarding
Customer & Data Continuity
Users must not notice the change. Plan for:
- Support inbox migration
- Privacy policy / data controller update
- Push notification credentials transfer
A Handover Checklist Snippet
Track progress with a simple checklist you can run through with the buyer.
# Handover progress
[x] Repo access granted
[x] Store transfer initiated
[ ] Domain transfer code sent
[ ] Secrets vault shared
[ ] Runbook reviewed live on callTransition Support Window
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.
Closing the Loop
After transfer, revoke your own access to repos, accounts, and secrets. This protects both parties and finalizes the separation.
Quick Check
Test your understanding of clean handovers.
Recap
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.
Frequently asked questions
Is the “Planning a Clean Handover & Knowledge Transfer” lesson free?
Yes — the full text of “Planning a Clean Handover & Knowledge Transfer” is free to read here on the web, and the Indie Hacker Mobile Apps course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Indie Hacker Mobile Apps course, upgrade to CoddyKit PRO.
What will I learn in “Planning a Clean Handover & Knowledge Transfer”?
Learn how to document, package, and transfer everything a buyer or new maintainer needs so your indie mobile app can change hands smoothly. You practise Indie Hacker Mobile Apps with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Indie Hacker Mobile Apps?
No prior experience is required. Indie Hacker Mobile Apps on CoddyKit is structured for beginners through advanced learners; this is — lesson 4 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Planning a Clean Handover & Knowledge Transfer” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Indie Hacker Mobile Apps lesson?
Yes. Every Indie Hacker Mobile Apps lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Maintaining & Updating Legacy Apps
- Exploring New Mobile Technologies
- Valuation, Acquisition, or Scaling
- Planning a Clean Handover & Knowledge Transfer