IT Layoffs vs. 2026 Deadlines: Who Runs the Work?

The layoffs are real. So are the deadlines. The uncomfortable question underneath both is a simple one: in the second half of 2026, who is actually running your migrations?

This post is not a hot take on the job market, and it is emphatically not a pitch that any of this is good news. People losing their jobs is not an opportunity to be spun. What it is, for the leaders still holding a stack of immovable 2026 deadlines with a smaller team than they had in January, is a planning problem. The Microsoft end-of-support calendar and the federal compliance calendar do not pause when a team shrinks. This is about how you keep continuity when the people who held the institutional knowledge are no longer in the building — and how a senior bench-on-demand supplements a stretched team for the scoped work it can't absorb, without touching your headcount plan.

The data, framed honestly

First-half 2026 was a hard stretch for the tech labor market, and it's worth being precise about what the numbers do and don't say.

• Challenger, Gray & Christmas (March 2026 report): the technology sector announced 52,050 job cuts in Q1 2026 — the highest first quarter since 2023 and up roughly 40% year over year. In March 2026 alone, AI was the most-cited reason, named in 15,341 of the cuts.
• Challenger, Gray & Christmas (February 2026 report): year-to-date hiring plans across sectors fell 56% — the other side of the same coin. It isn't only that more roles were cut; it's that fewer were being created to absorb the displaced.
• layoffs.fyi (event tracker, mid-May 2026): roughly 108,000+ tech employees across about 137 companies year to date. This is a crowdsourced, event-level tracker whose methodology differs from Challenger's announced-cut survey — treat it as a directional aggregate, not a precise census, and don't stack it on top of the Challenger figure as if they measure the same thing.
• TechTarget documents a consequence that matters more to operations leaders than the headline count: tech layoffs drive loss of internal knowledge and increased operational risk. The number is the story everyone reports; the knowledge drain is the story that lands on your migration timeline.

The risk: knowledge drains, and then the calendar arrives

A layoff or a quiet non-backfill isn't only the loss of a pair of hands. It's the loss of context. The engineer who left was the one who knew that the SharePoint 2019 farm has a custom workflow nobody documented, that the Exchange hybrid config has a connector someone hand-tuned in 2021, and that the AD has a service account three apps quietly depend on. TechTarget's framing — loss of internal knowledge, increased operational risk — is the polite version. The operational version is that a project that was 60% understood is now 20% understood, and the deadline didn't move.

And 2026's deadlines are unusually stacked. These are the projects that don't wait for a req to clear and a new hire to ramp:

• SharePoint Server 2016 and 2019 — end of support July 14, 2026 (about 30 days out as of this writing). There is no Extended Security Update program for SharePoint Server at any price. After this date you are running unpatched, or you have already moved to SharePoint Server Subscription Edition or SharePoint Online.
• Exchange Server 2016/2019 — paid ESU bridge ends end of October 2026. Mainstream support ended October 14, 2025; the ESU Period 2 bridge is the final extension, with no further runway. Then it's Exchange Server Subscription Edition or Exchange Online.
• Windows 10 — end of support was October 14, 2025. The mid-market is now living in the aftermath: mixed fleets, Year-2 ESU decisions, and the modernization work that got deferred during the deadline crunch.
• Kerberos RC4 enforcement — rollback removed at the end of Q2 2026 (around June 30). Environments still leaning on RC4 need to have moved to AES before the fallback disappears.
• CMMC Phase 2 — third-party (C3PAO) assessments required from November 10, 2026 for in-scope defense contractors. Self-attestation stops being enough for the levels that require an external assessment.

What stalls if the owner leaves

The collision is the point. Map each 2026 deadline to the institutional knowledge it depends on, and the exposure becomes concrete:

A decision tree: keep it in-house, or hand it to a scoped bench

Not every project should go to an outside bench, and we'd be the wrong people to trust if we said otherwise. The work that belongs with your internal team is the work that is the team's standing job: running the environment, knowing the business, holding the relationships, owning the roadmap. The question is narrower — which of the deadline-driven projects sitting on top of that job should you keep, and which should you hand to a senior bench for fixed-scope delivery?

A practical way to sort it:

1. Is there a hard external deadline you cannot move? If no, you have room to backfill and run it in-house at a sane pace. If yes, keep going — the calendar is now driving.
2. Does your current team have the bandwidth to deliver it on time on top of running the business? If yes, keep it in-house. If no — and a thinned team usually means no — a scoped bench is the pressure valve.
3. Did the project's institutional knowledge just walk out the door? If the person who owned it has left, you're paying for archaeology either way. A senior bench that does this work repeatedly reconstructs the runbook faster than a new hire ramping cold.
4. Is it a one-time push or an ongoing responsibility? One-time, bounded, has-a-finish-line work (an EOL migration, a tenant merge, a CMMC readiness sprint) is exactly what a fixed-scope SOW is for. Permanent, always-on responsibility belongs to permanent staff — hire for that, don't rent it.
5. Would handing it off protect your remaining team's bandwidth? If taking one immovable project off the stack keeps the people you kept from burning out, that's not a cost — that's retention insurance.

