Migrate from Folks HR to Crelate

Folks HR recruitment candidates map directly to Crelate Candidate records. We transfer full name, contact information (email, phone, address), application status, source channel, and any rating or score data. The Folks HR candidate_id becomes a reference field in Crelate's custom fields for post-migration audit. Candidate status values (new, screening, interview, offer, hired, rejected) map to Crelate's status pipeline, with custom statuses preserved in a mapped field if the customer has customized them.

Folks HR job postings and requisitions map to Crelate Job records. We transfer job title, description, department assignment, employment type (full-time, part-time, contract), location, salary range, and requisition status (open, filled, cancelled). Active job requisitions in Folks HR become open Jobs in Crelate; historical jobs map as closed Jobs with their original posting dates preserved.

Folks HR tracks candidate status transitions through the hiring pipeline with timestamps. We create Crelate Activity records for each status change (applied, screening, interview scheduled, offer extended, hired, rejected) with the original timestamp and the user who made the transition. Status history is preserved as an activity log attached to the Candidate rather than a separate object.

Folks HR resume uploads and application attachments migrate to Crelate Candidate attachments. Each file is downloaded individually from Folks HR (no bulk endpoint) and uploaded to the corresponding Crelate Candidate record. We preserve original filenames and file types (PDF, DOCX). For candidates with multiple resume versions, the most recent is flagged as primary. This step extends migration duration for large document archives.

Folks HR interview scores, interviewer feedback, and rating data transfer as Crelate Activity notes attached to the Candidate. Structured ratings (numerical scores) are preserved in custom fields; free-text feedback is stored as Activity note content. We link the interview activity to the assigned interviewer (mapped to a Crelate User by email match) and preserve the interview date.

Folks HR users assigned as recruiters, hiring managers, or interview panel members map to Crelate User records by email match. We resolve the ownership chain: the primary recruiter on a candidate or job maps to the Crelate User who owns the record. Any Folks HR user without a matching Crelate User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Folks HR departments map to Crelate Departments, which are used for organizing jobs and reporting within Crelate. Department name and code transfer. However, Crelate Departments do not carry the full HR organizational hierarchy (manager assignments, cost codes, headcount) that exists in Folks HR; that data is HR operational and does not map into Crelate's recruiting model.

Folks HR custom fields on candidate records (dropdown, text, date, number, checkbox) map to Crelate custom fields. We export the field definitions and values during scoping, then pre-create equivalent custom fields in Crelate before migration. Field type mapping is required: Folks HR dropdown values become Crelate picklist values, text fields map directly, and date fields use Crelate's date type.

Folks HR employees do not map directly to Crelate Candidates because the data model purposes differ. Current employees who are also candidates (internal hires, referrals) require a dual-record strategy: we create a Crelate Contact for HR/employment data and a Crelate Candidate record for the recruiting pipeline data. This is handled during scoping based on the customer's internal mobility policy.

Folks HR employee documents (employment contracts, tax forms, certifications, policy acknowledgments) are HR operational records with no Crelate equivalent. Crelate is an ATS and recruiting CRM, not an HR document management system. We flag these documents during scoping and recommend either retaining them in Folks HR (if keeping a subset), exporting them to a dedicated HR document archive, or migrating to a separate HRIS. This is not a data loss issue; it is a scope boundary.

Folks HR leave management data (leave types, accrual rules, current balances, request history) does not map to any Crelate object. Crelate has no leave management, time-off tracking, or accrual engine. We export leave balance snapshots as a CSV for the customer's reference and recommend they retain Folks HR or move to a dedicated HRIS with leave management capabilities. This is an explicit scope gap, not a technical limitation.

Folks HR time entry records (hours logged, cost codes, timesheet approval status) have no Crelate equivalent. Crelate does not support time tracking or timesheet management. We export timesheet summaries as CSV for record-keeping but do not transfer time data into Crelate. Customers requiring time tracking post-migration need a separate tool.

Folks HR performance review cycles, 360-degree feedback, ratings, and review forms do not map to Crelate. Crelate is a recruiting platform and does not include performance management or HR review tools. We export review history as a structured document or CSV during migration, but customers requiring ongoing performance management need a dedicated platform (BambooHR, Lattice, Culture Amp).