Migrate from Journeyfront to Bullhorn ATS & CRM

Journeyfront Job records map to Bullhorn JobOrder. Job title, description, location, department, employment type, and job board posting status migrate directly. Bullhorn JobOrder uses a standard schema with fields for title, address, employmentType, and payRate. We remap Journeyfront's custom job board status field to Bullhorn's isPublic or jobBoardList. If the customer has client-specific job workflows (common in BPO contexts), we map each Journeyfront job workflow to a Bullhorn Record Type on JobOrder.

Journeyfront Candidate records migrate to Bullhorn Candidate as the primary container. Contact information, work history, and employment eligibility data map to standard Bullhorn Candidate fields. Any pre-existing Candidate records in Bullhorn (from a prior ATS or test setup) are flagged by email address dedupe before import to avoid duplication.

Journeyfront assessment scores migrate as custom fields on the Bullhorn Candidate record. We create custom fields (up to 55 per Custom Object under Enterprise, 2 custom objects on Bullhorn ATS) to capture assessment dimension scores, total score, and assessment date. The company-specific predictive model does not migrate — we flag this gap during scoping and advise the customer to document their assessment rubric for manual baseline setup in Bullhorn. Scores are historical data, not re-runnable logic.

Journeyfront screening questions and responses vary by job and client in BPO contexts. We extract question text, answer type, and the candidate's response, then map to Bullhorn Candidate custom fields (if question count is under 20) or a Bullhorn Custom Object (if client-specific screening recipes have 20+ fields). We preserve the relationship between the screening response and the originating JobOrder via the Candidate Wrapper record.

Journeyfront pipeline stages are customizable per job or client workflow. Bullhorn uses a four-stage submission model (Submission, Client Submission, Interview, and Placement) controlled by Record Type and Sales Process. We remap Journeyfront stage names to the nearest Bullhorn submission status, and where the customer's workflow requires custom stages (common in BPO client-specific hiring), we configure Bullhorn Record Types to preserve the stage taxonomy. Stage automation triggers do not migrate — we document them for Bullhorn Workflows rebuild.

Journeyfront Interview records (interviewer assignment, scheduled date/time, scorecard, recommendation) map to Bullhorn Candidate Wrapper with a linked Note for scorecard content and an Appointment record for the scheduled time. We preserve the Interview recommendation field as a custom field on the Candidate Wrapper. If Journeyfront interview scorecards use a structured format, we create Bullhorn custom fields to hold each dimension score.

Journeyfront Offer records (position, compensation details, status, candidate response) map to Bullhorn Candidate Wrapper with a status value of Offer Extended, Offer Accepted, or Offer Declined. Compensation fields map to Bullhorn custom fields on Candidate Wrapper if Bullhorn's standard payRate fields do not capture the full offer detail.

Journeyfront users, hiring managers, and interviewers linked to candidate records map to Bullhorn User records. We resolve by email match against Bullhorn's User table. Any Journeyfront user without a matching Bullhorn User goes to a reconciliation queue for the customer's Bullhorn admin to provision before record import proceeds.

Journeyfront BPO clients with customized screening recipes and regional compliance requirements map to Bullhorn ClientCorporation. Client name, address, and contact details migrate directly. Regional compliance tracking data maps to custom fields on ClientCorporation. Client-specific screening recipes migrate to Bullhorn Custom Objects linked to ClientCorporation if the Bullhorn edition supports them.

Journeyfront automation rules (stage triggers, score thresholds, time delays) do not migrate as code. We extract rule definitions during scoping and deliver a written workflow inventory with each rule's trigger, conditions, actions, and recommended Bullhorn Workflow equivalent. The customer's Bullhorn admin or a Bullhorn partner rebuilds the rules post-migration. Bullhorn Workflows (formerly Herefish) are a separate add-on at $30-50/user/month.

Journeyfront analytics dashboards (turnover reduction, tenure improvement, SLA metrics) generate dynamically and cannot be exported as raw records. We recommend exporting PDF or CSV snapshots of key reports before migration cutoff. The underlying candidate, assessment, interview, and offer data migrates normally. Bullhorn Canvas ($40-60/user/month add-on) or a third-party BI tool (Tableau, Power BI via Bullhorn REST API) becomes the new reporting foundation.

Journeyfront integrations with job boards, background check vendors, and HRIS systems are configured via API credentials that do not export. Job board posting integrations, background check connections (Checkr, Sterling, HireRight), and HRIS sync settings must be reconfigured in Bullhorn manually. We provide a written inventory of all active Journeyfront integrations during scoping so the customer's Bullhorn admin can reconfigure them in parallel with migration.