SAP Layoffs 2026: What the AI Restructuring Means for ERP Hiring

SAP is trimming 1 to 2 percent of its 100,000-plus workforce every year as a permanent policy, with 82 cut at the Palo Alto research center in November 2025 and a steady drumbeat of role eliminations tied to the company’s AI restructuring.

The Walldorf line is that this is “continuous optimization.” For hiring managers, it means a slow, predictable trickle of senior SAP talent entering the market in the same window that the December 2027 ECC end-of-support deadline forces 60-plus percent of customers into S/4HANA migrations they have not started. Supply and demand aimed straight at each other.

Last updated: May 13, 2026

Gregg Flecke, KORE1. I’ve been placing SAP talent for nearly three decades, mostly into financial services, insurance, HR outsourcing, and healthcare. Disclosure first: we collect a placement fee when you hire through our IT staffing services practice. That biases the take below toward “the candidates exist and are easier to land than your competitors realize.” Worth saying out loud.

What follows is built from California WARN filings, the public restructuring announcements out of Walldorf, Gartner migration data, and our own pipeline. SAP layoffs do not behave like the rest of the 2026 cycle. They are not a single morning email to ten thousand people. They are a quarterly drip that nobody outside the company tracks closely, while the people on the receiving end are some of the most expensive ERP specialists in the world.

What “Continuous Optimization” Actually Means

SAP’s CFO Dominik Asam told the German daily Handelsblatt in late 2025 that annual job cuts at the company would now run roughly 1 to 2 percent of the global workforce, every year, indefinitely. He compared it to brushing your teeth. The framing landed with employees about how you would expect.

Math it out. SAP carries roughly 100,000 employees globally. Two percent is two thousand jobs. Every twelve months. Forever.

Most coverage of the 2026 SAP situation traces back to the original restructuring announcement from January 2024, when SAP said it would reorganize 8,000 positions to make room for an AI-focused future. TechTarget broke down the original plan: roughly two-thirds of those 8,000 employees would be re-skilled internally or moved into voluntary leave programs, with the remaining third taking the hardest landings. Tech Monitor’s reporting noted SAP committed nearly a billion euros in AI investment by end of 2025. CEO Christian Klein, in his own words, warned employees the AI shift would be “as painful as the cloud shift” was a decade ago.

What did not get covered as widely is that the 8,000-position reset was the floor, not the ceiling. SAP made that explicit in late 2025 when Asam used the brushing-your-teeth analogy. It is no longer a one-time restructuring program. It is policy.

The most concrete recent action lives in a California state filing. SAP America filed a WARN notice dated October 6, 2025, eliminating 82 positions at its Palo Alto research center at 3410 Hillview Avenue. The cuts took effect November 21, 2025. Roles listed in the filing include project consultants, quality specialists, and development experts. The Palo Alto site is part of SAP’s global Labs Network focused on artificial intelligence, cloud computing, and data analytics, per the KRON4 coverage of the filing.

Eighty-two. Tiny number against a 100,000-employee global headcount, and the kind of filing that would not make headlines on its own outside of an SF Chronicle business briefing, but stacked on top of the Sozialplan-driven reductions in Germany and the rolling departures across India, Singapore, and Brazil, the cadence is the actual story.

Two callouts on that table. One: I am treating the HPOM details cautiously because the only sourcing is an employee forum, not a Walldorf press release. The PM-to-architect track shift is consistent with what candidates have described to me directly in screening calls this spring, so I am including it. Treat it as directionally true, not officially confirmed.

Two: the Palo Alto cuts hit a research facility, not a sales or admin office. Project consultants and quality specialists at a Labs site are people who were building or testing actual product. That talent goes back into a market that is already short on AI-fluent SAP specialists.

The 2027 Deadline That Changes Everything

SAP confirmed years ago that mainstream maintenance for ECC EHP 6 through 8 ends December 31, 2027, with no further extensions, and customers who do not migrate to S/4HANA before that date face a roughly 9 percent maintenance premium for extended support, with some SAPinsider coverage noting extended-maintenance billing can compound to two or three times standard fees across a multi-year landscape.

