The IT Department Was One Man, and He Was Retiring

A manufacturer of thirty-some people had what plenty of businesses that size have: an IT department of one man. He'd run it for thirty years, starting when IT meant desktops, printers, cables and the shop floor. He was good at it and the company trusted him, and he was getting ready to retire.

When a one-person IT department retires, everything that person knows leaves the same day, and any work he never got to stays behind unfinished. This company had a fair amount of both:

• The business ran on an ERP built in an aging Access database, well past the point where that was comfortable
• A server at the end of its supported life was still carrying production workloads
• The PC fleet and the network were both due for a refresh large enough to be its own project
• Email and office tools predated the cloud, and nobody on site had done that migration before
• Thirty years of knowledge about how it all fit together was stored in exactly one place

None of this was neglect. One capable person had kept a business running for decades in a field that eventually moved past the era he trained in. Cloud migrations weren't the work of his generation of IT, and he knew it.

The goal was to get the company current before his retirement date, without pushing aside the man who had earned that date.

Tech Dynamix set up co-managed IT with the split drawn along a clear line. He kept what he was best at, and we took on the new work he had no reason to pretend was his.

He kept doing on-site desktop support for the people who had relied on him for years. Tech Dynamix took cloud services, security, backup and business continuity, and monitoring, the work that runs in the background whether or not anybody is in the building.

Over the years leading up to his retirement, the modernization happened as a series of projects:

• The end-of-life server was decommissioned and its workloads moved off aging hardware
• The Access-based ERP was replaced with a cloud ERP, taking the business off a database that one failure could have ended
• Email and office tools moved to Microsoft 365 through a planned cloud migration
• The PC inventory across the site was refreshed
• The network was upgraded underneath all of it
• Everything was documented as it was touched, so knowledge that had lived in one head for thirty years went into shared documentation

The arrangement worked because it was set up with him. Nobody asked him to defend territory or bluff through unfamiliar work. He stayed the person colleagues called when a machine misbehaved, and the projects he was never going to take on got done alongside him.

By the time he retired, it was safe to. The environment he left was current and documented, and we were already running it alongside him, so the handover was a date on the calendar and nothing broke. The company has been a client for more than five years and still is.

• A cloud ERP where the Access database used to be
• Microsoft 365 in place of systems that predated the cloud
• A refreshed PC fleet and an upgraded network, with no end-of-life server left in the building
• Backup, business continuity, security and monitoring running as services that don't depend on one person being there
• Thirty years of institutional knowledge written down before it walked out the door

The lesson is about timing. The right moment to bring in help alongside a one-person IT department is the years before that person leaves, while they're still there to take part. Waiting until the week after means the knowledge is gone and the projects are overdue.

Done that way, co-managed IT is how a company thanks someone for thirty years of service without betting the business on the retirement party. If your manufacturing business relies on one long-serving IT person, we wrote more in when your IT person needs a team behind them.