Migrate from hireful to BambooHR

Hireful Vacancy records map to BambooHR Job (Jobs) records. We map vacancy title to Job Title, vacancy description to Job Description, and vacancy status to Job Status. Pipeline stage order from hireful is captured as a sequence note and reconstructed manually in BambooHR's pipeline settings post-migration. Vacancies on hireful Hero and Pro plans with vacancy approval workflows do not migrate; we document the approval chain as a numbered step list for the customer's BambooHR admin to reconfigure in Workflows.

Hireful Candidate records map to BambooHR Employee records via the native employee import. We map candidate name fields, email address, phone number, work history, and skills. Hireful's EDI disability and ethnicity data (stored at application level) is mapped to custom BambooHR fields that we create before migration. CV and resume attachments are downloaded from hireful and uploaded to the corresponding BambooHR Employee record as documents in the Hiring or Documents tab. The migration does not run a background check or DBS check value through unless it is stored as a structured text field in the candidate profile CSV.

Each hireful Application record maps to a BambooHR Applicant record linked to the corresponding BambooHR Job. Application status (Applied, Shortlisted, Interviewing, Offer, Rejected, Withdrawn) maps to BambooHR Applicant Status values. Candidate answers to application form questions are mapped to BambooHR applicant data fields. On hireful Pro and above, bespoke custom application form structures do not have a direct BambooHR equivalent and require manual form rebuilding in BambooHR's applicant configuration post-migration; we document the original form fields and their data types for this rebuild.

Custom application forms with bespoke field sets available on hireful Pro and Hero tiers require a two-step approach. We export form field definitions and candidate responses separately, then map each response value to the corresponding BambooHR applicant data field. Free-text fields migrate without transformation. Multi-select and conditional logic fields cannot carry their conditional branching to BambooHR and are flagged for manual form rebuild. We deliver a written form-field inventory during the handoff.

Hireful hiring manager seat assignments map to Owner or Assignee fields on the BambooHR Job record. In BambooHR, any active Employee record can be assigned as a hiring manager on a Job. We map the hireful portal user's email address to the corresponding BambooHR Employee email and assign them as the job owner. Hireful's unlimited hiring manager seat model means we can assign all identified hiring managers without licence count restrictions in BambooHR at the Core tier and above.

Hireful interview schedules recorded as structured events map to BambooHR Events. We map the interview date and time, interviewer name, interview location or meeting link, and interview type (phone, video, in-person). BambooHR's self-service scheduling feature (Grow tier and above in hireful) does not migrate as a configuration; we document the original scheduling setup so the customer's BambooHR admin can configure BambooHR's interview scheduling or integrate with a calendar tool post-migration.

Hireful applicant scoring and recruiter evaluation notes stored against Application records are mapped to BambooHR rating or custom notes fields on the Applicant record. We export structured score values as integer or decimal fields and free-text evaluation notes as text fields. Hireful Hero plan's recruitment audit and candidate survey data migrate as text notes with a survey-response flag. Structured score comparisons across candidates require a custom report to be built in BambooHR after migration.

CV and uploaded documents attached to hireful Candidate records are extracted via hireful's download interface and uploaded to the corresponding BambooHR Employee record. We associate each document to the correct employee using the candidate email as the dedupe key. If the candidate was hired, the CV is placed in the BambooHR Employee Documents tab under the Hiring section. Documents are imported in their original format and encoding is normalised to UTF-8 before upload.

Hireful GDPR deletion flags, retention timestamps, and subject access request records are not included in the standard CSV export. We extract these values directly from the hireful admin interface during scoping and include them as metadata in the migration package. In BambooHR, deletion of candidate data requires manual action; we deliver a deletion schedule spreadsheet with candidate email, original hireful deletion date, and retention expiry to the customer's HR admin for manual processing post-migration.

Hireful's automatic talent pooling feature on the Pro tier creates segmented candidate groups for re-engagement. BambooHR does not have a native talent pool object. We export talent pool membership as a tagged list in the migration metadata and recommend rebuilding the segmentation as BambooHR Employee Tags or as a manual list in BambooHR. The customer's HR admin rebuilds the automated re-engagement logic in BambooHR Workflows post-migration or retains the talent pool list as a working document.