Migrate from WebCruiter to Bullhorn ATS & CRM

WebCruiter Candidate records map to Bullhorn Candidate. Standard fields (firstName, lastName, email, phone, address) map directly. We flag records where contact information was entered manually versus auto-populated from a job board application because the data quality differs. We preserve candidate source attribution where it exists in the record and map it to Bullhorn's source taxonomy. Any WebCruiter owner or recruiter assignment is resolved against the Bullhorn User table by email match; unresolved owners go to a reconciliation queue.

WebCruiter Job Postings export with title, department, location, and status. Status values (active, paused, closed) map to Bullhorn JobOrder status (Open, Paused, Closed/Dead). We preserve the original posting date and any internal requisition ID present in the export. Archived job requisitions are separated from active jobs during scoping; we recommend mapping archived pipelines to a dedicated legacy-job pipeline in Bullhorn to avoid active pipeline contamination.

WebCruiter Applications link a Candidate to a Job Posting with a status (applied, in review, rejected, hired). We map these to Bullhorn JobSubmission records, preserving the application date and any stage history exported. We flag records where stage history is incomplete or truncated in the WebCruiter export. The JobSubmission is created after both the Candidate and JobOrder exist in Bullhorn to satisfy the foreign-key dependency.

WebCruiter allows recruiters to add custom screening questions to application forms. These fields export as free-form text regardless of intended type (date, integer, multi-select). We profile each custom field in the staging environment, apply type inference, and map to the appropriate Bullhorn field type. If the intended type is a structured picklist or integer and type inference is ambiguous, we flag the field for customer review before load. Bullhorn edition constraints apply: ATS Growth supports 0 custom objects, Bullhorn ATS supports 2, and Enterprise supports 10 with 55 fields each.

WebCruiter uses configurable pipeline stages per job requisition. Stage names vary by organisation. We extract the full stage set from each exported job and map them to Bullhorn JobOrder status values (Open, Interview, Offer, etc.) or Opportunity Stage if the staffing workflow includes placement tracking. We document the original stage name in a custom field stageNameOriginal__c for audit and reconciliation.

Source tracks where an application originated (job board, referral, direct). This field is often blank in legacy WebCruiter records or populated inconsistently. We map source values to the Bullhorn Candidate source taxonomy and flag any unmapped source values for customer review. Where source is blank, we leave the field null rather than inferring a value.

Recruiters and hiring managers are assigned as owners to jobs and candidates in WebCruiter. The standard data export may not include a full user directory. We extract every distinct owner ID referenced on Candidate, Job, and Application records and match by email against the Bullhorn User table. Any owner without a matching Bullhorn User is held in a reconciliation queue for the customer's admin to provision the corresponding User record before record import resumes.

WebCruiter stores CVs, cover letters, and portfolio files attached to candidate records. The standard data export does not bundle these files; files must be retrieved individually from the WebCruiter UI or requested as a separate archive from Talentech support. We count the total attachment volume per candidate during extraction, request the file bundle from the customer before the load phase, validate attachment filenames against exported record IDs, and then associate each file to the Bullhorn Candidate record via ContentDocumentLink. Bullhorn accepts PDF, DOC, DOCX, and standard image formats. Files without a resolvable candidate match are logged as orphaned and presented to the customer for manual resolution.

WebCruiter organisations using the platform for staffing workflows may have client company records alongside candidate records. These map to Bullhorn ClientCorporation. The organisation name, address, and primary contact fields transfer directly. We use ClientCorporation name as the deduplication key during import. If no client companies exist in the WebCruiter export, this object is skipped.

Recruiter notes attached to candidates or job postings in WebCruiter migrate to Bullhorn Note records linked via ContentDocumentLink to the parent Candidate or JobOrder. We preserve the note body, author (resolved to Bullhorn User by email), and creation timestamp. Rich-text formatting in WebCruiter notes is simplified to plain text to avoid display inconsistencies in Bullhorn.

If the WebCruiter data export includes placement or hiring-outcome records, these map to Bullhorn Placement. Placement maps Candidate and JobOrder to a staffing transaction with start date, end date (for contract), pay rate, bill rate, and assignment status. Bullhorn's Placement object is part of the staffing workflow and requires both Candidate and JobOrder to exist before the Placement record is inserted.

WebCruiter archived jobs retain their original pipeline stage set and may conflict with the active pipeline schema in Bullhorn. We separate archived jobs from active jobs during scoping, recommend mapping them to a dedicated legacy-jobs pipeline in Bullhorn, and exclude them from the primary migration load unless the customer explicitly requests inclusion. Each archived job's candidates move with the job assignment but are flagged as belonging to a closed requisition.