Migrate your Folks HR data

Core employee profile object with all standard fields: contact info, job title, department, start date, employment status, salary history, and dependent information. Fully accessible via API with OAuth scopes. Export and import are straightforward with direct field mapping.

Leave types, accrual rules, and current balances are stored per employee. The API exposes leave records but accrual calculation logic lives server-side, so we preserve raw balance snapshots and flag that future accruals are not recalculated during migration.

Time entries are recorded by employee with date, hours, and optionally cost code association. We export all historical timesheet records and map them to the destination system's time entry object. Timesheet UI quirks (slanted text boxes) do not affect data quality.

Performance review cycles, review forms, ratings, and comments are stored per employee. The platform supports 360-degree feedback workflows. We export complete review histories including reviewer assignments and preserve the review cycle structure in the destination.

Candidates are tracked through job requisitions with application status, resume uploads, interview scores, and hiring stage. We export the full candidate pipeline including all status transitions and preserve attachment associations for resumes and cover letters.

Employee documents (contracts, tax forms, certifications) and recruitment attachments (resumes, offer letters) are stored separately from core records. The API allows download of individual files; there is no bulk export endpoint, so we retrieve files one-by-one and re-associate them post-migration.

Departments are defined with name, code, and manager assignment. We export the full org structure hierarchy and map it to the destination's department or cost-center object with manager assignments preserved.

Folks HR supports custom fields on employee profiles and potentially on other objects. Custom field definitions and values are exported via API, but field type mapping (dropdown vs text vs date) requires explicit review to ensure correct rendering in the destination system.

Expense reports with line items, receipts, amounts, and approval status are stored. Receipts must be downloaded individually—there is no bulk-download API endpoint. We export expense report metadata and flag that receipt files require individual retrieval.

User accounts with role-based permissions (admin, manager, employee) are defined per employee. We export user roles and permission sets and map them to the destination's role model, noting that role nomenclature may differ between platforms.

Folks HR supports integrations with third-party tools including payroll systems and Merge.dev. Integration configuration and sync history are platform-specific and do not transfer across systems. We do not migrate integration connection settings; these must be re-established in the destination.