If you run SAP SuccessFactors Recruiting, you are the rare buyer whose vendor has already named your replacement. On March 3, 2026 SAP released SmartRecruiters for SAP SuccessFactors as the go-to-market talent acquisition product inside the HCM suite, and moved the existing Recruiting module into what it calls a Core Stability Phase. That is a roadmap decision, not an eviction notice — and the difference is the whole page.
What Core Stability Phase actually obligates you to
Nothing, on a deadline. SAP has published no end-of-life date for SuccessFactors Recruiting, and specialist SAP partners advising on the transition say the same thing in August 2026. SuccessFactors president Daniel Beck told CIO in October 2025 that customers get three to five years to complete the migration, and SAP said it would signal migration availability by the end of Q1 2026. Nobody is turning your requisitions off.
The forcing function is starvation, not a cliff. Core Stability Phase means maintenance without roadmap, and the 1H 2026 release shows what that produces: OnChange business rules that fire on a candidate status change, automatic requisition closure at Hired, styling options in Career Site Builder — plus an embed of SmartRecruiters’ Winston chat on the SuccessFactors career site. The successor is being shipped inside the incumbent.
Every recruiting capability SAP has announced since it closed the $1.8B SmartRecruiters acquisition on September 11, 2025 has landed on the other side. Winston Match, in the June 2026 release, now scores candidates on profile data they confirmed or entered themselves and falls back to resume parsing only when that data is missing. That capability is not coming to your module. So the cost of staying is not a shutdown; it is running hiring on a system that gets bug fixes while the recruiters you compete with get agents.
SmartRecruiters — the path SAP is funding
The SmartRecruiters integration is productized in three phases, and SAP has published what each one carries. Phase 1 (H1 2026) delivers single sign-on through IAS, a recruiter UI that spans both systems, and automatic flow of foundational organizational data from SuccessFactors into SmartRecruiters. Phase 2 (also H1 2026) automates candidate-to-hire conversion into Employee Central and Onboarding, adds an SAP SuccessFactors Story Reports integration, and — the part that governs your sequencing — supports running both systems side by side. Phase 3 (H2 2026 and beyond) connects Winston Chat to Joule and opens BTP extensibility.
The migration tooling is real and it moved in June 2026. Migration Hub now runs the migration rather than handing you a readiness report: once you review and finalize field mappings, it migrates job fields and application fields with their configurations into SmartRecruiters, analyzes Application, Candidate profile and Offer configurations for data-type mismatches and picklist changes, and pushes eligible single-select field definitions directly into Integration Sync. The same release added a SuccessFactors Connectivity Hub in SmartRecruiters Settings for master-data sync and Position-to-Job mapping.
Price: Vendr’s 2026 transaction data puts median SmartRecruiters spend at $33,507 a year, with most deals between $15,250 and $51,561. Mid-market buyers land at $5,000-$10,000 per recruiter seat per year. Professional services for configuration, integrations and data migration are quoted separately — $10,000-$50,000 for mid-market, past $100,000 for global enterprise.
Move here when: you run Employee Central, your Recruiting configuration is close to standard, and recruiter experience is the loudest complaint in your TA org. This is the default, and it should be.
Don’t, when: your reason for leaving is SAP. Migrating to the SAP-owned successor answers a UX complaint, not a vendor-strategy one.
Workday
The alternative that only makes sense if the HR system of record is also in play. Workday Recruiting rides the same worker record, position budget and org chart that Employee Central holds for you today, and adds two agents SAP has no equivalent for: the HiredScore-powered Recruiting Agent for sourcing and screening, and the Paradox-powered Candidate Experience Agent for conversational apply and self-scheduling, both registered in Workday’s Agent System of Record.
Vendr’s 2026 data puts median Workday spend at $50,865 a year across 367 purchases, ranging from $19,522 to $549,949 — that figure covers the platform, not the Recruiting module alone, which is priced as an add-on per employee, per user, or in some packagings per requisition or per hire.
Move here when: you are already running an SAP-to-Workday HCM evaluation for reasons that have nothing to do with recruiting. Bolting Workday Recruiting onto a SuccessFactors core is the worst of both — you pay enterprise-suite prices for a standalone ATS and rebuild the hire handoff by hand.
Greenhouse
The pick when the problem is hiring quality, not HR-record adjacency. Greenhouse built the structured-hiring convention — scorecards, interview kits, source-of-hire reporting — and 450+ certified integrations mean every sourcing, assessment and background-check vendor builds against it first. Its ladder is Core, Plus and Pro.
Vendr’s 2026 data puts median Greenhouse spend at $26,611 a year across 868 purchases, from $10,222 to $75,001 — about 21% under the SmartRecruiters median at the middle of each distribution, though per-seat it runs higher at $6,000-$12,000 for mid-market buyers, and implementation is quoted at $15,000-$150,000+. Greenhouse is cheaper on the median deal and more expensive per recruiter; which one you feel depends on whether your spend is driven by seats or by scope.
Move here when: your hiring managers submit unstructured feedback, your interview loops differ by team, and you cannot answer “which source produced our best hires” from the ATS. Greenhouse fixes that and SmartRecruiters does not.
Don’t, when: you hire at high volume in frontline or multi-country operations. Greenhouse is built for considered white-collar hiring and thins out fast outside it.
iCIMS
The way to replace the ATS without touching the HR system of record. iCIMS maintains a SuccessFactors integration, so it is the only option here that lets you keep Employee Central as the worker record while swapping recruiting for a platform built for multi-business-unit, multi-country hiring with OFCCP-aligned reporting. Vendr’s dataset shows an average iCIMS contract of $20,781 a year against an observed range of $14,500 to $635,000 — the widest spread of the four, because iCIMS sells Recruit, Attract, Engage, Video Studio and Onboard as separate modules.
Move here when: you are a regulated or multi-brand enterprise, your SuccessFactors HCM investment is staying, and your objection to SmartRecruiters is concentration risk rather than product fit. See iCIMS vs Greenhouse for the enterprise-versus-structured-hiring axis.
The migration cost most teams underestimate
Three costs bite in the same order every time.
Your history does not come with you. Candidate, job and application records stay in SuccessFactors for reporting and audit while new recruiting activity runs in the new platform. You either keep paying for a system nobody recruits in, or you fund an export and a reporting rebuild. Decide which before you sign, not in month four.
The career site fragments during a phased rollout. Two recruiting platforms can coexist — Phase 2 explicitly supports it — but candidates see the seam unless site architecture, navigation, branding and job distribution are planned as one thing. Guard: assign career-site ownership to a named person on day one of the program, not to whichever workstream finishes first.
Services outrun licences. SmartRecruiters quotes configuration, integration and migration separately at $10,000-$100,000+; Greenhouse at $15,000-$150,000+; Workday implementations run one to two times the annual subscription. Budget the services line before you negotiate the licence, because it is the line that gets discounted last.
Pick a transition shape deliberately. A big bang is fastest and riskiest. A phased rollout by country, region or business unit is the practical route for most global teams and is what Phase 2’s side-by-side support exists to enable. A targeted transition — new requisitions only, or one hiring population — is the lowest-risk entry and the right choice if your configuration is heavily customized.
When staying is right
Do not move yet if all three hold: your recruiters are not complaining, your SuccessFactors Recruiting configuration carries heavy custom business rules and integrations, and your renewal is more than two years out. Core Stability Phase is a real product state, not a countdown, and burning a transformation budget in 2026 to escape a system with no announced sunset is a spend without a trigger. Guard: set a hard re-evaluation date at your next renewal, and a second trigger the moment SAP publishes an end-of-life date. Waiting is a decision that needs a review calendar; drift is not the same thing.
Verdict
If you run Employee Central and cannot decide between the conditions above, default to SmartRecruiters. You are paying a migration cost either way, and this is the only destination where SAP funds the tooling, ships the Employee Central hire handoff as a product, and supports a side-by-side cutover. Moving that same data to a third party means paying the same bill and building the handoff yourself.
Two named exceptions. Pick Greenhouse when the defect is interview quality and source attribution rather than recruiter UX. Pick iCIMS when you need the ATS replaced but the SAP HR core kept, and concentration risk is a stated procurement objection.
Workday is not an ATS decision at all — it is an HCM decision that drags recruiting along, and it is the wrong answer unless that larger evaluation is already open.
And the counter-case worth stating plainly: a forced platform change is the cheapest exit you will ever get from a vendor, because the migration budget is already approved. If your complaint about SuccessFactors Recruiting was really a complaint about SAP, the next three years are the window — after that you will be re-migrating off SmartRecruiters and paying for it twice. Start from the recruiting stack you actually need, not from the successor your vendor picked.
If you run SAP SuccessFactors Recruiting, you are the rare buyer whose vendor has already named your replacement. On March 3, 2026 SAP released SmartRecruiters for SAP SuccessFactors as the go-to-market talent acquisition product inside the HCM suite, and moved the existing Recruiting module into what it calls a Core Stability Phase. That is a roadmap decision, not an eviction notice — and the difference is the whole page.
What Core Stability Phase actually obligates you to
Nothing, on a deadline. SAP has published no end-of-life date for SuccessFactors Recruiting, and specialist SAP partners advising on the transition say the same thing in August 2026. SuccessFactors president Daniel Beck told CIO in October 2025 that customers get three to five years to complete the migration, and SAP said it would signal migration availability by the end of Q1 2026. Nobody is turning your requisitions off.
The forcing function is starvation, not a cliff. Core Stability Phase means maintenance without roadmap, and the 1H 2026 release shows what that produces: OnChange business rules that fire on a candidate status change, automatic requisition closure at Hired, styling options in Career Site Builder — plus an embed of SmartRecruiters’ Winston chat on the SuccessFactors career site. The successor is being shipped inside the incumbent.
Every recruiting capability SAP has announced since it closed the $1.8B SmartRecruiters acquisition on September 11, 2025 has landed on the other side. Winston Match, in the June 2026 release, now scores candidates on profile data they confirmed or entered themselves and falls back to resume parsing only when that data is missing. That capability is not coming to your module. So the cost of staying is not a shutdown; it is running hiring on a system that gets bug fixes while the recruiters you compete with get agents.
SmartRecruiters — the path SAP is funding
The SmartRecruiters integration is productized in three phases, and SAP has published what each one carries. Phase 1 (H1 2026) delivers single sign-on through IAS, a recruiter UI that spans both systems, and automatic flow of foundational organizational data from SuccessFactors into SmartRecruiters. Phase 2 (also H1 2026) automates candidate-to-hire conversion into Employee Central and Onboarding, adds an SAP SuccessFactors Story Reports integration, and — the part that governs your sequencing — supports running both systems side by side. Phase 3 (H2 2026 and beyond) connects Winston Chat to Joule and opens BTP extensibility.
The migration tooling is real and it moved in June 2026. Migration Hub now runs the migration rather than handing you a readiness report: once you review and finalize field mappings, it migrates job fields and application fields with their configurations into SmartRecruiters, analyzes Application, Candidate profile and Offer configurations for data-type mismatches and picklist changes, and pushes eligible single-select field definitions directly into Integration Sync. The same release added a SuccessFactors Connectivity Hub in SmartRecruiters Settings for master-data sync and Position-to-Job mapping.
Price: Vendr’s 2026 transaction data puts median SmartRecruiters spend at $33,507 a year, with most deals between $15,250 and $51,561. Mid-market buyers land at $5,000-$10,000 per recruiter seat per year. Professional services for configuration, integrations and data migration are quoted separately — $10,000-$50,000 for mid-market, past $100,000 for global enterprise.
Move here when: you run Employee Central, your Recruiting configuration is close to standard, and recruiter experience is the loudest complaint in your TA org. This is the default, and it should be.
Don’t, when: your reason for leaving is SAP. Migrating to the SAP-owned successor answers a UX complaint, not a vendor-strategy one.
Workday
The alternative that only makes sense if the HR system of record is also in play. Workday Recruiting rides the same worker record, position budget and org chart that Employee Central holds for you today, and adds two agents SAP has no equivalent for: the HiredScore-powered Recruiting Agent for sourcing and screening, and the Paradox-powered Candidate Experience Agent for conversational apply and self-scheduling, both registered in Workday’s Agent System of Record.
Vendr’s 2026 data puts median Workday spend at $50,865 a year across 367 purchases, ranging from $19,522 to $549,949 — that figure covers the platform, not the Recruiting module alone, which is priced as an add-on per employee, per user, or in some packagings per requisition or per hire.
Move here when: you are already running an SAP-to-Workday HCM evaluation for reasons that have nothing to do with recruiting. Bolting Workday Recruiting onto a SuccessFactors core is the worst of both — you pay enterprise-suite prices for a standalone ATS and rebuild the hire handoff by hand.
Greenhouse
The pick when the problem is hiring quality, not HR-record adjacency. Greenhouse built the structured-hiring convention — scorecards, interview kits, source-of-hire reporting — and 450+ certified integrations mean every sourcing, assessment and background-check vendor builds against it first. Its ladder is Core, Plus and Pro.
Vendr’s 2026 data puts median Greenhouse spend at $26,611 a year across 868 purchases, from $10,222 to $75,001 — about 21% under the SmartRecruiters median at the middle of each distribution, though per-seat it runs higher at $6,000-$12,000 for mid-market buyers, and implementation is quoted at $15,000-$150,000+. Greenhouse is cheaper on the median deal and more expensive per recruiter; which one you feel depends on whether your spend is driven by seats or by scope.
Move here when: your hiring managers submit unstructured feedback, your interview loops differ by team, and you cannot answer “which source produced our best hires” from the ATS. Greenhouse fixes that and SmartRecruiters does not.
Don’t, when: you hire at high volume in frontline or multi-country operations. Greenhouse is built for considered white-collar hiring and thins out fast outside it.
iCIMS
The way to replace the ATS without touching the HR system of record. iCIMS maintains a SuccessFactors integration, so it is the only option here that lets you keep Employee Central as the worker record while swapping recruiting for a platform built for multi-business-unit, multi-country hiring with OFCCP-aligned reporting. Vendr’s dataset shows an average iCIMS contract of $20,781 a year against an observed range of $14,500 to $635,000 — the widest spread of the four, because iCIMS sells Recruit, Attract, Engage, Video Studio and Onboard as separate modules.
Move here when: you are a regulated or multi-brand enterprise, your SuccessFactors HCM investment is staying, and your objection to SmartRecruiters is concentration risk rather than product fit. See iCIMS vs Greenhouse for the enterprise-versus-structured-hiring axis.
The migration cost most teams underestimate
Three costs bite in the same order every time.
Your history does not come with you. Candidate, job and application records stay in SuccessFactors for reporting and audit while new recruiting activity runs in the new platform. You either keep paying for a system nobody recruits in, or you fund an export and a reporting rebuild. Decide which before you sign, not in month four.
The career site fragments during a phased rollout. Two recruiting platforms can coexist — Phase 2 explicitly supports it — but candidates see the seam unless site architecture, navigation, branding and job distribution are planned as one thing. Guard: assign career-site ownership to a named person on day one of the program, not to whichever workstream finishes first.
Services outrun licences. SmartRecruiters quotes configuration, integration and migration separately at $10,000-$100,000+; Greenhouse at $15,000-$150,000+; Workday implementations run one to two times the annual subscription. Budget the services line before you negotiate the licence, because it is the line that gets discounted last.
Pick a transition shape deliberately. A big bang is fastest and riskiest. A phased rollout by country, region or business unit is the practical route for most global teams and is what Phase 2’s side-by-side support exists to enable. A targeted transition — new requisitions only, or one hiring population — is the lowest-risk entry and the right choice if your configuration is heavily customized.
When staying is right
Do not move yet if all three hold: your recruiters are not complaining, your SuccessFactors Recruiting configuration carries heavy custom business rules and integrations, and your renewal is more than two years out. Core Stability Phase is a real product state, not a countdown, and burning a transformation budget in 2026 to escape a system with no announced sunset is a spend without a trigger. Guard: set a hard re-evaluation date at your next renewal, and a second trigger the moment SAP publishes an end-of-life date. Waiting is a decision that needs a review calendar; drift is not the same thing.
Verdict
If you run Employee Central and cannot decide between the conditions above, default to SmartRecruiters. You are paying a migration cost either way, and this is the only destination where SAP funds the tooling, ships the Employee Central hire handoff as a product, and supports a side-by-side cutover. Moving that same data to a third party means paying the same bill and building the handoff yourself.
Two named exceptions. Pick Greenhouse when the defect is interview quality and source attribution rather than recruiter UX. Pick iCIMS when you need the ATS replaced but the SAP HR core kept, and concentration risk is a stated procurement objection.
Workday is not an ATS decision at all — it is an HCM decision that drags recruiting along, and it is the wrong answer unless that larger evaluation is already open.
And the counter-case worth stating plainly: a forced platform change is the cheapest exit you will ever get from a vendor, because the migration budget is already approved. If your complaint about SuccessFactors Recruiting was really a complaint about SAP, the next three years are the window — after that you will be re-migrating off SmartRecruiters and paying for it twice. Start from the recruiting stack you actually need, not from the successor your vendor picked.