Rarely because your value was reassessed. Usually because your departure is expensive and inconvenient right now.

Replacing you costs a search, a notice period, a ramp-up, and whatever your absence does to a live programme in the meantime. Against that, a salary increase is cheap and immediate.

That is not cynicism. It is a reasonable commercial response to a problem that landed on someone's desk this morning. But it explains the timing, and the timing explains what follows.

Two things, and neither is in your favour.

Your employer now knows you are willing to leave. That information does not expire. It affects how you are viewed in succession planning, how you are staffed on critical work, and what happens the next time a restructure comes round.

The reason you were looking has not been addressed. If it was money alone, the counteroffer solves it. If it was scope, progression, the technology you are working with, a manager, or the fact that your role has quietly become keep-the-lights-on maintenance, none of that has changed. You have bought time.

Backfill planning frequently starts in the same week the counteroffer is accepted. Not always, and not universally, but often enough that it is worth knowing.

Because resigning is uncomfortable and the counteroffer removes the discomfort.

The new role is uncertain. The current one is known. Loyalty is real and the relationships are real. A counteroffer lets you keep all of that and get paid more, and the part of your brain that avoids risk finds it extremely persuasive.

The honest test is this: if this offer had been made two months ago, unprompted, would you still have started looking?

If yes, the problem was money and it is now solved. If no, the problem is still there and you have postponed it.

Worth knowing which one you are likely to get, before you are in the room.

The clean exit. Your employer accepts it, wishes you well, the notice period proceeds. What everyone expects, and the least common outcome when the person leaving is good.

The counteroffer. Covered above. Expect it. Prepare for it.

The hostile exit. Your new employer is disparaged, your judgment is questioned, the move is framed as a career error. It is uncomfortable by design and it works on people who have not thought about it in advance.

None of the three is personal. All three are predictable, and preparation is the difference between handling it and being handled.

Decide before you resign. Write down what would need to change for you to stay, and at what number. Then, if the counteroffer arrives, you are comparing it against something you decided calmly rather than deciding under pressure in a room with your manager.

Resign to the decision, not to the conversation. If you have accepted an offer, you have made a decision. The resignation is communicating it, not reopening it.

Expect the delayed version. The immediate reaction is usually shock. The considered response arrives days or weeks later, once your employer has worked out what your departure costs. The pressure is often heavier at week two than on day one.

Think about the notice period. Thirty to sixty days is a long time to spend somewhere you have just told you are leaving.

If you are working with a recruiter, this is where they earn their fee or fail to.

The work happens before the resignation, not after it. You should know which of the three scenarios is likely, what will be said, and what you intend to do about it. Counteroffer exposure should have been discussed in the first assessment conversation, not discovered on the day.

Through the notice period, someone should be answering the unglamorous questions that actually decide how a move feels. What the health plan covers, how 401(k) contributions run, what hardware you will get, what the first week looks like. Those feel too trivial to raise with a new employer before starting, and they are exactly the ones that go unanswered and quietly erode commitment.

Is it ever right to accept a counteroffer?

Yes, when the issue genuinely was compensation, when the new offer was marginal anyway, or when something material has changed in your personal circumstances since you started looking. It is the default answer being wrong, not the answer always being wrong.

How long do people stay after accepting one?

Varies too much for a reliable figure, and most numbers quoted on this subject come from recruiters with an interest in the answer. What is consistent is that the original reason for looking tends to resurface.

Will my employer know I was looking if I decline the counteroffer?

They will know you resigned. That is unavoidable. Whether they know where you were looking, and for how long, depends on how the process was handled.

Can I explore the market without my employer finding out?

Yes, and it is the main practical reason to work through an intermediary. A direct approach to a competitor triggers informal reference checking almost immediately. One call to a former colleague, the question gets repeated, and within days you are known to be in the market.

If you are weighing a move, registering takes a few minutes and commits you to nothing. Nothing is sent to any employer without your explicit permission, and that holds even if your current employer is a client.

The people worth hiring are load-bearing where they are. Their employer knows it.

A counteroffer is the default response, not the exception. More money, a new title, a promise of scope that was somehow unavailable last quarter. It is persuasive precisely because it removes the discomfort of change.

