SAP acquired SmartRecruiters in September 2025. For SmartRecruiters customers, the immediate operational impact is limited — contracts remain in place, the platform continues to function, and the product team has communicated continuity messaging. The longer-term concern is more structural: SAP acquisitions of standalone HR software products have a pattern. The platform gets absorbed into the SAP SuccessFactors ecosystem, pricing moves upmarket, and features that were the reason mid-market companies chose SmartRecruiters — agility, relatively clean interface, reasonable implementation complexity — gradually give way to the complexity priorities of enterprise SAP customers.

Whether that pattern plays out the same way here remains to be seen. What is clear is that planning a migration now, while you have full control over the timeline and can run a careful evaluation, is the right approach — regardless of whether you ultimately decide to stay. The knowledge you gain by understanding exactly what you have in SmartRecruiters and what your migration options look like is valuable even if you don't use it immediately.

What's almost certainly true: the SmartRecruiters you renew with in 2027 will not be the same product you originally selected. The question is whether the changes will be improvements relevant to your company, or enterprise-focused additions that increase your cost without serving your hiring workflow. Planning the migration evaluation now gives you the leverage to make that determination on your own terms, not SAP's.

What data you can export from SmartRecruiters

Before you can plan a migration, you need to understand exactly what data is in your SmartRecruiters account and what format it can be exported in. SmartRecruiters' data portability capabilities are reasonable for candidate profile data but less complete for workflow configuration data.

Data that migrates cleanly

  • Candidate profiles. Name, contact details, CV/resume files, application history, custom application form responses. This is the core candidate data and it exports in standard formats.
  • Job history. Job titles, descriptions, hiring team assignments, open/close dates, job status history.
  • Pipeline stages. The stage names and structures of your hiring pipelines are exportable as data, though rebuilding them as functional workflows in a new system requires configuration work.
  • Notes and activities. Interview notes, candidate activity logs, and communication history associated with candidate records can typically be exported, though formatting may not be preserved exactly.
  • Offer data. Offer details associated with accepted and rejected offers in your history.

Data and configuration that doesn't migrate cleanly

  • Custom workflow automation. SmartRecruiters' workflow automation (automated stage transitions, triggered communications, approval routing) is platform-specific logic. It exports as documentation at best — you rebuild it in the new system, you don't import it.
  • Interview scorecards. Structured interview kits and scorecard templates are SmartRecruiters-specific configurations. Export what you can as documentation, but plan to rebuild these from scratch.
  • Integration data. Data held in third-party tools connected to SmartRecruiters (background check providers, video interview platforms, assessment tools) is held by those tools, not SmartRecruiters. Each integration needs to be re-established with your new ATS.
  • Historical analytics. Pipeline velocity data, source tracking, time-to-hire trends, and similar reporting data is in SmartRecruiters' analytics layer. Export summary reports before migration rather than expecting this data to transfer.

Week-by-week migration checklist

This timeline assumes a company with moderate SmartRecruiters configuration complexity — established workflows, 3–5 active integrations, 10–20 active users. Adjust the timeline based on your actual complexity.

Weeks 1–2: Discovery and vendor selection

  • Request a full data export from SmartRecruiters support. Review completeness before proceeding.
  • Document your current pipeline stages, automation rules, and integration list.
  • Export summary reports for your key metrics: time-to-hire, source tracking, pipeline conversion rates. These become your baseline for comparison after migration.
  • Evaluate 2–3 alternative ATS platforms against your documented requirements.
  • Select new ATS and sign contract. Confirm their data import capability matches your export format.
  • Map out your migration team: who owns data import, who owns workflow configuration, who will train users.

Weeks 3–4: New system configuration

  • Configure career page branding in the new system.
  • Build pipeline stages that mirror your current SmartRecruiters configuration.
  • Rebuild job posting templates and application form configurations.
  • Set up user accounts and permission groups.
  • Begin rebuilding automation rules and workflow triggers from your documentation.
  • Start integration re-mapping: identify the native integration options in the new system for each integration you currently use in SmartRecruiters.

