Migrate your SAP SuccessFactors data

The core PerPerson and PerPersonal HRIS elements export cleanly via OData Compound Employee API. Standard fields (name, employment dates, manager relationships) map 1:1. We preserve the employment status and userSysId as primary keys for downstream reference integrity.

Job Profile data is stored in JobCode and JobProfileLoc MDF objects. Standard fields export via OData. Job-to-position associations are preserved as foreign-key links in our load sequencing.

Position Management is a structural framework, not just a data object. Positions define budgeted headcount, reportsTo hierarchy, and job association. We map position incumbent relationships to the destination's equivalent org-chart model, flagging vacant positions separately from filled ones.

Compensation records include pay components, currency, frequency, and effective dates. MDF-based pay structures require field-level mapping because value types (fixed, percent, lump-sum) differ across source and destination schemas. Effective-dated history is preserved as separate rows.

Corporate Structure objects export via Foundation Object OData endpoints. Department hierarchies, cost centers, and location assignments are extracted as a tree and reconstructed in the destination using parent-child links.

Absence and time-off balances depend on the Time Off module being licensed. We export entitlement rows, accrual rates, and taken/pending balances. Approval history and comment threads are optionally included in extended scoping.

Goal plans and performance form data are stored in SuccessFactors proprietary tables. Goal content is text-heavy and requires re-authoring in most destination systems, though we preserve goal metadata, ratings, and linked competencies as structured records.

SAP SuccessFactors Learning tracks course enrollments, completions, and certifications. The Learning OData API operates under separate rate limits (stricter than the main HXM Suite API). We export completion records and transcript rows, preserving certification expiry dates.

Competency libraries and skill profiles are managed via the Talent Intelligence Hub. During migration, we flag duplicate competencies, map inactive job-to-competency associations, and preserve translated competency labels across locales. This is a known pain point — SAP KB articles document specific migration failure modes we explicitly handle.

Managed Framework (MDF) objects are customer-defined entities with custom fields and picklists. Standard MDF objects (Work Order, Higher Duty Temp Assignment, Onboarding Info) export via generic-object OData endpoints. We inspect the target MDF schema at scoping time and build a field map before load.

Employee document attachments (offer letters, contracts, performance reviews stored in EC) can be exported via Integration Center attachment outbound integrations. We route binary files to an SFTP target or blob storage and create association records pointing from the employee to the document.

Foundation Objects are the building blocks of the corporate data structure. They are predelivered standard objects in Employee Central. We export locations, business units, divisions, and pay groups as lookup tables and load them before employee records to satisfy foreign-key constraints.

Workflow audit trails and step-by-step approval history are not exposed via standard OData APIs. Reconstructing approval chains from system notes is possible but requires manual mapping. We do not currently migrate workflow history as a structured object.