The pattern that falls out of this is consistent: keep the standing job and the roadmap in-house; hand the bounded, deadline-driven, knowledge-intensive project to a senior bench when your team is too lean to absorb it without slipping the date or breaking the people.

How a fixed-fee SOW transfers the risk — without touching headcount

The mechanism matters, because "bring in help" can mean very different things. Renting hours by the body shifts almost no risk to the vendor — you still own scope creep, rework, and the question of whether the person actually knows what they're doing. A fixed-scope, fixed-fee Statement of Work is a different instrument.

• You buy an outcome, not time. "SharePoint 2019 retired and content landed in M365, validated, before July 14" is a deliverable with a definition of done — not a timesheet.
• The delivery risk sits with the firm. If the work runs long, hits surprises, or needs rework, that's on the fixed fee, not your budget. Scope creep is the vendor's problem to manage, which is exactly the incentive you want.
• No headcount, no payroll tail. No new salary, no benefits load, no severance exposure when the project ends. Your org chart and your headcount plan are untouched. When the SOW closes, the cost stops.
• It supplements, it doesn't supplant. The bench takes one project off the stack and hands it back documented. Your team keeps the environment, the knowledge, and the relationships. This is reinforcement for a stretched team, not a quiet replacement of it.
• Knowledge comes back to you. A good SOW ends with the runbook, the as-built documentation, and a handoff — so the institutional knowledge that left the building gets rebuilt and stays with your team this time.

That last point is the answer to the fear underneath all of this. The goal is not to make you dependent on an outside firm. It's to get a deadline cleared and leave your team better-documented than the departure left them.

What this costs, directionally

Consistent with how we price elsewhere on this blog: scoped project work is quoted as a fixed fee against a defined deliverable, and the real number comes out of a short discovery, not a web page. What we can offer is directional framing so the conversation starts in the right zip code.

• A focused, single-system EOL migration (e.g., a contained SharePoint or Exchange environment with clean discovery) is typically a low-five-figure fixed-fee engagement.
• A larger or multi-system push — a hybrid Exchange cutover, a tenant consolidation, a CMMC-readiness sprint with an evidence trail — scales from there into the mid-five figures and up, driven by scope and the amount of undocumented complexity discovery turns up.
• The variable that moves the number most is institutional-knowledge debt. A well-documented environment scopes fast and cheap. An environment where the owner left and nothing was written down costs more, because reconstruction is real work. The single best thing you can do to control the price is bring someone in before the project sits orphaned for a quarter.

We don't publish fabricated fixed numbers because every environment's discovery changes them. What's stable is the model: a fixed fee, a defined deliverable, a finish line, and the delivery risk carried by us rather than your payroll.

Related reading

• The July deadline in detail, with the three viable paths: SharePoint Server 2019 EOL July 2026: three paths.
• The Exchange clock and what the final ESU bridge actually buys you: Exchange Server 2019 EOL: your real migration deadline.
• The identity deadline a lean team can miss quietly: Kerberos RC4 enforcement: the end-of-Q2 2026 cliff.
• If a CMMC assessment is on your H2 calendar: CMMC Level 2 pre-assessment, and what it costs.
• The other deadline-driven exit a lean team often owns at the same time: VMware after Broadcom: exit options compared.

Sources and further reading

• Challenger, Gray & Christmas — March 2026 job-cut report (technology sector: 52,050 Q1 cuts, +40% YoY; AI 15,341 in March)
• Challenger, Gray & Christmas — February 2026 report (year-to-date hiring plans down 56%)
• layoffs.fyi — tech layoff event tracker (~108,000+ employees / ~137 companies, mid-May 2026; crowdsourced, methodology differs from Challenger)
• TechTarget — tech-sector layoffs feature (loss of internal knowledge, increased operational risk)

The 30-second version

Tech-sector cuts ran high in early 2026 — Challenger counted 52,050 technology job cuts in Q1 (up 40% YoY) while hiring plans fell 56%, and the layoffs.fyi tracker showed 108,000+ tech employees affected by mid-May. The hard numbers are concentrated in big tech; our inference (labeled as such) is that mid-market internal IT feels a knock-on version through freezes and non-backfills. Meanwhile the 2026 deadline calendar didn't move: SharePoint 2016/2019 EOL on July 14, the final Exchange ESU bridge ending in October, Kerberos RC4 enforcement at the end of Q2, and CMMC C3PAO assessments from November 10. When the team that held the institutional knowledge shrinks, those projects stall. A senior bench-on-demand supplements a stretched team for the bounded, deadline-driven work it can't absorb — fixed scope, fixed fee, delivery risk on us, headcount untouched, and the documentation handed back so the knowledge stays with your people this time.

If you have a 2026 deadline and a thinner team than you planned for, the project intake form takes about three minutes. Two-business-day response with scope and a fixed-fee range — and no pitch to replace anyone on your team.

Pro IT NW is a senior-led, vendor-neutral, labor-only Microsoft project consultancy based in Seattle and serving clients USA-wide. We supplement stretched internal teams with fixed-scope, fixed-fee project delivery — we don't replace headcount, and we don't resell software or licensing. We charge for the engineering and hand the documentation back to your team.