It is also rarely in the candidate's interest. An employer who improves terms under threat of resignation has learned the individual is willing to leave, and has bought time rather than settled the matter. Backfill planning frequently starts the same week.

What to do about it. Counteroffer exposure is established at assessment, not discovered at resignation. Before an offer goes out, you should know what the candidate's current employer is likely to do, what the candidate intends to do about it, and whether they have thought it through at all.

Expect a counteroffer on every senior hire. Plan for it, and do not take it as an insult. The whole market is competing for the same people.

Every brief opens with a requirement to hire quickly. The process then meets its real constraint, which is almost always internal.

Resumes sit unreviewed. Interview slots take a week to confirm. A decision waits for a diary.

Meanwhile the candidate is in three other conversations. Scarce, migration-proven people do not wait through a fourth round.

What to do about it. Decide before the search starts who is in the interview loop, how many stages there are, and what happens if someone is on holiday. A two-week interview process delivers a six-week hire. A process that takes five weeks to convene delivers nine, and frequently loses the strongest candidate somewhere inside it.

An experienced hiring manager recognises the right person and acts. The instinct to hold out for a comparison set is reasonable in a deep market and expensive in this one.

The most common reason, and the most fixable.

The role is described as transformation leadership. It is banded as line management. The two do not meet, and the search fails before anyone has been approached.

The numbers show why. Salary.com's median for a generic SAP Director dipped slightly between 2023 and 2025, from $181,222 to around $179,970. Over the same period, pay for scarce, migration-proven profiles moved the other way.

The market has split. A band set against a generic job title will not reach the specific profile, because the generic title is no longer what the specific profile is paid.

What to do about it. Set the band against the profile, not the title. If the band genuinely cannot move, that is worth knowing in week one, because it changes what the search can realistically deliver. It is information, not a failure.

Not fatal on their own. Decisive when the candidate has an alternative that does not require a move.

Most senior SAP professionals have delivered remotely for years and can evidence it. A five-day mandate on a role that does not require presence narrows the candidate pool considerably, and it narrows it precisely at the senior end where people have options.

What to do about it. Be clear about it at the brief, not at offer. A candidate who knows the expectation from the first conversation either accepts it or declines early. One who discovers it at offer stage declines late, and takes eight weeks of your search with them.

How common are counteroffers at this level?

Common enough to plan for on every search. The stronger the candidate, the more likely it is.

Should we match a counteroffer to keep someone?

That is a retention question rather than a hiring one, and the honest answer is that it usually buys months rather than years. The underlying reason they were looking is rarely money.

We have a fixed salary band. Is a search still worth running?

Yes, provided the band is realistic for the profile. If it is not, the search will surface that in week three with evidence attached, which is more useful than a shortlist of people who will not move.

How fast should our interview process be?

Two weeks from first candidate to decision. Beyond four weeks you are competing on patience rather than on the opportunity. 

Read next:The Initiate 7-Stage Mapped Search Methodology

Hiring for a senior SAP role? Book a client consultation.

The default assumption, and the right answer for many organisations. It is also the most demanding in hiring terms.

What it needs:

The timing problem. Between 20,000 and 25,000 legacy customers have still to move, in programmes running twelve to twenty-four months. Everyone choosing this path is competing for the same architects in the same window, and specialist SAP roles already take more than ninety days to fill against roughly forty-four for general IT.

The date is not the constraint. The number of people who have done an end-to-end conversion is the constraint.

For the hiring sequence, see Who do you actually need to hire for an S/4HANA conversion?

Staying on ECC through extended maintenance, or moving to third-party support.

Underrated, and made considerably more viable by the 2026 commitments. For organisations whose ECC estate is stable, whose competitive advantage does not sit in the ERP, or whose capital is committed elsewhere, this is a defensible commercial decision rather than a failure to act.

What it needs, and this is the part that gets missed:

Split support, partial migration, or migrating specific functions while the core stays put. The commitments explicitly permit split support, which makes this more workable than it was.

What it needs: both skill sets, which is the most demanding option of the three from a hiring perspective, and integration capability to hold the two estates together. 

Because a deadline is easier to sell than a decision.

The honest position is that the 2027 date is real, the extension options are also real, and which path suits depends on things a vendor timeline cannot know: your capital position, your competitive exposure, and whether your ERP is a differentiator or a utility.

