Migrate from Factorial to BambooHR

Factorial Employee records map directly to BambooHR Employee. We transfer name fields, contact information, employment status, hire date, job title, and department via lookup. Factorial's employment status values (active, inactive, on leave) map to BambooHR's status field. We discover all active custom employee fields during scoping by calling the employee endpoint and enumerate each one for mapping to BambooHR custom fields before production migration.

Factorial departments and cost centers with parent-child relationships map to BambooHR Locations as the primary organizational unit, with a custom department field added to Employee for multi-level hierarchies. We preserve the full organizational tree and flag any departments with no assigned employees for customer admin review.

Factorial absence types and approved records map to BambooHR time-off policies and time-off history. Accrual balances are preserved as snapshots at migration time, but BambooHR's accrual rules must be reconfigured to match the original Factorial accrual logic (monthly, yearly, or anniversary-based). Custom absence types discovered during scoping are mapped to BambooHR equivalents or flagged for policy creation.

Factorial documents attached to employee records migrate as files on the corresponding BambooHR Employee. Factorial does not expose a bulk document export endpoint, so we paginate the documents list via API and download each file individually. We flag document-heavy migrations (over 500 files per account) during scoping and set timeline expectations accordingly. BambooHR applies per-file size limits that we verify against the source archive during discovery.

Factorial stores historical salary changes, bonuses, and equity grants as effective-dated compensation records on each Employee. We migrate these as separate entries on the BambooHR Employee Employment Info tab for current pay, with any additional historical compensation entries stored as custom date-stamped fields or a migration-specific notes field. Effective dates are preserved to maintain the full compensation timeline.

Factorial clock-in/out records and timesheets with timestamps, hours, and project or cost-center tags migrate to BambooHR time tracking as individual entries in chronological order. Original timestamps are preserved. Factorial project and cost-center tags that have no BambooHR equivalent are stored in a custom field for admin reference. Large time-entry archives (over 50,000 records) require batch processing with reconciliation by employee and date range.

Factorial employment contracts including contract type, working hours, probation period, and legal entity reference map to the BambooHR Employment Info tab. Country-specific legal clauses and mandatory fields that do not map directly to BambooHR standard fields are stored in custom fields or the contract notes section. The customer admin should verify all country-specific contract fields after migration against local labor requirements.

Factorial custom fields on Employee, Contract, and Document objects are discovered during scoping by calling the relevant endpoints. We map each Factorial custom field to a BambooHR custom field of the matching type (text, number, date, dropdown, checkbox). Fields with no direct BambooHR equivalent are flagged in the mapping document for the customer admin to review and resolve before production migration.

Approval chains for time-off, expenses, and documents are defined as Factorial workflow objects with no export representation. BambooHR uses custom approval workflows with a different configuration model. We do not migrate workflows as code. We document the active Factorial workflow structure (trigger, conditions, approvers, actions) during discovery and deliver it as a written map so the customer admin can rebuild approvals in BambooHR's workflow configuration.

Factorial payroll runs are tied to the country legal entity and include gross salary, deductions, supplements, overtime, and net pay. We export payroll data as structured compensation records with gross amounts and deduction codes preserved. Net pay calculations, tax withholding, and social security contributions must be recomputed in BambooHR's payroll logic or in the third-party payroll provider the customer selects post-migration. Payroll data is not imported as paid payroll runs in BambooHR.