The migration is not small. A typical ECC-to-S/4HANA project runs 18 to 36 months. Greenfield rebuilds and brownfield conversions both take that long; the only deciding factor on duration is the depth of your custom ABAP, the volume of master data, and how many third-party integrations you wrapped around your ECC core over the past fifteen years.

Now the part that matters for hiring. As of late 2024, Gartner research cited by multiple SI partners put licensed S/4HANA adoption at roughly 39 percent of the installed ECC base. More than 60 percent of SAP customers had not yet licensed the platform they need to run after 2027. That is the demand side.

The supply side is the SI ecosystem: Accenture, Deloitte, Capgemini, the Big Four, plus a long tail of mid-market boutiques, none of which can scale headcount fast enough to absorb 60 percent of the global ECC base moving inside an 18-to-36-month window regardless of how aggressively they recruit through 2026. That is not a forecast. That is arithmetic.

One client of ours, a $400M industrial manufacturer in Texas, started their S/4HANA discovery in October 2024. They wanted to be live by mid-2026. As of last month they had still not closed their preferred SI partner because the firm could not commit a lead architect until Q3. They ended up split-sourcing: a boutique SI for the functional build, two of our contract S/4HANA specialists for integration work. That story is not unusual in our queue right now. It is becoming the default.

So SAP is shedding specialists. Customers need specialists. Most of those specialists are not going to land at the Big Four, who are already booked. The mid-market, the SI long tail, and end-customer internal teams are where this pool lands. If you run hiring at any of those, the next 18 months are the window.

Three SAP Talent Profiles Worth Hiring Right Now

Not every SAP resume carries the same shape, the displaced pool is heavier in some areas than others, the cost-to-hire math varies sharply by profile, and the strategic value to your team depends entirely on which slice of the cohort you can actually identify and screen against during intake. Three profiles are worth knowing in detail.

1. ABAP Developers with S/4HANA Modernization Chops

The classic SAP ABAP developer is not what hiring managers should be looking for. The valuable ones are the ABAP devs who actually rewrote their craft over the past four years. RAP (RESTful ABAP Programming Model). Fiori/UI5 front-ends. CAP and BTP extensions instead of monolithic Z-tables. Eclipse-based ADT instead of SE80. These are the engineers who can take a 15-year ECC custom mess and refactor it into clean S/4HANA-native code without burning the audit trail.

What to screen for: have they built anything in BTP? Do they have a public Fiori demo or a SAP Community profile? Can they explain the difference between a CDS view and a classic SE11 table maintenance dialog without flinching? If yes, you are looking at the right candidate.

What hiring teams miss: senior ABAP developers from German, Indian, or Bay Area SAP product teams often do not put “ABAP” first on their resume anymore because they have rebranded themselves as full-stack BTP developers or platform engineers. Keyword searches for “ABAP” will skip them. Search for SAP, BTP, CAP, Fiori, S/4HANA Cloud, and read the body of the resume, not the headline.

2. Functional Consultants from the Labs Cuts and PM Eliminations

The Palo Alto WARN listed quality specialists and project consultants. SAP product organizations call those roles “functional consultants” in customer-facing contexts. Add in the HPOM-driven Product Manager and Product Owner compression and you have a cohort of mid-career to senior FICO, MM, SD, HCM, and SuccessFactors functional people coming onto the market with deep product knowledge.

This profile slots cleanly into client-side S/4HANA implementation teams, especially at the $200M–$2B mid-market manufacturers and distributors who cannot afford an Accenture engagement but desperately need someone who has lived inside the product. They are also strong fits for boutique SI partners and for industry verticals where SAP carries deep configuration nuance (consumer goods, life sciences, automotive supply chain, and public utilities).

One thing to clear up: ex-SAP functional consultants are not the same as ex-Big-Four SAP consultants. The product-side person knows why a feature exists. The SI-side person knows how it gets deployed at fifty different clients. You want both on a migration. Do not screen them against each other.

