Migrate from SAP SuccessFactors to Bullhorn ATS & CRM

SAP SuccessFactors PerPerson records (the core HRIS element) map to Bullhorn Candidate records. We extract name, email, phone, address, and nationality from PerPersonal and map them to Bullhorn's Candidate firstName, lastName, email, phone, and address fields. The SuccessFactors personIdExternal becomes a custom Bullhorn field ssf_person_id__c for dedupe and reconciliation. Active job-seekers (identified by a targetJobApplication status in the recruiting module) are prioritized as Candidate records; we preserve employment status and current title in Bullhorn custom fields rather than native fields since Bullhorn's Candidate model is ATS-centric.

SuccessFactors employees who will not be active candidates in the Bullhorn ATS (past employees, passive talent in the pipeline, or contractor records) migrate as Bullhorn Contact records. We map the same PerPersonal fields to Bullhorn Contact, with ssf_person_id__c carrying the original identifier. Contact records do not enter the ATS pipeline but are available for CRM workflows and candidate pools.

SuccessFactors PerEmployment records carry job title, manager relationship, employment type (full-time, part-time, contractor), start date, and probation end date. We map these to Bullhorn Placement records attached to the Candidate, with employment type mapped to Bullhorn's empType field and manager chain preserved as a text custom field (since Bullhorn does not have a native manager hierarchy on Placement). Compensation components from MDF-based pay structures migrate as custom fields on the Placement record or as separate custom objects if the customer licenses Bullhorn Enterprise.

SAP SuccessFactors Recruiting Management job requisitions (jobReqNumber, jobReqTitle, jobReqStatus, hiringManager) map to Bullhorn JobOrder records. We extract the job title, description (rich text), requirements, and status from SuccessFactors Job Requisition OData endpoints and map them to Bullhorn JobOrder title, description, requirements, and status. The SuccessFactors jobReqId becomes jobOrderID for reconciliation. Open, on-hold, and filled statuses map directly to Bullhorn's JobOrder status values.

SuccessFactors Foundation Object Locations (address, city, state, country, locationCode) map to Bullhorn Branch records. Bullhorn Branch stores office or branch location for staffing operations. We extract the location tree from Employee Central Foundation Object OData and reconstruct it as Bullhorn Branch records with address fields mapped 1:1. Multiple SuccessFactors locations map to one Branch if the customer consolidates offices.

SuccessFactors corporate structure (BU-POD-Division-Department hierarchy from Foundation Objects) maps to Bullhorn Company records representing the customer's own corporate entities. We extract the full org tree from Foundation Object OData endpoints, preserve the parent-child hierarchy as Bullhorn Company records with a parentCompanyId reference, and store costCenterCode and divisionId as custom fields. This is a structural mapping, not a candidate-company mapping, and is scoped separately from external client Companies in Bullhorn.

SuccessFactors MDF (Managed Framework) objects are customer-defined entities with custom fields, picklists, and effective-dating behavior. We perform schema discovery against the SuccessFactors generic-object metadata endpoint to enumerate all active MDF objects, then map them to Bullhorn custom objects. Bullhorn Enterprise editions allow up to 10 custom objects with 55 fields each (Front Office Growth/Enterprise) or 2 custom objects on ATS Growth. We audit the customer's MDF field count against this ceiling before migration and flag any overflow to the customer's Bullhorn admin for consolidation or archival. Custom field types (picklist, text, number, date) map to equivalent Bullhorn field edit types per the Bullhorn field type reference.

SAP SuccessFactors Learning course completions and certifications map to Bullhorn CandidateCertification records. We extract course title, completion date, expiration date, and certification status from the SuccessFactors Learning OData API (which operates under separate stricter rate limits from the main HXM Suite). Bullhorn CandidateCertification records are linked to the Candidate by candidateID. Active course enrollments (not yet completed) are optionally mapped to a custom field on Candidate if the customer requires in-progress training visibility; we scope this decision during discovery.

SuccessFactors Talent Intelligence Hub competency libraries and skill profiles (including translations across language packs) map to Bullhorn CandidateSkill records. We deduplicate the competency library before migration (SAP TIH migration is documented to produce duplicate competencies in target systems per SAP KB), flag inactive job-to-competency associations for customer review, and map competency names to Bullhorn CandidateSkill skillName. Proficiency level maps to Bullhorn skillLevel if populated in SuccessFactors.

SuccessFactors time-off balances and absence records (entitlements, accrual rates, taken/pending balances) depend on the Time Off module being licensed. We export entitlement rows and balance data from Employee Central OData and map them to Bullhorn custom objects (if Bullhorn Enterprise with available custom object slots) or as formatted Note records attached to the Candidate. Approval history and comment threads are not exposed via standard OData and do not migrate. The customer's Bullhorn admin configures time-off tracking in Bullhorn or a paired payroll system post-migration.

SuccessFactors compensation records (base salary, bonus, allowances, stock, pay frequency, currency) are stored in MDF-based pay structures with value types (fixed, percent, lump-sum) that require field-level mapping. We extract payComponent, payCompFixedAmount, currency, frequency, and effectiveDate from the SuccessFactors Compensation Information OData export and map them to Bullhorn custom fields on Placement (salary, bonusAmount, currency) or to a Compensation custom object. Effective-dated history (multiple compensation records over time) is stored as separate rows in Bullhorn with periodDate marking the effective period.

Employee document attachments (offer letters, contracts, performance reviews stored in Employee Central) export via SuccessFactors Integration Center attachment outbound integrations. We route binary files to an SFTP target for Bullhorn to ingest, then link them to the corresponding Candidate record via Bullhorn's ContentDocumentLink mechanism. Only documents linked to the Candidate record (not org-level documents) migrate. The customer's Bullhorn admin configures the document storage repository before migration.