Migrate from Workday Recruiting to Bullhorn ATS & CRM

Workday Supervisory Organizations form the org chart and are the prerequisite for every Position write. Bullhorn has no equivalent org hierarchy object. We extract the supervisory tree from Workday org chart data you provide, map each Supervisory Organization to a Bullhorn Corporate record (as a Client Corporation or internal corporate entity), and use it as the parent reference for Job records. This is a flat map — Bullhorn does not enforce parent-child org validation on candidate writes.

Workday Positions represent headcount slots and belong to a Supervisory Organization. Bullhorn Jobs represent open job orders and do not require a position hierarchy. We map each Workday Position with an active Requisition to a Bullhorn Job, carrying title, department, location, employment type, and salary range into Bullhorn's Job fields. Positions without active Requisitions are held as reference records with a note flag for your Bullhorn admin to create corresponding Jobs manually or in batch.

Workday Job Requisitions are the core recruiting object and map cleanly to Bullhorn Job records. We preserve all standard fields: title, department, location, employment type, salary range, hiring manager, recruiter assignment, status, and creation date. Confidential Requisitions map to Jobs with restricted visibility flags set in Bullhorn. Requisition approval status is serialized as a Job note since Bullhorn does not have a native approval-chain object on Job.

Workday Candidates are the talent pool entity, separate from Workers. Bullhorn Candidates are the unified talent record across all job applications and placements. We map Workday Candidate fields (name, email, phone, address, source, tags, and custom properties) directly to Bullhorn Candidate. The dedupe key is email address, validated and normalized before insert. Any Workday Candidate with multiple Applications is handled by the multi-application resolution step below.

Workday Job Applications link a Candidate to a Job Requisition. Bullhorn JobApplications do the same but a single Candidate can have multiple JobApplications across multiple Jobs. We resolve each Workday Job Application as a separate Bullhorn JobApplication record, carrying application status, submission date, rejection reason, and referral source. Scorecards, interview ratings, and evaluation data are serialized as structured notes on the JobApplication with evaluator name and rating preserved. This resolves Workday's flat-application constraint by ensuring every historical application becomes a first-class record in Bullhorn.

Workday Scorecards are tied to Interview Kits and submitted by specific evaluators with structured rating fields. Bullhorn does not have a native structured scorecard object. We serialize evaluator name, interview date, rating scores, and comments as a formatted note on the JobApplication or Candidate, and archive original scorecard PDFs as Bullhorn attachments linked to the same record. We flag which Interview Kit templates need to be configured in Bullhorn as part of your post-migration setup.

Workday Interview Kits define interview plans and question banks and must exist in the destination tenant before submitted scorecards can be stored natively. Bullhorn has no equivalent template object. We document each Workday Interview Kit as a structured configuration note for your Bullhorn admin to recreate in Bullhorn Automation or as a custom setup guide, and serialize the existing kit content as notes and attachments on relevant JobApplications.

Workday Workers are HCM employee records created via the Revise Hire business process, distinct from Candidates. Bullhorn does not have a separate Worker object. We map Workday Workers with historical recruiting activity to Bullhorn Candidates, preserving name, employment dates, job title, department, manager, and termination date as custom fields on the Candidate record. Workers without any candidate activity are flagged for your admin to decide whether a bulk candidate import is needed.

Free-form notes attached to a Workday Candidate or Application migrate directly to Bullhorn Candidate Note records. We preserve author, timestamp, and note body where available from the Workday export. Bullhorn Note does not support rich text natively, so we strip formatting and preserve hyperlinks as plain text URLs within the note body.

Workday background check records are typically managed via third-party integrations (HireRight, Checkr) or stored as attachments to the hire. Bullhorn has no native background check object. We migrate background check data as PDF attachments on the Candidate record, or as a Bullhorn Custom Object (pre-created during schema design) if your Bullhorn edition supports it and you need structured searchable fields for compliance records.

Workday generates offer letters via business processes tied to the Requisition. Bullhorn does not have a native offer letter object. We migrate offer letter data (candidate name, job, compensation, start date, offer status, and the signed PDF if available) as attachments on the Candidate record. Offer status (accepted, declined, pending) is captured in a custom field on the Candidate.

Workday attachments (resumes, cover letters, portfolio files) are stored against Candidate or Application. We download all accessible resume and file attachments from Workday at migration time, normalize file formats, and re-upload them as native Bullhorn Candidate attachments. We flag any records where the Workday source URL is no longer accessible so you can request documents directly from candidates or retrieve them from Workday before the source system account is closed.

Workday Custom Objects extend the delivered business object graph (Worker, Position, Candidate, etc.) to capture company-specific recruiting data. Bullhorn Custom Objects extend Candidate, Contact, Company, Opportunity, Job, and Placement records and are limited by edition: ATS Growth has none, Bullhorn ATS has 2, and Front Office Growth/Enterprise supports 10 Custom Objects with 55 fields each. We pre-create Bullhorn Custom Objects during schema design, map all custom fields from Workday, and flag any Workday Custom Object that exceeds Bullhorn's field-count limit for your admin to restructure before migration.

Workday Workers carry employment history, job changes, compensation changes, and performance ratings as separate business objects. Bullhorn Placements track the active placement of a Candidate in a Job. We map the most recent Workday employment record (title, department, employment dates, manager) to Bullhorn Candidate custom fields, and full placement history to Bullhorn Placement records if your Bullhorn edition includes the Placement object. Performance ratings and compensation history are serialized as Candidate notes since Bullhorn does not have a native compensation tracking object in the ATS module.