Migrate from PeopleStrong to BambooHR

PeopleStrong Employee records map to BambooHR Employee with personal details (name, date of birth, address, contact), employment status, department, job title, manager assignment, and hire/termination dates. We use employee email as the dedupe key. Any PeopleStrong employee records without a valid email address are held in a reconciliation queue for the customer's HR admin to resolve before import. BambooHR does not support a separate user account object separate from employee records the way PeopleStrong does; we separate PeopleStrong user accounts with login credentials from employee records without system access during scoping.

PeopleStrong organizational units (departments, cost centers, locations) migrate as reference tables before the Employee object to satisfy dependency requirements. In BambooHR, departments and locations are standard lookup fields on the employee record. We preserve the full hierarchical structure using the parent department relationship where applicable.

Job titles, grade structures, and band definitions migrate as value maps before the employee object. PeopleStrong stores these as lookup tables referenced by employee and payroll records. We create the corresponding BambooHR job titles during the configuration phase so they are available as valid options when employee records are imported.

Payroll records (salary components, deductions, pay periods, payslip metadata) migrate from PeopleStrong as payrun cycles tied to date ranges. We establish a cut-off date aligned with the customer's payroll calendar and verify with the HR admin that the final payrun is complete before executing the export. CRITICAL CONSTRAINT: BambooHR Payroll is US-only. Organizations with PeopleStrong payroll active in India, the Philippines, Southeast Asia, or the Middle East cannot migrate payroll data to BambooHR. We flag this during scoping and scope payroll history out of the migration for non-US destinations, providing a written explanation of the constraint for the customer's finance and HR leadership.

PeopleStrong attendance data (clock-in/out timestamps, regularization requests, shift assignments) maps to BambooHR's time-off tracking. Regularization status and pending requests migrate as BambooHR time-off requests with appropriate status flags. Shift assignments are preserved in custom fields if no native BambooHR equivalent exists. Attendance data tied to specific pay periods requires careful date-range scoping to avoid pulling partial pay periods.

Leave management in PeopleStrong (accrued balances, request records, approval status, leave type by earned/casual/sick) maps to BambooHR time-off types and balances. Leave types from PeopleStrong map to BambooHR time-off policies with the accrual method and carryover rules preserved as policy configuration. Pending and historical leave requests migrate as time-off history entries.

PeopleStrong Performance Management module records (review cycles, ratings, goals) map to BambooHR's Performance Management feature, which is included only at the Pro tier ($17/employee/mo) or above. We probe the active module list during scoping to confirm whether the Performance Management module is licensed. If not licensed, we flag that review history cannot be migrated. Review templates vary by organization in PeopleStrong; we map standard fields (reviewer, reviewee, rating, date, comments) to BambooHR's review structure and hold configurable template content as a written reference document for the admin to rebuild.

PeopleStrong recruitment module records (candidates, job applications, interview scores, offer letters) map to BambooHR's Applicant Tracking System, which is a separate add-on priced at $99-$199/month and separate from the core HR subscription. We probe ATS scope during scoping. If the customer does not license BambooHR ATS, we export candidate records as a structured CSV with full resume data, stage history, and recruiter assignments and deliver it as a written inventory for manual upload or integration into a separate ATS.

Salary revisions, effective-dated compensation changes, and bonus payouts stored as separate objects in PeopleStrong map to BambooHR's Compensation Management feature, available only at the Elite tier ($25/employee/mo). Compensation effective dates are preserved as BambooHR compensation entries. If the customer is on a lower tier, we migrate compensation history as historical records in a custom field or as a structured data export for manual entry.

PeopleStrong supports organization-level custom fields on employee records with schema that varies by tenant and is not consistently exposed via the public API. We perform a schema discovery step during scoping to enumerate all active custom fields and their data types before building the migration mapping. Custom fields migrate to BambooHR custom fields of matching type (text, number, date, dropdown). Fields with options migrate as single-select or multi-select picklists in BambooHR.

Employee documents (offer letters, contracts, ID proofs) stored as binary attachments linked to PeopleStrong employee IDs require separate file-level API retrieval after the primary record export. We separate the migration into a record phase and a document phase. The document phase runs as a secondary batch using employee email as the lookup key to avoid timeout errors on large file volumes. Document type classification from PeopleStrong maps to BambooHR document categories.