Migrate from Simplicant to Bullhorn ATS & CRM

Simplicant Jobs map to Bullhorn JobOrder records. The Job title, description, department, location, and current pipeline stage migrate as JobOrder fields. In Bullhorn, JobOrder holds the published job state, and the bullhorn_job_status field tracks open, closed, or on-hold. We map Simplicant pipeline stage names to Bullhorn JobOrder status values and configure record type assignments per business line during migration. JobOrder ownership maps from the Simplicant recruiter assignment.

Simplicant Candidate records map to Bullhorn Candidate with 1:1 correspondence. Contact details, email, phone, source attribution, and application date transfer directly. In Bullhorn, Candidate is the primary talent pool record and is linked to JobOrder via a CandidateJobOrder join record that tracks the application stage. We preserve application history as Bullhorn CandidateJobOrder records with status and date fields set from Simplicant's stage history.

Simplicant Departments are organizational metadata that attach to Jobs. We map Department names to Bullhorn Category records, which serve as the corporate classification for jobs and candidates. Bullhorn's Category object supports a hierarchy, so multi-level department structures in Simplicant map to parent-child Category relationships in Bullhorn.

Simplicant Locations attached to Jobs map to Bullhorn JobLocation records. Bullhorn JobLocation stores city, state, and country; we infer the full address components from Simplicant's location data where available. JobLocation records are linked to JobOrder at migration time.

Simplicant Interview Packets bundle structured evaluation forms with field names and scoring conventions that vary by organization. Bullhorn does not have a native interview packet object; completed evaluations migrate as CandidateReference records with evaluation scores stored in custom fields on the CandidateReference or on the Candidate object. We map form field names to Bullhorn custom fields, flagging any form schema that exceeds Bullhorn's 55-field custom object limit for the applicable tier.

Simplicant Offer records contain salary, start date, terms, and e-signature status. Bullhorn's Placement object captures the placement of a Candidate in a JobOrder with billing information, start date, and employment terms. We map Simplicant Offer fields to Placement fields, with the original offer e-signature status preserved as a custom field note. Placement in Bullhorn is the record that links Candidate, JobOrder, and the client (Contact/ClientCorporation) into a billable placement event.

Simplicant Hiring Pipelines define stage sequences per job type with automation routing rules. Bullhorn's stage model uses JobOrder status values and, in Bullhorn Automation (formerly Herefish), workflow sequences. We map pipeline stage names to Bullhorn JobOrder status values and deliver a written inventory of Simplicant pipeline automation rules for the customer's Bullhorn admin to rebuild in Bullhorn Automation or via Bullhorn workflow configuration. Active automation definitions do not migrate as executable code.

Simplicant stores resumes, cover letters, and HR files as attachments on Jobs and Candidates. Bullhorn links documents via Salesforce ContentDocument records attached to Candidate, JobOrder, or Placement. We extract document binary data from Simplicant's cloud storage (contingent on plan tier and API access), transform file names and MIME types, and upload to Bullhorn with ContentDocumentLink records pointing to the parent Candidate or JobOrder. Plan-tier document storage availability in Simplicant is confirmed during scoping.

Simplicant Users with role-based access map to Bullhorn User records. Bullhorn User licensing is per-seat, so we resolve every Simplicant user referenced on a Job, Candidate, or Offer record and map to a Bullhorn User by email. Inactive Simplicant users are mapped to inactive Bullhorn users to preserve ownership history without incurring license cost. The customer's Bullhorn admin provisions any missing users before the migration phase begins.

Simplicant's onboarding module tracks offer acceptance transitioning into new hire setup tasks. Bullhorn Onboarding (formerly Able) manages the onboarding workflow post-placement. We export completed onboarding record state and current task list status from Simplicant. Complex branching automation sequences may not be exportable without API access; in those cases we deliver a written summary of onboarding workflow definitions for the customer's Bullhorn admin to reconfigure in Bullhorn Onboarding.

Simplicant stores structured screening scores and evaluation ratings per candidate per stage. Score ranges and weighting logic vary by organization and form. We export raw score data and map to Bullhorn custom fields, flagging any score schema that requires more than the Bullhorn ATS tier's 55-field custom object capacity. Score weighting logic (how Simplicant aggregates scores into a ranking) does not migrate as executable logic; it is documented for the customer to rebuild in Bullhorn's reporting layer.

Simplicant organizations add custom fields to Jobs and Candidate profiles for industry-specific data. Bullhorn supports custom fields on all primary entities (Candidate, JobOrder, Placement, Contact, ClientCorporation, Lead, Opportunity). We pre-create Bullhorn custom fields during schema design, mapping data types from Simplicant to the closest Bullhorn field type. Bullhorn's Edit type restrictions (up to 20 of any combination of specific edit types per custom object) are factored into the field mapping plan. On Bullhorn ATS tier, the 2 custom object limit may require consolidating Simplicant custom fields into fewer Bullhorn custom objects using multi-select picklists or delimited text fields.