Transfer Checklist

GitHub, GitLab, Bitbucket — transfer ownership or add buyer as owner and remove yourself post-close.

Create a secure handoff (1Password, Bitwarden) with all .env values, API keys, and credentials.

GitHub Actions, Vercel, Railway, Render — buyer needs to know how to deploy without you.

Post-transfer, revoke any personal tokens so only the buyer has access.

Transfer the account itself where possible, not just add the buyer as a member.

Namecheap, GoDaddy, Cloudflare — document the DNS setup including all records.

Supabase, PlanetScale, MongoDB Atlas — transfer the project and provide a recent backup.

Stripe account transfers require business verification. Start this process early — it takes time.

Include domain authentication (SPF, DKIM, DMARC) records in the DNS handoff.

Export historical data and transfer account ownership so buyer has full history.

Change email, phone, and recovery options to buyer's details before handoff.

Apple and Google both have formal transfer processes. Budget 1–2 weeks for approval.

Transfer admin rights and remove yourself (or negotiate a transition period as moderator).

Export subscriber list and transfer account, or migrate to buyer's existing email platform.

Architecture, key decisions, known issues, tech debt. A 2-page doc saves the buyer weeks of confusion.

List every external service, its purpose, and what breaks if it goes down or the key expires.

Any existing help docs, onboarding flows, or support materials should transfer with the product.

Warm intros build trust and reduce churn post-acquisition. Agree on this scope in the purchase agreement.

Signed by both parties before any access is transferred. Use a lawyer or DayXero's standard APA template.

A signed IP assignment is your proof that the code, brand, and assets legally belong to you.

No unpaid contractors, subscriptions, or outstanding bills should transfer to the buyer.

If the product operated under an LLC or Ltd, agree whether it transfers or winds down.