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 consisting of one man. He had run it for thirty years, from an era when IT meant machines you could touch. Desktops, printers, cables, the shop floor. He was good at it, the company trusted him, and he was getting ready to retire.

That sentence is the whole problem. When a one-person IT department retires, everything that person knows retires on the same day, and everything that person never got to leaves with him as unfinished business. 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, still carrying production workloads
• A PC fleet and a network both due for the kind of refresh that is a project, not a repair
• Email and office tools that predated the cloud, with a migration nobody on site had done before
• And thirty years of knowledge about how it all fit together, stored in exactly one place

None of this was neglect. It was one capable person keeping a business running for decades, in a field that eventually moved past the era he was trained in. Cloud migrations were simply not the work of his generation of IT, and he had the self-awareness to know it. The question was how to get the company modern before his retirement date arrived, without shoving aside the man who had earned that date.

What we did

Co-managed IT, with the split drawn along an honest line: he kept what he was best at, and Tech Dynamix took what was coming that he had no reason to pretend was his.

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

Then, over the years leading up to his retirement, the modernization happened as a sequence of projects rather than a single upheaval:

• The end-of-life server was decommissioned, 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
• The entire site's PC inventory was refreshed
• The network was upgraded underneath all of it
• And everything got documented as it was touched, so what had lived in one head for thirty years began living in writing

The arrangement worked because it was set up with him, not around him. Nothing about the split asked him to defend territory or bluff through unfamiliar work. He stayed the person his colleagues called when a machine misbehaved, and the projects he was never going to take on happened anyway, alongside him rather than despite him.

By the time he retired, the retirement was safe to have. The environment he left behind was current, documented, and already jointly run, so the handover was a calendar event rather than a crisis. Nothing broke. Nobody scrambled. The company has been a client for more than five years and remains one.

• A cloud ERP where an aging Access database used to be
• Microsoft 365 in place of systems that predated the cloud
• A refreshed PC fleet, an upgraded network, and no end-of-life server anywhere in the building
• Backup, business continuity, security, and monitoring running as services rather than depending on any one person's presence
• Thirty years of institutional knowledge captured in documentation 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 not the week after that person leaves, when the knowledge is already gone and the projects are already overdue. It is the years before, while the person who knows everything is still there to be part of it. Done that way, co-managed IT is not a replacement for anybody. It is how a company says thank you to thirty years of service without betting the business on the retirement party.