What is not in doubt is the labour market underneath. In ASUG's 2026 Pulse survey of 663 members, 36% cite maintaining internal skills as a significant challenge and 22% struggle to retain knowledgeable staff through turnover. That applies whichever path you choose.

This is the practical consequence.

The S/4HANA market is tight and getting tighter, concentrated on conversion-proven architects, BTP and integration, and post go-live product and process ownership.

The ECC market has stayed valuable longer than most forecasts predicted, because the commitments made staying a legitimate strategy for a meaningful share of customers.

Both are thinning, and for the same reason. The generation that built these systems is retiring.

An organisation that decides to extend and assumes its hiring problem is deferred has misread the situation. It has chosen the market with fewer new entrants.

What exactly happens on 31 December 2027?

Mainstream maintenance for SAP ECC ends. Extended maintenance is available to 2030 at a premium. Systems do not stop working.

Do the European Commission commitments apply outside Europe?

They apply globally to on-premise customers, for ten years, and they removed the reinstatement fee, capped back-maintenance and permitted split support.

Is staying on ECC a reasonable strategy?

For some organisations, yes. It is a commercial decision rather than a technical one, and it carries a retention problem rather than a migration problem.

How early should we start hiring for a conversion?

Before the systems integrator is selected, if possible. The architect should be part of that decision rather than inherit it.

Read next:The Initiate 7-Stage Mapped Search Methodology

Planning your SAP hiring strategy? Book a client consultation.

Because "S/4HANA experience" covers at least four different things, and only one of them is what you need.

Greenfield implementation. A new build on a clean system. Different problem, different skills, and considerably more common.

Brownfield conversion. Taking a live ECC system to S/4HANA with its history, its custom code and its data. This is the scarce one.

Selective data transition. A hybrid, with its own set of decisions about what carries over.

Upgrade. Moving between S/4HANA releases. Useful experience, not the same experience.

On a resume these look identical. All four produce the phrase "full lifecycle S/4HANA implementation", which appears on thousands of profiles and means something different on almost every one.

The distinction only emerges in conversation. Which conversions, how many, what did you own end to end, and what went wrong.

Four, in rough order of how much damage their absence causes.

Solution or enterprise architect with a live conversion behind them. The scarcest profile in the market and the one that decides the shape of everything else. They hold design authority, they arbitrate between what the business wants and what the platform should do, and they carry the consequences of both.

Data lead. Migration, master data quality, and cutover readiness. More conversions go badly because of data than because of configuration. Someone has to own whether the data is actually ready, and that person cannot be the same one who is incentivised to hit the date.

Business process owners. Not project roles. These are the people who own the platform after go-live, and hiring them during the programme rather than after it is the difference between owning the system and renting it back.

Integration lead. BTP, Integration Suite, and everything touching the wider data estate. Underestimated on almost every programme, because the integration surface is always larger than the plan assumed.

Everything else is genuinely rentable.

Earlier than feels necessary, for one specific reason.

Specialist SAP roles routinely take more than ninety days to fill, against roughly forty-four days for general IT. An architect search started when the programme kicks off arrives in time for the second phase, not the first.

There is also a timing problem specific to this market. Between 20,000 and 25,000 legacy customers have still to move, and programmes run twelve to twenty-four months. Everyone who chooses to migrate is competing for the same architects in the same window.

Practical sequence:

The hiring does not stop. It changes shape.

43% of technology leaders are now optimizing existing S/4HANA environments, against 31% still transitioning. That second wave runs on different people: product owners, process owners, data governance, and the analytics and AI capability the platform was supposed to enable.

Programmes that treat go-live as the end of hiring typically discover within six months that the knowledge left with the systems integrator.

Can our systems integrator supply the architect?

They can supply an architect. Whether you want the design authority for your platform sitting inside the firm delivering it is a different question. When the programme closes, that person leaves with the reasoning behind every decision.

How do we test conversion experience in an interview?

Ask what went wrong. Anyone who has genuinely run a conversion carries a scar, and the answer tells you what they owned. Three flawless go-lives usually describes proximity rather than ownership.

Is it cheaper to use contractors for everything?

On the invoice, sometimes. Contract rates for scarce SAP skills run 30 to 50% above the FTE-equivalent hourly. The larger cost is that capability walks out at the end of the engagement.

