Software businesses have many moving parts. Plan the transfer together and take it step by step.

What to move

• The code — transfer the repository or add the buyer as owner, then remove the seller.
• Servers and cloud accounts — transfer the account, or move the app to the buyer’s account.
• The domain and DNS.
• Payment processing — Stripe, Paddle and similar accounts usually cannot be transferred. Agree how customers and subscriptions move: for example, some providers can migrate subscriptions to a new account on request.
• App store listings — Apple and Google have their own app transfer procedures; follow them from the developer accounts.
• Third-party services — email sending, analytics, error tracking, support tools, APIs and their keys.
• Customer data — move it securely and respect privacy laws. Tell customers about the new owner if needed.
• Documentation — how to deploy, run and maintain the product.

A proven order

1. The buyer creates their own accounts where needed.
2. The code and infrastructure move; the buyer deploys and tests.
3. The domain moves and traffic goes to the buyer’s setup.
4. Payments and subscriptions move.
5. Keys and passwords are replaced; the seller’s access is removed.

After the transfer

Agree a support period: the seller answers questions for a few weeks. Put it in the terms.