3. BTP Architects, Hyperscaler Integration Leads, and the New “AI Architect” Track

Here is where the displaced pool gets most expensive and most valuable. SAP’s internal HPOM restructure consolidated the old technical product hierarchy into a slimmer model with central architects and tech leads. The same restructure created an “AI Architect” track designed to support the Joule and Generative AI Hub work SAP is pushing in its 2026 product roadmap.

Some of those architects are in. Some are out. The ones who are out, by reputation and via the candidate flow I am seeing, are the senior people who built BTP integration patterns, owned hyperscaler co-engineering relationships with AWS, Azure, or GCP, or shipped the analytics layer in SAP Datasphere. These are not garden-variety enterprise architects, they are senior product engineers who built the integration patterns and analytics layers that most SAP customers consume as packaged features without ever knowing the names of the teams that shipped them, sitting at the crossroads of SAP product internals, hyperscaler cloud platform engineering, and the AI feature roadmap that defines Walldorf’s 2026 direction.

For a mid-market hiring manager, this is a profile you have probably never had real access to. SAP product architects do not normally come up for air. When they do, they sign with hyperscalers, large SIs, or enterprise customers running global SAP estates. The window the 2026 restructuring opens is brief.

What This Talent Will Cost You

Comp ranges below blend Glassdoor, ZipRecruiter, Salary.com, and the SAP Salary Calculator with our own placement data from the past 12 months across financial services, insurance, and HR outsourcing clients. The ranges are US, full-time direct-hire base, with reasonable bonus and equity layered in for senior roles. Freelance and contract hourly ranges sit underneath.

Cross-reference these against our salary benchmark tool if you want to pressure-test what your offer looks like in a specific metro. Bay Area, Boston, and North Texas trend 10 to 15 percent above the midpoint. Most Midwest and Sun Belt markets sit at or just under.

One observation worth saying clearly. KORE1’s average time-to-hire across IT roles is 17 days. SAP-specific searches usually run longer (three to five weeks for the senior architect bands) because the candidate pool requires more careful pre-screening on module fluency, but the speed advantage over hiring through traditional channels still holds. Whether you use us or not, build your interview loop to close within four weeks. If you take eight, you lose every candidate worth hiring.

For Displaced SAP Employees: The Honest Read

Week one is when most of the leverage gets spent or kept, so two things matter more than the rest of the noise.

First, severance. SAP’s US standard runs in the range of two to four months of base depending on tenure, with stock components prorated against vesting cliffs. In Germany, where the bulk of SAP’s workforce sits, the works-council-negotiated social plan (“Sozialplan”) is materially more generous than US norms and includes structured transition packages. If you are negotiating in the US and have works-council colleagues in Europe, ask them what their package looks like. The contrast will sharpen what you are entitled to challenge.

Second, the non-compete. SAP’s US separation agreements typically include 6 to 12-month non-compete and non-solicitation language. Enforceability varies by state. California is largely unenforceable, full stop. Texas and most other US states depend on scope, geographic reach, and how narrowly the restricted activity is defined. Have an employment lawyer read the clause before you sign, because two hours of their billable time is the single best dollar-per-minute investment you will make in the entire transition, regardless of whether you ultimately decide to push back on the language or comply with it as written for the duration.

Where the talent is landing, based on the flow we have seen since November:

