Your Only IT Person Just Quit. What Should the Business Do Next?

When the only person managing your company’s IT resigns, finding a replacement may not be the first priority.

That employee may control Microsoft 365, servers, firewalls, backups, domains, security tools and vendor accounts. They may also hold years of undocumented knowledge about how those systems work.

The immediate goal is business continuity: keep control of critical systems, protect access and identify what knowledge is leaving.

Secure Critical Access

Start with systems capable of controlling users, data or business operations.                                                                                                                                                             

Review:

• Microsoft 365 or Google Workspace
• Servers and Windows domains
• Firewalls, VPNs and network equipment
• Backup and cybersecurity platforms
• Website hosting and domain accounts
• Internet, phone and software vendor portals

Remove the departing employee’s access at the appropriate time, but first make sure the company has another working administrator account.

Do not automatically change every password. Some applications or automated processes may depend on existing service credentials.

Confirm the Business Owns Its IT Accounts

Paying for a service does not always mean the company controls the account.

For each critical system, confirm:

• The company controls the administrator login
• Recovery information uses a company-controlled address or number
• Billing belongs to the business
• Vendor contacts are documented
• Credentials are stored somewhere authorized employees can access

Pay particular attention to services registered using the departing employee’s personal email address.

Verify Backup and Recovery

Before making major system or access changes, verify the recovery position.

Check:

• When the last successful backup completed
• Which systems and data are protected
• Where backup copies are stored
• Who has access to the backup platform
• Whether important data can actually be restored

A successful backup notification is not the same as a tested recovery.

Assign Temporary IT Ownership

The resignation does not stop daily technology work.

Someone still needs responsibility for:

• Password resets and account changes
• Employee onboarding and offboarding
• Device setup
• Patching and security alerts
• Backup checks
• Vendor support cases
• Urgent IT incidents

Outside IT support can provide temporary coverage while leadership decides what comes next.

Decide What the Next IT Model Should Be

Do not automatically recreate the same one-person dependency.

Consider:

• Internal IT: dedicated day-to-day employee support
• Managed IT: outside team handling defined IT responsibilities
• Co-managed IT: internal staff supported by an MSP for additional coverage and specialist skills

The right model depends on your systems, support needs, required expertise and growth plans.

CONCLUSION

An IT resignation becomes a larger business problem when system access, documentation and technical knowledge exist only with one employee.

Alpha Network Systems provides IT Management, help desk support, cybersecurity, cloud and onsite server support, disaster recovery and strategic IT planning for businesses in Greeley, Northern Colorado and the surrounding region.

Has an IT departure exposed gaps in your access, documentation or support coverage? Contact Alpha Network Systems at 970.373.4546 or support@alphanetworksystems.com

Alpha Network Systems provides IT Management, help desk support, cybersecurity, cloud and onsite server support, disaster recovery, communications, web development, and strategic IT planning for businesses in Greeley, Northern Colorado, and the surrounding region.

Last updated: August 2026
By Rob Citrino, CEO at Alpha Network Systems. Rob has spent 30 years providing CIO advisory to C-Suite, ownership and IT Management teams for local and national companies.