It happened the way it always happens.
Your IT person — the one who set everything up, who knew where all the passwords were, who was the only one who could make sense of the server — gave notice. Two weeks. Maybe a few friendly emails after that, if you're lucky.
Now you're standing in front of your business's technology and realizing: you have no idea how any of it works. And neither does anyone else.
This Is More Common Than You Think
In small businesses, IT support often starts informally. The owner's nephew helped set things up. A friend of a friend manages the server "on the side." The person who wore the IT hat left last year, and someone else has been holding things together with digital duct tape.
The result is a business where critical systems are held together by institutional knowledge that lives in one person's head — and when that person leaves, the knowledge leaves with them.
This is called key person risk, and it's one of the most underappreciated vulnerabilities in small businesses.
What You're Actually Exposed To
When your IT person leaves without a proper handoff, here's what's likely to happen:
You lose access to things. Passwords, account logins, recovery codes — if these were stored only in someone's memory or personal password manager, they're gone. If you can't log into something, you may be stuck.
You don't know what you have. A server in a closet? An old application that's running on someone's old laptop? A vendor contract that's auto-renewing for a service no one uses anymore? You find out when something breaks or when you get a bill you can't explain.
You're starting from zero with a new provider. Anyone new you bring in to help has to reverse-engineer everything from scratch — hours of billable discovery work before they can solve a single problem. You're paying to re-do what was already supposed to be done.
Downtime while you figure it out. Every hour without functioning technology is lost revenue and frustrated clients. A planned transition could have been days. A crisis scramble is weeks.
How to Avoid the Crisis (Before It Happens)
The answer is a structured IT onboarding and documentation process — one that happens whether or not you're in the middle of a transition. Ideally, it happens before there's a crisis.
Here's what it involves:
1. A complete infrastructure audit. What do you actually have? Servers, workstations, cloud services, domains, SSL certificates, vendor contracts, backup systems. Everything.
2. Centralized documentation. All of the above, written down in plain language: what each system does, how it connects to the others, who the vendors are, what the contracts cost, and how to access everything.
3. Centralized access. All accounts and credentials stored in a password manager or access system that's owned by the business — not an individual. Shared with the people who need access. No one person's laptop is a single point of failure for the entire company's infrastructure.
4. A transition plan. What happens if your current IT person is unavailable tomorrow? Who can step in, with what information, and how fast?
5. A regular review cadence. Technology changes. A system that was documented six months ago may have been replaced or reconfigured. Quarterly or biannual check-ins keep the documentation current.
What to Do If You're In the Middle of This Right Now
If your IT person just left and you're scrambling:
- Don't panic. Whatever is working right now will keep working for a bit. Take a breath.
- Call someone. Not your nephew's friend — someone who does this professionally and can do a fast emergency audit.
- Change the critical passwords now. Anything that only your former IT person knew — domain registrars, hosting accounts, email admin, anything with your business's data — change those first.
- Ask for what they built. If you have any contact with your former IT person, ask for documentation, credentials, and a handoff conversation before they disappear. Most people will help if you ask clearly.
Want to make sure this never happens to you? The right time to do an IT onboarding and documentation project is before you're in a crisis. Let's talk about getting your infrastructure documented, centralized, and resilient — so you're never held hostage by one person's departure.
Ben is the owner of Spruce IT, a technology support and advisory service for small businesses and individuals in the Harleysville, PA area.