Skip to main content
Operations8 min read

Taking over a server nobody documented: a checklist for the business owner

When the person who set up your server leaves, the risk is rarely the machine. It is the accounts, backups and decisions nobody wrote down. A checklist for the business owner, in the order that protects you.

A server that has run quietly for years can become a worry overnight. The person who built it has moved on, or the employee who looked after it has left, and nothing was written down. You still depend on it for email, files or your website, and you are not sure who can sign in to what.

This checklist is for the owner or manager of a small team with no IT department, where the person who built the server was a freelancer, a part-time contractor or one employee. It is written for you, not for the administrator. It puts the questions in the order that protects you: first who controls what, then what to leave alone, then what to ask whoever takes over.

In short: before anyone changes anything, confirm that your business, not an individual, controls the domain, hosting, backup and billing accounts around the server. Pause changes that are not urgent, close the leaver's access once your own is secure, and get a written audit before any repair.

Six things to confirm before anything else

Most trouble with an inherited server comes from the accounts around it, not the machine. One provider's guide to inherited infrastructure, published on 26 October 2026, puts confirming control of every account first, and we agree. For each item below, find out whose name and email address it is under, and whether two people who work for you today can sign in.

  1. —The domain registration. Whoever registers a domain enters a contract with a registrar and manages the domain through it, as ICANN explains for registrants. Find the registrar with a public lookup, then check that the registered owner is your business and that the account's email address is one you can read. A registration in the leaver's name, or tied to their personal email, needs fixing first. Ask the registrar before you change the registered owner: under ICANN's transfer policy, a change of registrant can put a 60-day lock on moving the domain to another registrar.
  2. —DNS. These records say where your email and website live. They may be managed at the registrar or at a separate service. Find out where, and who can edit them. Do not change any record yet.
  3. —The hosting or cloud account. This is the account with the company that runs the server. Check whose it is, which email address receives its messages, and whether you could prove to the provider's support team that the business owns it.
  4. —Backup storage. Find out where the copies go and under whose account. If the backups sit in the leaver's personal account, they may disappear with it.
  5. —Billing. Check whose card pays for hosting and domain renewals, and when the next renewals fall. A renewal that fails on a closed card is an easy way to lose a service.
  6. —Logins to the server itself. Who has administrator access, how they sign in, and where those credentials are kept. Do not search old chat history for passwords. Ask the leaver, if they are reachable, and note what you learn as a lead to check, not as fact.

What to leave alone in the first week

Pause changes that are not urgent: no upgrades, no deleting files that look unused, no moving things to tidy up. You do not yet know what depends on what, and in an undocumented setup those dependencies tend to show themselves only when something is removed. The guide above makes the same point and recommends a written audit before any repair, upgrade or migration. Urgent security fixes are the exception.

Decide, too, who will answer an alert tonight if the server fails, and who is the backup. In a small team that may be you, then one named person. What matters is that it is agreed before something breaks.

Close the leaver's access, in the right order

The UK National Cyber Security Centre's guidance for small organisations, published on 9 April 2026 and reviewed on 21 July 2026, notes that former staff accounts often stay active. It advises removing or disabling accounts nobody needs and reviewing who can reach important accounts every few months.

For an inherited server, the order matters:

  1. —Make sure you have your own working administrator access.
  2. —Disable the leaver's accounts.
  3. —Change any shared password they knew.

Doing it in this order stops you locking yourself out. The same guidance recommends passkeys where they are supported and two-step verification where passwords remain. For your own laptops, it also advises a separate standard account for everyday work, with administrator access used only when needed. Keep the new credentials in a shared password manager, not in a spreadsheet or a chat thread. We say more about this in who has access to what.

Is the system still supported, and are the backups real?

Ask what operating system the server runs and whether it still receives security updates. Operating systems stop getting them after a published period. For example, Canonical's release page says Ubuntu long-term support releases receive five years of standard security maintenance. A server on a system that no longer gets updates is not an emergency this week, but it is a decision to make deliberately.

Then ask where the backups go, who holds that account, whether they are stored somewhere other than the server itself, and when anyone last restored one. The NCSC's guidance on backing up data says that once a backup exists, it is important to know how to restore it and to check that it holds all your important data. If nobody knows, assume they are untested. An untested backup is a hope, not a backup, a point we make in the handoff problem.

You may not be able to answer these questions yourself. That is normal, and it is what the audit is for.

What to ask whoever takes over

The guide we have been citing says a written audit should come before any repair. In plain terms, it is an inventory of what runs, who can reach it, whether a backup has ever been restored, how out of date everything is, and what could go wrong first. For a small setup, what you want from it is a short list of what to fix first. The guide also suggests pricing the audit on its own and quoting any repair separately, since nobody can price work on a system they have not yet looked at. Ask for the scope in writing so the cost is predictable.

Questions worth asking any contractor or provider:

  • —What will you check before you change anything, and will I receive it in writing?
  • —Is the audit a fixed price, and how will repairs be quoted separately?
  • —Who will hold the accounts and passwords at the end? It should be you.
  • —What documentation will I have afterwards, and could another administrator follow it?
  • —If the server holds personal data, will there be a written agreement about how it is handled? Under Article 28 of the GDPR, anyone handling personal data for you must be bound by a written contract and may act only on your documented instructions. This is general information, not legal advice.
  • —What is not included, and what do extra tasks cost?
  • —Can I leave at the end without being locked in?

Whether to hire someone, use a contractor, use a managed provider or move to something simpler is a choice the audit should inform, not one to make blind. When we look after a setup someone else built, we start with a review and a short written summary before changing anything, and you keep the accounts and the passwords.

What this checklist cannot tell you

It tells you whether you control the setup, not whether the setup is sound. A server can have every account in order and still be out of date, badly backed up or poorly configured. It also cannot replace someone who can read the server and say what is on it. The way to prove ownership differs between registrars and hosting providers, so check each one's own process. If the leaver is reachable and on good terms, a conversation about what they remember is cheap and useful. Treat what they say as leads to verify, not as documentation.

Common questions

What should I do first when my IT person leaves? Confirm that your business controls the domain, hosting, backup and billing accounts, and that two people who work for you today can sign in to each. Pause changes that are not urgent. Then get a written audit before any repair, upgrade or move.

Can I change the passwords myself straight away? Only after you have your own working administrator access, otherwise you can lock yourself out. Then disable the leaver's accounts, change any shared passwords they knew, and keep the new ones in a shared password manager that more than one person in your business can open.

Can the server wait while I decide what to do? If it is running and no alerts are firing, a short pause to establish control and arrange an audit is reasonable. The risk is that nobody can say how healthy it is without looking, so do not leave it for months.

If you would like a second pair of eyes before you decide, the free 30-minute review is a good place to start. We look at what you run, who looks after it and what could go wrong, then send a one-page written plan with a fixed quote within two business days. The details are on our services page.

New posts are also available by RSS. Add the address to any feed reader.

We set up and look after open-source tools for small teams, and move you off paid tools gradually and carefully. A free 30-minute review is a good place to start.

See our services

Everything we set up is open-source software. TrySelfHost is independent and not affiliated with or endorsed by any of these projects. We sell setup, migration and care, not the software. Product names belong to their owners.