Skip to content

Handing the business to a successor, which accounts and licences transfer

A handover is list-work. Who owns what, who can pay, who is admin where.

Try this first

  1. 1Make a list of every system where you are admin or owner. Domain registrar, hosting, mail tenant, accounting, bank, chamber of commerce, Google Business Profile, social media, every SaaS. Cross-check inbox logins and bank statements so nothing is missed.
  2. 2Add the successor as a second admin or owner everywhere before you remove anything. Add first, test, then remove yourself, not the other way round.
  3. 3The domain registrar is the most sensitive. Whoever owns the domain can hijack the mail. Confirm a written handover and a test login by the successor before you leave.
  4. 4Accounting and bank run on separate tracks with the bank and the accountant. Plan those separately, they often take weeks.
  5. 5Write a handover document listing every system, account, licence, contract, renewal date, and who owns which password. Better too thorough than too thin in this document.

When to bring us in

If the handover touches a live customer relationship or a major SaaS licence whose annual renegotiation falls during the handover, we will help build the runbook. That is not overcaution.

See also

None of the above fits?

Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.

Who are you?

For the AI question we need your email and company, so we can follow up if the AI gets stuck, and to prevent abuse.

Limited to 2 questions per hour and 5 per day, kept lean so the AI stays useful. For more, contacting us directly works better for you and us.

Or skip the DIY entirely

Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.