Migrate from SAP SuccessFactors to BambooHR

Core employee records from SuccessFactors Employee Central PerPerson and PerPersonal HRIS elements export via the Compound Employee API. Standard fields (legal name, preferred name, date of birth, nationality, address, emergency contact) map directly to BambooHR Employee fields. The employment status field maps from SuccessFactors personType or employmentType to BambooHR's hire date, termination date, and employment status fields. We use PerPerson's userId as the BambooHR employee ID for dedupe.

SuccessFactors Job Info (jobRelationship, department, division, location, business unit) maps to BambooHR's jobTitle, department, division, location, and supervisor fields. Manager relationships extract from the employment reportsTo field and are resolved to BambooHR supervisorEmployeeNumber during import so that the org chart reconstructs correctly. Effective-dated Job Info entries use the most recent record as the current state unless historical tracking is requested.

SuccessFactors Foundation Objects (org units, cost centers, business units, pay groups) export as a tree structure via Foundation Object OData endpoints. Department records in BambooHR are created from the highest non-company level of the org tree. Locations map from SuccessFactors Location Foundation Object to BambooHR's location field. Cost center and pay group assignments are stored as custom fields on Employee or in a custom table depending on whether the customer needs them filterable in BambooHR.

SuccessFactors MDF-based pay components (base salary, bonus, equity, allowances) with effective dates, currency, and frequency do not have a direct BambooHR equivalent because BambooHR's pay rate is a single field. We discuss the customer's reporting requirements during scoping. For full compensation history, we create a BambooHR custom table (Pro and Elite tiers) with fields for pay component, amount, currency, effective date, and frequency. For a simplified migration, we write the current base salary to the Employee payRate field and note that historical compensation data is preserved in the written handoff document.

Customer-defined MDF objects (Work Orders, Higher Duty Assignments, industry-specific extensions) export via the generic-object metadata endpoint after a schema discovery step. We inspect each custom object definition to extract field names, picklist IDs, and effective-dating behavior, then create equivalent BambooHR custom tables on the destination Pro or Elite account. Note that BambooHR custom tables are not connected to standard Employee records and do not auto-link; the customer chooses whether to store the MDF data as standalone custom table records or as JSON-encoded fields on the Employee for simpler querying.

Absence and time-off balances export from SuccessFactors Time Off module (if licensed), including entitlement rows, accrual rates, and taken/pending balances. We map accrual balances to BambooHR's Time Off feature, creating time-off types that match the SuccessFactors absence types. Taken balance updates after the last payroll run date are imported; pending requests are recreated as open requests in BambooHR. Approval history is not migrated.

SuccessFactors Position Management defines budgeted headcount, incumbent relationships, reportsTo hierarchy, and job associations as structural elements. BambooHR does not have a Position object. We map position incumbent relationships to the BambooHR supervisor chain (each employee's supervisorEmployeeNumber) and flag positions without current incumbents as unfilled roles in the written handoff document. Budgeted headcount and position cost center data are stored as custom fields or in a custom table depending on reporting needs.

SuccessFactors Job Profile and JobCode MDF objects export via OData. Job code, job title, job family, and job level map to BambooHR's jobTitle field and optional custom fields. Competency requirements attached to Job Profiles are noted in the written handoff as requirements for BambooHR's Skills and custom fields feature if the customer needs competency tracking post-migration.

Competency libraries and skill profiles from SuccessFactors Talent Intelligence Hub export with a pre-migration deduplication scan to prevent duplicate skills accumulating in the destination. Inactive job-to-competency associations are flagged for customer review. We map active competencies to BambooHR custom fields on the Employee record (for structured skills) or to the BambooHR Skills feature if available on the customer's tier. Translation metadata from multilingual competency libraries is preserved in the handoff document.

SAP SuccessFactors Learning tracks course enrollments, completions, and certifications via the Learning OData API under stricter rate limits than the main HXM Suite API. We export completion records with course name, completion date, expiration date (for certifications), and status. BambooHR does not have a native LMS, so completion records are stored in a custom table or provided as a CSV alongside the migration. Active and pending enrollments are flagged for manual reassignment in the customer's chosen learning tool post-migration.

Employee document attachments (offer letters, contracts, performance reviews stored in Employee Central) export via Integration Center attachment outbound integrations. We route binary files to an SFTP deposit for the customer's BambooHR admin to associate with the correct Employee record manually, or we deliver them alongside the migration package. BambooHR's document feature accepts uploads per employee, and we provide a file-naming convention that maps to the corresponding employee record.