Migrate from Webrecruit to Bullhorn ATS & CRM

Webrecruit Candidate records map directly to Bullhorn Candidate. Contact details, application history, stage progression, and GDPR consent flags transfer as standard fields or custom fields. Webrecruit consent timestamp and boolean flag require Bullhorn Support configuration of a custom Candidate field; we export these as separate columns and create the destination field via Support ticket during schema setup. Candidates with withdrawn or expired consent are flagged during scoping and migrated as suppressed records per the customer's GDPR policy.

Webrecruit Job records map to Bullhorn JobOrder. Title, description, department, location, status, and posting dates transfer directly. JobOrder's title field is limited to 200 characters; we truncate with an ellipsis and store the full title in a custom field if truncation occurs. Inactive or archived Webrecruit jobs are migrated with status reflecting their source state and flagged for the customer to review post-migration.

Each Webrecruit Application links a Candidate to a Job with a timestamp and current stage. We map to Bullhorn JobSubmission with the CandidateId and JobOrderId resolved at migration time, submission date preserved, and current status reflecting Webrecruit's rejection, withdrawal, or active stage. Application history including rejection dates and withdrawal timestamps transfers as part of the JobSubmission record.

Webrecruit uses a fixed set of pipeline stages. Bullhorn pipeline stages are configurable per JobOrder record type. We map each Webrecruit stage to the closest Bullhorn stage name and probability, flagging any that cannot be represented in Bullhorn's stage model. Webrecruit stages that have no Bullhorn equivalent (such as bespoke assessment stages) are migrated as notes on the Candidate record rather than as pipeline transitions.

Webrecruit Hiring Managers are assigned to jobs and can leave feedback. Bullhorn has separate User (internal staff) and ClientContact (external hiring manager) entities. We map Webrecruit Hiring Managers with an email domain match: if the email domain matches the organization's domain, we map to a Bullhorn User record; otherwise, we map to ClientContact linked to the relevant ClientCorporation. Assignment of Hiring Manager to Job migrates as a User or ClientContact assignment on the JobOrder.

Webrecruit approval workflows define job requisition steps from creation to posting. Bullhorn does not store approval workflows as a code object that migrates. We export workflow step definitions as a written configuration inventory document listing each step, its conditions, and its actions. The customer's Bullhorn admin uses this inventory to rebuild equivalent workflows using Bullhorn's Task assignment and approval routing features post-migration.

CVs, cover letters, and attachments stored per Webrecruit application migrate as Bullhorn ContentDocument records linked via ContentDocumentLink to the corresponding Candidate or JobSubmission record. Document file names and MIME types are preserved. Binary blobs are extracted from Webrecruit's export and re-attached to the Bullhorn record at migration time. Files exceeding Bullhorn's attachment size limits are flagged for alternative handling.

Webrecruit custom fields vary by account. We export field definitions and all values during discovery. Bullhorn custom fields are created via Admin > Field Mappings by Bullhorn Support or the customer's admin. We provide a field creation checklist mapping each Webrecruit custom field to its Bullhorn equivalent, including field type, required status, and picklist values. Custom fields that exceed Bullhorn's field type options are flagged for manual re-entry or alternative handling.

Webrecruit User accounts include name, email, role, and permissions. We export user records and provision corresponding Bullhorn User accounts by email match. Bullhorn User provisioning requires the customer's Bullhorn admin to create accounts through the Admin menu; we provide a user import template with all sourced fields pre-populated. Users without an email match in Bullhorn go to a reconciliation queue for manual provisioning before record migration begins.

Webrecruit stores employer companies within its job context. Bullhorn uses ClientCorporation for agency client companies and ClientContact for individual hiring managers. We map Webrecruit company records to Bullhorn ClientCorporation, preserving company name, address, and any associated notes. If the customer's Webrecruit instance stores candidate-employer affiliations separately, those map as text on the Candidate record or as a custom field.

Webrecruit does not natively support aptitude tests or competency assessments as pipeline stages. Reviewers note these are tracked outside the system or not at all. We migrate any assessment results exported from Webrecruit as Bullhorn Note records or ContentDocument attachments on the Candidate record. We flag this during scoping and ask the customer to confirm whether assessment data exists in a separate system or spreadsheet. Bullhorn custom objects (Growth/Enterprise) can also be configured to store structured assessment results if the customer requires a searchable home for this data.

Webrecruit stores candidate GDPR consent as a boolean flag with a timestamp. UK law requires this status to be honored in the destination system. We export consent timestamp and boolean alongside each Candidate record and create a custom Candidate field in Bullhorn via Bullhorn Support ticket. Candidates with withdrawn or expired consent are flagged but not migrated unless the customer explicitly requests suppression overrides. Post-migration, the customer's Bullhorn admin uses this custom field to enforce suppression lists and honor withdrawal requests.