Migrate from Journeyfront to BambooHR

Journeyfront Jobs map to BambooHR Job Openings. We extract job title, description, location, department, employment type, and posting status. Job board distribution settings do not migrate because BambooHR handles job distribution through its own native job board posting integrations, which must be reconfigured in the BambooHR ATS settings post-migration. Closed or archived Journeyfront jobs map as inactive Job Openings in BambooHR.

Journeyfront Candidate profiles map to BambooHR Candidate records, which store contact information, work history, screening responses, assessment scores, interview ratings, and pipeline stage. The candidate's email address is the dedupe key. We preserve the full candidate history including all associated interviews, offers, and assessment scores as structured fields in BambooHR's ATS candidate profile. Any candidate in an active pipeline stage at migration cutoff is flagged for the customer's review before cutover.

Journeyfront's company-specific calibrated assessment scores migrate as structured custom fields on the BambooHR Employee record or as applicant custom fields if the candidate has not yet been hired. We preserve the raw score, percentile, and any pass/fail threshold as separate fields. The underlying predictive algorithm does not export; the assessment model resets in BambooHR. We document every assessment field migrated so the customer's HR team can re-establish baseline scoring if they choose to use a third-party assessment tool post-migration.

Customizable screening questions vary by job and client in Journeyfront's BPO contexts. We extract question text, answer types, and scoring rubrics and remap them to BambooHR's custom application question format. BPO-specific screening recipes (client-customized question sets) cannot map to BambooHR's single-company ATS schema without significant restructuring; these are documented as a gap in the migration inventory and flagged for manual rebuild in BambooHR's job configuration if needed.

Journeyfront's customizable pipeline stages per job or workflow require remapping to BambooHR's standardized ATS stage names. We extract the full stage list from Journeyfront, map each stage to the nearest BambooHR equivalent, and flag any non-standard stages (common in BPO workflows with client-specific stage names) as requiring manual configuration in BambooHR's job pipeline settings post-migration. Stage automation triggers are extracted and documented but do not migrate as rules.

Journeyfront Interview records (interviewer assignment, scheduled date/time, scorecard, overall recommendation, and linked notes) map to BambooHR Interview records attached to the Candidate. We preserve interviewer name, date, scorecard ratings, and recommendation. Any notes associated with the interview are appended to the candidate's BambooHR record as plain text.

Journeyfront Offer records (position, compensation details, offer status, candidate response, and offer letter) map to BambooHR's offer tracking within the candidate record. We preserve compensation fields, offer status values, and the candidate's response. Offer letter documents migrate as file attachments to the candidate record.

Journeyfront Users, Hiring Managers, and Interviewers tied to candidate records map to BambooHR Employee and User records. Role assignments (Hiring Manager, Recruiter, Interviewer) are stored as BambooHR employee job title and custom fields. BambooHR's permission model differs from Journeyfront's role-based hiring team assignments; we document the role mapping and flag any permission structures requiring rebuild in BambooHR's admin settings.

Journeyfront workflow automation rules (stage-triggered, score-threshold-triggered, and time-delay actions) are extracted and documented. BambooHR supports basic workflow automation for employee data updates but does not have a recruiting-stage automation model equivalent to Journeyfront's pipeline triggers. We deliver a written inventory of every active Journeyfront automation rule with its trigger conditions, actions, and a recommended BambooHR equivalent or alternative approach. The customer's admin rebuilds these manually post-migration.

Journeyfront's performance analytics dashboards (turnover reduction, tenure improvement, SLA metrics, predictive insights) are generated dynamically from raw records and do not export as flat data. We recommend exporting PDF or CSV snapshots of key reports before migration cutoff. All underlying candidate, assessment, interview, and offer data migrates normally. The customer's HR team rebuilds any required reporting in BambooHR's HR Insights module using the migrated data.