Weeks 5–6: Data import and testing

  • Import candidate data from SmartRecruiters export. Verify completeness and formatting.
  • Test the import with a sample dataset (50–100 records) before running the full import.
  • Run a complete test job through the entire workflow: post the job, apply as a test candidate, move through pipeline stages, complete interview scheduling, generate an offer.
  • Identify gaps between expected behaviour and actual behaviour in the new system. Fix configuration issues.
  • Brief 2–3 pilot users (ideally experienced recruiters) to use the new system for one active role. Collect their feedback.

Week 7: Training and go-live preparation

  • Run training sessions for all recruiter users. Focus on the workflows they use most frequently.
  • Prepare hiring manager onboarding — simplified, role-specific guidance rather than full platform training.
  • Establish a support channel for go-live week (dedicated Slack channel or email address for immediate questions).
  • Communicate the go-live date and basic change summary to all hiring managers.
  • Complete final data import from SmartRecruiters for active candidate records.

Week 8: Parallel running and cutover

  • Go live on new system. All new job postings go into the new system only.
  • Active pipeline candidates: decide whether to complete existing pipelines in SmartRecruiters or move active candidates to the new system. For candidates late in the process (offer stage), complete in SmartRecruiters. For early-stage candidates, moving them is manageable.
  • Keep SmartRecruiters in read-only mode for reference during the parallel period.
  • After 2 weeks, assess whether active pipelines from SmartRecruiters are complete or can be closed. Once all active pipelines are resolved, SmartRecruiters can be fully decommissioned.
  • Before closing your SmartRecruiters account, confirm your data export is complete and stored securely for any future GDPR or data subject access requests.

What the SAP acquisition means for your roadmap

SAP's acquisition of SmartRecruiters follows a well-documented pattern in enterprise HR software. When enterprise software conglomerates acquire standalone products, the transition typically unfolds over 2–3 years. In the first year, customer communications emphasise continuity and independence. Product development continues on the standalone roadmap, and contractual terms remain unchanged.

In years two and three, the integration begins. Product roadmap priorities align with the parent company's ecosystem needs. Features that benefit SAP SuccessFactors customers rise in priority; features primarily relevant to standalone mid-market customers may deprioritise. Pricing conversations start referencing the broader SAP relationship. Implementation partners familiar with the original product may shift to SAP-focused practices.

For current SmartRecruiters customers, the relevant questions to ask your account team now are:

  • What is the product roadmap for the next 18 months, and which items on that roadmap are specific to SmartRecruiters versus SAP ecosystem integration?
  • Will SmartRecruiters be available as a standalone product, or will it eventually require an SAP SuccessFactors relationship?
  • How will renewal pricing be structured — through SmartRecruiters' current pricing model or through SAP's enterprise pricing structure?
  • What happens to SmartRecruiters' non-SAP integrations (with HRIS vendors like BambooHR, Rippling, and Personio) as the SAP integration becomes the primary supported path?

The answers you get will tell you a lot. A vendor relationship with honest answers to these questions — even difficult ones — is the kind of relationship worth maintaining. Vague or deflecting answers are themselves a signal about the direction of travel.

If you're on a multi-year contract with SmartRecruiters that extends into 2027 or 2028, the practical risk is lower in the near term — your terms are locked, and the product will continue to function. If your contract renews in the next 12 months, the renewal negotiation is a meaningful inflection point: you're either committing to the SAP-era SmartRecruiters or planning a migration.

What to look for in a SmartRecruiters replacement

SmartRecruiters positioned itself as a collaborative hiring platform. The features its users rely on most are the hiring team collaboration tools: shared candidate notes visible to all hiring team members, structured interview scheduling with interviewer-facing guidance, and offer approval workflows that route through managers without requiring email chains.

When evaluating replacements, test these specific capabilities explicitly — don't assume they're present because the vendor has them on the features list. Run through the workflow: create a job, build the interview process, schedule interviews for multiple interviewers, have a simulated candidate go through the workflow, generate an offer, route it for approval. The gaps in a platform show up in the workflow testing, not the feature comparison spreadsheet.

Beyond capability matching, the pricing model matters. SmartRecruiters has moved toward per-seat and per-job pricing in ways that make growth costly. Alternatives with flat monthly pricing give you cost predictability as hiring volume grows. Verify how each vendor prices before starting a trial — discovering mid-evaluation that the platform costs three times more at your current team size than the entry price point is a waste of evaluation time.