• Big Four practices. Hiring on S/4HANA delivery teams, especially at Deloitte and Accenture. Comp is competitive with SAP product roles but the travel and utilization expectations are different from product life.
• Boutique SI firms. The mid-tier integrators (think Cognitus, NTT Data, Spinifex IT, Argano, and regional players) are moving fastest because they need the talent more urgently than the big firms do. Faster close cycles. Less bureaucracy. Often a more interesting client mix.
• End-customer internal teams. Mid-market manufacturers and distributors running ECC-to-S/4HANA programs want someone who has lived inside the product. They will pay competitively for that. The 17-day fill window we see on these roles tells the story.
• Hyperscaler SAP teams. AWS, Azure, and GCP all run dedicated SAP co-engineering organizations. They have been quietly hiring out of SAP for years. Pace picked up in Q1.
• Adjacent ERPs. A small but real fraction of senior SAP people pivot into Oracle NetSuite, Workday, or Oracle Cloud ERP. The product overlap is partial, but the underlying ERP rigor ports. If you want context on what those moves look like, read our coverage of the NetSuite layoffs and where that ERP talent landed.

Two pieces of pragmatic advice for the displaced.

Do not undersell the BTP and AI work on your resume. Most hiring managers outside Big Four practices do not know what BTP is. You have to teach them in the first thirty seconds of the screen.

And do not sign the first offer that lands at 70 percent of your SAP base. The 2027 deadline is your leverage. Customers know they need you. Negotiate accordingly.

Common Questions Hiring Managers Are Asking

Is SAP actually replacing humans with AI in 2026, or is that PR cover for cost cuts?

Partly true, mostly cost optimization. SAP is genuinely embedding AI into Joule, Datasphere, and the BTP layer. The headcount reductions are real, but they pre-date the AI story and would have happened on the cloud-transition math alone. AI gives the cuts a cleaner narrative. The 1 to 2 percent annual policy is real and will continue regardless of how AI features perform.

Should we wait for Big Four firms to free up capacity, or hire SAP talent directly now?

Hire now. The SI capacity crunch is structural, not temporary. With more than 60 percent of ECC customers still un-migrated and an 18-to-36-month average project length, Accenture and Deloitte will not have lead architect availability until 2027 at the earliest, which is exactly when you need to be live. A split-source model (boutique SI plus internal hires plus a contract S/4HANA architect on retainer) lands faster and costs less.

What does an ex-SAP ABAP developer actually port to outside of SAP?

If they have rewritten their craft in RAP, CAP, and BTP, they port to any enterprise platform-engineering role where deep data modeling and clean abstraction matter. Salesforce platform development. Workday integrations. Oracle Cloud ERP customization. Custom enterprise Java or .NET. Pure ECC ABAP, on its own, ports poorly outside the SAP ecosystem.

How fast can a displaced SAP consultant realistically land a new role?

Three to eight weeks for functional consultants and ABAP developers, depending on geography and seniority. BTP and AI Architect-track candidates often have multiple offers inside three weeks. The senior product architects who do not have a public profile (most of them) take longer because the market does not know they exist until a recruiter pulls them out.

Do we really need 18 months for an S/4HANA migration if we are a $200M mid-market company?

Usually, yes. Brownfield conversions can hit 12 months if your ECC custom code is minimal and your master data is clean, which it rarely is. Greenfield rebuilds force you to redesign your business processes, which is the right thing to do but adds time. Plan on 15 to 18 months minimum from go-decision to go-live. Anyone selling you nine months is either lying or planning a glorified lift-and-shift that you will pay to fix later.

What is the difference between an ex-SAP functional consultant and an ex-Big-Four SAP consultant?

The product person knows why the software works the way it does. The SI consultant knows how it gets installed at fifty different companies. Both are valuable on a migration team. Treat them as complementary hires, not substitutes for each other.

The Window Is Open and Closing

SAP is going to keep doing this. The “brushing your teeth” framing is not a one-quarter story. Expect another 1 to 2 percent of the global workforce to come onto the market every year through 2028 at minimum.

The 2027 ECC deadline is fixed. The SI capacity is finite. The talent pool is real and findable, if you know where to look and what to screen for.

If you are hiring SAP talent in the next 12 months, or you are an SAP specialist trying to understand what the market actually pays right now, reach out to our team. We will not pitch you. We will tell you what we are seeing in the actual queue. For broader context on ERP hiring patterns in this cycle, our coverage of the Oracle 2026 layoffs and displaced talent flow is the closest sibling read.