Migrate from PeopleForce to BambooHR

PeopleForce Employee records map directly to BambooHR Employee. The core fields (first name, last name, email, hire date, termination date, employment status, work phone, mobile phone) transfer directly. We flag that BambooHR stores some job-related fields (department, job title, location) on the Employee record rather than in linked objects, so we flatten the Position fields into the appropriate BambooHR Employee tab during import. Active and inactive status maps to BambooHR's employment status field with hire date and termination date preserved for historical records.

PeopleForce Profile stores photo, bio data, emergency contacts, and skills as structured sub-objects. We flatten these into the BambooHR Employee personal information section. Emergency contact name, relationship, and phone number transfer to BambooHR's emergency contact fields. Profile photos migrate as file attachments linked to the Employee record. Skills migrate to BambooHR custom fields if the customer has defined them, or to a supplemental import file if BambooHR's standard fields do not accommodate the skill taxonomy.

PeopleForce Positions capture job title, department, employment type, and effective dates per employee with historical versions stored as separate linked records. BambooHR stores current job title and department directly on the Employee record with an optional Job History table for prior positions. We take the most recent Position record as the current job info, populate BambooHR's department and job title fields, and create a Job History entry for each prior position. Where multiple Position records exist for the same effective date range (a PeopleForce data anomaly), we use the most recently modified record and flag the conflict in the reconciliation report.

PeopleForce Leave Policies with accrual rules and Leave Requests with approval status transfer to BambooHR Time Off. We migrate the current leave balance for each employee as an opening balance in BambooHR and the historical leave request records as approved time-off entries with dates, type, and status. Policy definitions (accrual rates, carryover rules, policy names) are inventoried and documented for manual reconfiguration in BambooHR Time Off Settings because accrual calculation logic is platform-specific and cannot be migrated as executable rules.

Completed PeopleForce review cycles and submitted review feedback migrate as historical records. Review scores, competency ratings, and reviewer comments transfer to BambooHR's Performance module as completed review entries linked to the employee. PeopleForce's configurable review form builder questions, scales, and weighting configurations are documented in a written review-form inventory because the form builder itself does not export. The customer's BambooHR admin rebuilds review templates using BambooHR's custom review cycle builder post-migration.

PeopleForce employee documents (contracts, ID copies, certifications) stored per employee record migrate as file attachments to the corresponding BambooHR Employee record. We extract document metadata (filename, upload date, file type) and the binary content via the PeopleForce API or admin export. The document is reattached to the BambooHR Employee file section. File naming conventions from PeopleForce are preserved to aid retrieval after migration. Any documents stored outside the employee record (org-level templates) are inventoried separately.

PeopleForce stores compensation as linked records (salary, bonus, equity, effective dates) per employee. BambooHR's Pro plan includes Compensation Management with benchmarking and planning; Core lacks native compensation storage. For Core-tier destinations, we migrate compensation data to a custom fields structure (salary amount, salary effective date, bonus amount, bonus effective date, currency) that the customer's admin configures before import. For Pro-tier or higher destinations, we map compensation records to the native Compensation Management module.

PeopleForce employment history records (prior job titles, department changes, employment type changes) migrate to BambooHR Job History entries. Each history record includes the effective date, job title, department, and employment type. Employment type changes (full-time to part-time, contractor conversion) are captured as separate Job History entries with effective dates. We sort entries by effective date before import to maintain chronological order in BambooHR's Job History timeline.

PeopleForce Kudos given between employees with timestamps and optional messages migrate to a supplemental import file that the customer can load into BambooHR's Employee Experience module if that module is active. BambooHR's Employee Experience (Pro+ tier) includes recognition features that can accommodate kudos-style entries. If the customer does not have Employee Experience enabled, we document the kudos data in a CSV deliverable with employee names, kudos sender, message, and timestamp for manual re-entry or future Employee Experience activation.

PeopleForce custom fields on the Employee object are inventoried during discovery with their data types (text, number, date, dropdown, checkbox). We pre-create matching custom fields in BambooHR using the Custom Field Builder (available from Core tier) before employee data import. Dropdown custom fields require a value-mapping table if the PeopleForce dropdown options do not match BambooHR's allowed values. Boolean and checkbox fields migrate directly. Any PeopleForce custom fields containing protected personal information (SSN, bank details) are flagged and excluded from migration per data protection policy.