Treegarden's pricing starts at $299/month and includes all features without per-seat or per-job increments. For teams that have been managing SmartRecruiters cost increases, the contrast is immediate: all features accessible from day one, no overage charges when you have a hiring surge, no enterprise tier required for approval workflows or structured interview capability.

Communicating the change to hiring managers

Hiring manager resistance is a genuine migration risk. Hiring managers who have invested time learning SmartRecruiters — and who are in the middle of active searches — will be frustrated by a system change unless the communication is handled carefully.

The most effective approach is framing that acknowledges the disruption honestly. "We know this is a change, and change in the middle of hiring is inconvenient. Here's specifically what's getting better: [concrete improvements relevant to hiring managers]. Here's what will feel different for the first two weeks: [honest description of the adjustment period]. Here's how we're supporting you through it: [training, support channel, named contact]."

Hiring managers who feel the change was explained to them rather than imposed on them adopt new systems significantly faster. The fastest way to create lasting resistance is to announce the change without acknowledgment of the friction it creates.

We make the switch straightforward

Treegarden's team helps with data migration from any ATS. Transparent pricing from $299/mo. No surprise costs mid-migration.

See pricing and migration support →

How to negotiate your SmartRecruiters exit

Your SmartRecruiters contract has specific terms around notice periods, data retention after cancellation, and what access you retain after cancellation is processed. Before initiating the cancellation conversation:

Review your contract for notice period requirements. Most ATS contracts require 30–90 days notice before contract end for cancellation. Missing this window means you're automatically renewed for another term.

Confirm the data access window after cancellation. You typically have a defined period (30–90 days) of read-only access to your SmartRecruiters account after the contract end date. Plan your data export to complete well before this window closes, not at the last minute.

Request a shorter renewal term if you're not ready to migrate immediately. If your contract is coming up for renewal and you want more time, requesting a 3–6 month extension rather than a full annual renewal gives you flexibility without committing to another year.

Use competitive evaluation as negotiating leverage. If you have a documented alternative offer at a lower price, your SmartRecruiters account manager has more room to move on renewal pricing than their initial quote suggests. Use this leverage before you sign a renewal, not after.

Frequently asked questions

Can I export all my candidate data from SmartRecruiters?

Core candidate profile data (names, contact details, application history, CV files) exports reasonably well. Workflow configuration, automation rules, interview scorecard templates, and historical analytics data do not migrate cleanly — these need to be rebuilt or accepted as lost in the migration. Request a full export early and review completeness before committing to a migration timeline.

How long does an ATS migration take?

A well-planned migration typically takes 4–8 weeks from decision to go-live. The range depends on your configuration complexity: simpler setups with few integrations can go live in 3–4 weeks. Complex setups with many integrations, custom workflows, and large user groups should plan for 8–10 weeks. Compressing the timeline is possible but increases the risk of go-live problems.

Should I migrate before or after contract renewal?

Before, ideally. You have maximum leverage with SmartRecruiters before renewal — either to negotiate better terms or to exit cleanly at contract end. After renewal you've committed to another year. The exception is if you're in a high-volume hiring period; in that case, negotiate a shorter renewal term (3–6 months) while you complete the migration.

What SmartRecruiters data is hard to migrate?

Custom automation workflows, interview scorecard templates, offer letter merge field logic, and historical analytics data are the categories that don't migrate cleanly. Plan to rebuild automation and templates from scratch. Export summary analytics reports before migration to preserve metric baselines. Integration history and data held in connected tools is held by those tools, not SmartRecruiters.

Is now a good time to move away from SmartRecruiters, or should I wait to see how the SAP integration develops?

If your contract renews within the next 12 months, now is the right time to run the evaluation — regardless of whether you ultimately decide to migrate. Running a proper competitive evaluation before renewal gives you genuine pricing leverage with SmartRecruiters and a clear migration option if the renewal terms are unacceptable. Waiting passively means defaulting to renewal without leverage. If your contract has 18+ months remaining, monitoring the SAP integration developments over the next 6 months before committing to a migration project is reasonable.

Related Reading