Helpdesk to sysadmin: the actual path
The LinkedIn version of this transition goes: "learn Azure, get certified, network strategically, 6 months." The version I watched happen on my desk, dozens of times over nine years, was different: it took 18-36 months, it involved almost no certificates, and it ran through a specific mechanism: the problems nobody else wanted.
What actually transfers
Tier 1 gives you more real assets than it feels like. You have: production exposure to Active Directory (accounts, groups, passwords), the ticket system (which is the sysadmin's change-management system wearing a costume), the user base's actual behavior (invaluable, since sysadmins who've never done support design systems users defeat), and the escalation relationships. The gap is almost entirely on the systems side: servers, imaging, scripting, backup, networking beyond the basics.
The techs who crossed over closed that gap with a pattern so consistent it was almost a checklist:
1. They became the desk's specialist in something. Printers, VPN, imaging, Intune. Pick a system the desk touches constantly and go deeper than anyone. When the sysadmin team needed something done in that area, the name that came up was always the same tech. Every one of my techs who got pulled up had been that name for something first.
2. They took the project scut work. A Windows rollout needs bodies to image machines. A Teams migration needs people who'll sit with users. Volunteer for every one. It's paid time learning sysadmin work, side by side with the people who do it, and the sysadmin team's manager is watching how you handle it, because that manager is your actual future interviewer.
3. They scripted their own job first. PowerShell didn't click for anyone on my desk until they automated something boring they personally did daily: password reports, account disabling, machine inventories. The first script is a chore-killer; the tenth is a portfolio. And "here are my scripts, documented, with the hours each saves" is a shockingly strong interview artifact for a sysadmin role.
4. They had the meeting before the posting existed. Internal moves are made in the six months before the requisition opens. The techs who got out told the sysadmin manager they wanted the move, asked what would make them ready, and then did the list. When the req opened, they weren't an applicant; they were the known quantity. External postings get 100 resumes; internal transfers get one conversation.
What doesn't transfer, and what to do about it
Ticket speed. Nobody upstream cares how fast you closed tickets. The metrics that matter change. Start thinking in uptime, change windows, and "did I break anything," not calls per day.
Vendor certs, mostly. Internal moves at mid-size companies run on demonstrated work and trust, not paper. Certs matter more when you're jumping companies to make the move. If you're going external, the AZ-104/AZ-900 or RHCSA type stuff starts earning its keep, because you lack the internal evidence.
Waiting to be noticed. The desk is loud and the sysadmins are in a different room (or building, or timezone). Work that isn't visible to them doesn't exist. This is the step people skip and it's the one that fails quietly.
The 18-month plan, compressed: months 1-6: pick your specialty, take every project day offered, start scripting. Months 6-12: knowledge-base everything you touch, have the conversation with the sysadmin manager, ask for the readiness list. Months 12-18: do the list, visibly; apply the day a req opens, internally first, external as the parallel track. It is not glamorous. It worked, over and over.
The manager track, for contrast
Some of you don't want sysadmin; you want to run the desk. That's the other escalation, and it's a different skill entirely: scheduling, coaching, KPIs, and the strange work of being accountable for fifty people's bad days. I did it for nine years and I'll write about it separately. If you like the coaching part of tier 1 more than the fixing part, that's your tell.