Migrate from SAP SuccessFactors to Recruit CRM & ATS

SAP SuccessFactors Candidate (PerPerson and associated PerPersonal HRIS elements) maps to Recruit CRM Candidate records via the Candidate API endpoint. Standard fields (name, email, phone, address) migrate directly. Custom candidate fields stored as MDF picklist or string values migrate to Recruit CRM custom candidate fields, which we create during schema discovery. We resolve the candidate's status (active application vs passive profile) from SuccessFactors application associations. SAP compound employee email (emailPersonal/emailWork) maps to Recruit CRM's email_work and email_home fields with primary email flagged by SAP preferred_email_type.

SAP SuccessFactors Job Requisition (RCM Requisition entity) maps to Recruit CRM Job records via the Jobs API. Fields including title, description, department, location, employment type, and salary range migrate directly. SAP's position-to-requisition associations (documented in SAP KB 2925869, where position fields require FORMAT function mapping) are stored as custom job fields in Recruit CRM because Recruit CRM does not maintain a Position Management hierarchy. Requisition status (draft, open, filled, cancelled) maps to Recruit CRM job status with a direct value translation table.

SAP SuccessFactors Application records (linking Candidate to Job Requisition with stage and timestamp) map to Recruit CRM Candidate Job Applied records. The application stage (applied, screening, interview, offer, hired, rejected) maps to Recruit CRM's candidate_job_status values. Application submission date and last-modified date migrate as created_at and updated_at timestamps. Historical stage transitions migrate as candidate_job_stage records if Recruit CRM's data model supports stage history, or as a JSON blob in a custom notes field for admin review.

SAP SuccessFactors Foundation Objects (Division, Department, Business Unit, Location) map to Recruit CRM's organizational hierarchy. Multi-level SAP hierarchies collapse into Recruit CRM's flat organization structure with department as a primary tag. Cost center codes from SAP migrate as a custom field on the Department record. If SAP uses Position Management for org structure, we extract the reports-to chain and map it to Recruit CRM's user hierarchy for recruiter assignment.

SAP JobCode and JobProfileLoc MDF objects contain job classification data that has no direct Recruit CRM equivalent. We extract job family, job level, and competency associations as Recruit CRM Skills attached to Job records. Competency names from the SAP Talent Intelligence Hub migrate as Skills with the original SAP competency ID stored in a custom field for reference. Skills without a Recruit CRM equivalent are created during migration and flagged for the customer's admin to assign icons and categories.

SAP SuccessFactors Recruiting email threads, notes, and tasks attached to candidates or applications map to Recruit CRM Candidate Activities. Email body content migrates as activity records of type email; manual tasks migrate as activity records of type task. Attachments (offer letters, resume files) export via SAP Integration Center attachment outbound integrations and are uploaded to Recruit CRM via the Candidate document endpoint or as base64-encoded file attachments on the candidate record. SAP's SFTP file delivery method requires us to download files before upload, adding a step to the pipeline.

SAP SuccessFactors Interview schedules and feedback forms migrate to Recruit CRM interview records and candidate notes. Interview scorecards stored as SAP MDF forms with rating scales require transformation to Recruit CRM's interview rating structure, which may involve collapsing multi-dimension scorecards into a single overall rating or distributing them across multiple custom fields if Recruit CRM's schema supports it. We flag incomplete mappings during schema discovery and deliver a written field-level recommendation.

SAP SuccessFactors Talent Pools (managed via Recruiting Marketing or Talent Intelligence Hub) map to Recruit CRM Candidate Lists. We extract the talent pool membership records, including creation date and membership source (sourced, referred, applied), and create corresponding Candidate List entries in Recruit CRM. Duplicate candidate detection runs against the merged candidate database to prevent list inflation from candidates already in the system.

SAP SuccessFactors offer records (offer amount, start date, benefits package, approval status) map to Recruit CRM's candidate_job status with offer extended or offer accepted values. Offer details that exceed Recruit CRM's standard fields migrate as JSON in a custom notes field. Offer approval workflow history from SAP does not migrate as a functional workflow in Recruit CRM; we document the approval chain in a written handoff for the customer's admin to configure in Recruit CRM's workflow builder.

SAP SuccessFactors custom MDF objects created in the RCM context (documented in SAP KB 3276791 for RCM-to-MDF field mapping) require a schema discovery step against Recruit CRM's candidate and job custom field metadata before migration. We inspect the MDF object field types (picklist, string, date, user, fo-entity) and map them to the closest Recruit CRM field type, flagging any unsupported type (such as SAP Foundation Object entity references) for manual resolution. SAP picklist option IDs migrate as string values with a lookup table delivered alongside the migration output.

SAP SuccessFactors Employee Central records created from a hired candidate (PerPerson with hire date set) migrate to Recruit CRM as Candidate records with a custom hired flag set to true. We do not migrate the full Employee Central HRIS data model (compensation, benefits, time off) as that falls outside Recruit CRM's scope as a recruitment platform. The candidate's hire date, start date, and initial job title from SAP EC migrate as fields on the Recruit CRM candidate record for reporting purposes.