How long does an architect search take?

Six weeks from first conversation to start date is achievable on a permanent search. The market average for a specialist SAP role is more than ninety days.

Read next:The Initiate 7-Stage Mapped Search Methodology

A staffing firm maintains a bench and a database. When a requirement arrives, it is matched against people who are already known, already looking, and already available.

The mechanics are volume-driven. The role is advertised. A keyword search runs against the database and the job boards. Resumes are screened for matching terms. A batch is submitted, usually quickly, often within days.

Several firms typically work the same requirement at once, on a contingent basis, and whoever submits an acceptable candidate first gets paid.

That model works well when three things are true: the skill is reasonably common, speed matters more than precision, and there are enough available people that a database match is likely to land.

For contract roles on a defined scope, it is frequently the right answer. Data migration support, testing surge, additional configuration capacity during a build phase. The requirement is clear, the work has an end date, and the candidate does not need to be persuaded to leave a career they are happy in.

A search firm starts from the opposite end. Not from who is available, but from who exists.

The market is mapped: the organizations running comparable SAP programs, the named individuals inside them, and who has worked alongside that profile before. Every relevant person is approached directly and confidentially, whether or not they are looking.

Assessment is a conversation rather than a keyword match. What the person actually owned on a program, not what their resume lists. Their motivation, their circumstances, their compensation in full, what else is live in their process, and how exposed they are to a counteroffer.

Fewer candidates are presented. Three to five is normal. Each one has been spoken to properly, and the reservations are stated openly alongside the strengths.

That model is necessary when the person you need is not looking. Which, for senior SAP roles, is almost always.

Three reasons, and all of them are specific to this market.

Specialist SAP roles take more than twice as long to fill. The market average is over ninety days, against roughly forty-four days for general IT. That gap is not inefficiency. It is supply.

The scarcity is specific, not general. There are plenty of people whose resume says SAP. There are very few who have delivered a live ECC-to-S/4HANA conversion end to end. On paper those two groups look identical. The difference only emerges in conversation, which a keyword match cannot have.

SAP terminology defeats keyword search. Finance appears as FI, CO, FICO, Finance, Central Finance and Treasury, depending on who wrote the profile and when. HR appears as HCM, HXM, SuccessFactors and Human Capital. The word SuccessFactors also turns up in profiles describing the success factors of someone's career, which has nothing to do with the platform.

The result is noise in both directions. Relevant people are missed because they described the same work in different language. Irrelevant people fill the results because a term matched by accident.

That is why a database-first approach underperforms here in a way it does not in, say, Java development. The database is only as good as the language the candidate happened to use.

Four questions. The answers tell you which model you are actually buying, regardless of what the firm calls itself.

Who did you approach, and what came back? A search firm can name the organizations it mapped, who was contacted, who engaged and who declined with the reason given. A staffing firm can tell you who responded.

How many candidates will I see? Three to five assessed is a search. Fifteen screened is staffing.

What did this person actually own? Ask about a submitted candidate. If the answer repeats the resume, nobody has had the conversation.

What are the risks with this candidate? A proper assessment surfaces the hesitations, the competing processes and the counteroffer exposure up front. Enthusiasm with no reservations attached usually means nobody asked.

Staffing answers "who is available?" Search answers "who could do this?"

For contract capacity on defined work, availability is the right question and staffing is the efficient answer.

For anything that holds decision rights or has to survive go-live, availability is the wrong question entirely. The people who could do it are employed, and the only way to reach them is to go and find them.

Is SAP search more expensive than SAP staffing?

Per hire, usually. Against a role sitting open for six months, rarely. The cost of an empty seat on a live programme, of a contractor covering it, or of a hire who cannot hold design authority, generally exceeds the difference.

Can one firm do both?

Yes, and many claim to. What matters is which process they are actually running on your requirement. The four questions above establish it in about ten minutes.

Does contract work always mean staffing?

No. Senior interim roles, particularly programme leadership and architecture cover, are scarce enough to need a mapped approach even on a contract basis.

How long should a senior SAP search take?

Six weeks from first conversation to start date is achievable on a permanent search: two weeks to present assessed candidates, two weeks for your interview process, two weeks notice. The market average for a specialist SAP role is more than ninety days, and the variable that usually decides it is the speed of the client's own process.