Migrate from SAP SuccessFactors to Crelate

SuccessFactors Employee Central PerPerson records that correspond to job applicants or contingent workers (not full HCM employees) map to Crelate Person records. We map standard fields: firstName, lastName, email (from PerPersonal communication), phone, location (from FO Location), and jobTitle. Employment dates and manager relationships from SuccessFactors do not map directly to Crelate; they become custom fields on the Person record or are retained in the out-of-scope HRIS. Crelate's Person record handles both candidate and contact types, which maps to SuccessFactors candidate profiles from the Recruiting module.

SuccessFactors Recruiting requisitions map to Crelate Job records. We map job title, department (from FO Division), location (from FO Location), employment type, and job description fields. SuccessFactors requisition status (open, on hold, filled) maps to Crelate Job status. Compensation information attached to a requisition in SuccessFactors becomes a custom field in Crelate rather than a native compensation object. Filled requisitions that represent historical placements map to Crelate Placements as a subtype of Job with a linked Person record.

SuccessFactors Recruiting candidate profiles map to Crelate Person records. The application association (candidate-to-requisition) maps to Crelate's application or submission link between the Person and Job. Application status from SuccessFactors (applied, screening, interviewing, offered, hired, rejected) maps to the corresponding Crelate pipeline stage. Candidate source and recruiting channel from SuccessFactors become Crelate Tags or custom fields.

SuccessFactors Foundation Objects (Corporate Structure) are structural HR entities that define the organizational chart, cost centers, and legal entity hierarchy. Crelate does not have an equivalent org-structure model. We map Locations to Crelate Tags on Person or Job records; Divisions and Departments map to Crelate Teams or custom picklist fields. The full org tree from SuccessFactors is exported as a structured reference document for the customer to configure in Crelate after migration.

SuccessFactors Onboarding 2.0 tracks tasks, document collection, and I-9/employment eligibility during the onboarding phase. Crelate does not have a native onboarding task model. Onboarding task completion status and document checklist flags migrate as Notes or Tags on the corresponding Crelate Person record. Incomplete onboarding tasks are flagged in a separate out-of-scope document for the customer's HR team to resolve post-migration.

SuccessFactors competencies and skill profiles from Talent Intelligence Hub do not map to a native Crelate object. We extract competency labels and skill ratings and write them as Tags or a skills-related custom field on the Crelate Person record. As noted in the SAP source gotchas, Talent Intelligence Hub migrations risk duplicate competencies; we run a deduplication scan against the competency library before inserting. Job-to-competency associations for inactive roles are flagged for customer review.

Pay components, salary bands, and compensation history from SuccessFactors Employee Central Payroll have no Crelate equivalent, as Crelate is not a payroll or compensation management system. We export compensation records as a structured CSV reference file and flag them for disposition to a separate HRIS or payroll system. Salary information attached to a job requisition in SuccessFactors migrates as a custom compensation-offer field in Crelate if the customer uses Crelate for offer management.

SuccessFactors performance reviews, goal plans, and 360-degree feedback are stored in proprietary SuccessFactors tables that have no Crelate equivalent. Crelate does not manage performance management, career development plans, or succession planning. We do not migrate these records. The customer receives a written inventory of all active goal plans and performance forms with suggested disposition to a dedicated performance management system.

SuccessFactors Learning enrollments, course completions, and certification records migrate as Tags or a certifications-related custom field on the Crelate Person record if the customer wants compliance and training history visible in the ATS. We note that Learning module API has separate, stricter rate limits from the main HXM Suite OData API; we throttle Learning exports accordingly and export in chunks to avoid the hard 1,000-record ceiling that applies across SuccessFactors entities. Completions and certifications for non-compliance training are flagged as optional data for the customer's L&D team to decide.

Absence entitlements, accrual balances, and time-off request history from SuccessFactors Employee Central have no Crelate equivalent. Crelate does not manage time-off tracking. We do not migrate absence records. The customer receives an export of entitlement balances as a reference CSV for import into their chosen absence management system.

MDF (Metadata Framework) objects are customer-defined in SuccessFactors with custom field schemas, picklists, effective-dating, and conditional visibility rules. There is no universal export schema for MDF entities. We perform a schema discovery step against the target SuccessFactors generic-object metadata endpoint before building the field map, then decide disposition per object: Crelate custom fields if the MDF data is candidate-relevant, or a structured reference CSV export if it belongs in a different HRIS. MDF effective-dating (start/end validity on records) does not map to any Crelate native mechanism.

Employee and candidate document attachments (offer letters, resumes, performance reviews, compliance documents) export via SuccessFactors Integration Center attachment outbound integrations. We route binary files to an SFTP archive in the customer's cloud storage with a manifest CSV that maps each file to its source record ID, candidate name, and document type. Resume files are linked to the corresponding Crelate Person record where Crelate supports file attachment; other document types are archived and referenced in the manifest.