Free checklist

Project handover checklist

A co-founder leaves, a teammate takes over, or you sell. Go asset by asset so nothing stays stuck in one person's account.

Ticks are saved in this browser only. Exact steps vary by provider, so check each provider's current help pages.

Domain

Write down the registrar, expiry date and who pays for renewal.
Move the domain to the new owner's registrar account, using the registrar's internal transfer or the auth code.
Update the registrant contact details.
Check DNS still points to the right places after the move.

Email and recovery

List every account whose recovery email or phone belongs to the person leaving.
Move recovery to a project address the new owner controls.
Hand over 2FA: add the new owner's authenticator, then remove the old one.

Code (GitHub or similar)

Make the new owner an owner of the organization before removing anyone.
Move repos from personal accounts into the organization.
Rotate deploy keys and tokens the leaver created.

Hosting and database

Add the new owner to the hosting team (Vercel, Netlify, Railway…) with owner rights.
Change the billing card.
Rotate environment secrets and database passwords.

Payments

Check who the payment account (Stripe, Lemon Squeezy, Paddle) legally belongs to. It may need a new account, not just a new login.
Update the payout bank account.

Tools and subscriptions

Notion, Slack, Figma, AI tools: transfer workspace ownership.
Cancel or move every subscription on the leaver's card.
Settle up shared costs to the handover date.

Audience

Social accounts, newsletter list, app store accounts: add the new owner, then transfer.
Analytics and search console: add the new owner as owner.

WhoOwnsWhat.xyz will build this list for your project automatically and track each step. Join the waitlist.