Migrate from Whitecarrot.io to Bullhorn ATS & CRM

Whitecarrot.io Job records (title, description, requirements, status, and job board posting configuration) map to Bullhorn JobOrder. The Bullhorn JobOrder is the parent entity for all candidate submissions. We flag the Recruiter Pro 5-job cap during scoping so the customer can upgrade or archive before migration begins. JobOrder IsDeleted, IsHot, and startDate migrate as standard Bullhorn fields.

Whitecarrot.io Candidate profiles map directly to Bullhorn Candidate. Contact information (name, email, phone, address), candidate status, and source attribution migrate as standard Candidate fields. The Whitecarrot candidate application history maps to Bullhorn JobSubmission records created during the candidate-job association phase.

Whitecarrot.io screening question sets attached to jobs migrate as Bullhorn custom fields on the Candidate or JobOrder entity depending on whether the question applies per job or per candidate. We pre-create the custom field definitions in Bullhorn via the Field Mappings admin section before migration and validate edit types (text, drop-down, checkbox) against Bullhorn's supported custom field options. Conditional routing logic from Whitecarrot does not transfer; we document the conditional rules for the Bullhorn admin to recreate using Bullhorn's workflow or Bullhorn Automation.

Whitecarrot.io skill-based test configurations and candidate completion statuses map to Bullhorn custom fields on the Candidate record. Test name, pass/fail status, numeric score, and test completion timestamp migrate as separate custom fields. Bullhorn's custom field limit per entity (55 fields) applies; we audit the field count during scoping and consolidate test scores into a structured custom object if the candidate entity exceeds the limit.

Whitecarrot.io one-way video interview recordings and metadata (submission timestamp, duration, view count) require a migration strategy decision during scoping. If Bullhorn has Bullhorn Onboarding (formerly Able) enabled, video links or metadata can attach to the Candidate record. Otherwise, video interview metadata migrates as Bullhorn custom fields (text for the access URL, date for submission timestamp) and the recording URLs are preserved as-is. Bullhorn does not natively host video files; the customer should confirm their video storage strategy before migration.

Whitecarrot.io coding challenge configurations and candidate submissions (code, automated scoring results, rubric alignment) map to Bullhorn custom fields on the Candidate record. We map scoring rubrics to Bullhorn custom number or picklist fields and preserve the challenge title as a reference. Automated scoring status (pass/fail/running) migrates as a custom picklist field.

Whitecarrot.io interview scorecard templates, interviewer responses, and aggregate ratings require Bullhorn edition verification during scoping. Bullhorn's native scorecard functionality is available on Front Office Growth/Enterprise editions. For Bullhorn ATS or ATS Growth editions, scorecard data migrates to a custom object (with Bullhorn Support request for custom object provisioning) or as custom fields on the Candidate record. Multi-interviewer scorecard attribution migrates with interviewer name as a custom field or as separate custom object records.

Whitecarrot.io Offer records (compensation details, e-signature status, approval flow state) map to Bullhorn Placement records with offer-specific data in Bullhorn custom fields on the Placement entity. Bullhorn Placement is the canonical record for a hired candidate and includes start date, pay rate, and bill rate. We map Whitecarrot's offer compensation structure to Bullhorn Placement custom fields. Any e-signature status flags require re-triggering in Bullhorn because e-signature integrations (DocuSign, HelloSign) are destination-platform-bound.

Whitecarrot.io psychometric test configurations and candidate results migrate to Bullhorn custom fields on the Candidate record. Test vendor integration details (API keys, test session IDs) do not transfer because they are tied to Whitecarrot's own integration account. We document the vendor name and test type for the customer to re-authenticate in their psychometric test platform and re-link if supported.

Whitecarrot.io User accounts and role assignments (Recruiter, Hiring Manager, Interviewer) map to Bullhorn User records. We match by email address. Role name strings map to Bullhorn UserType and department assignments. Whitecarrot's permission sets require translation to Bullhorn's user role hierarchy and field-level security configuration in Bullhorn Admin.

Whitecarrot.io Career Site Builder page configurations and branding settings export as structured JSON or configuration records. Bullhorn does not have a native career site builder in all editions; Bullhorn Career Portal is a separate product. We export the Whitecarrot career site configuration as a JSON package and provide a written reconstruction guide so the Bullhorn admin can rebuild the site in Bullhorn Career Portal, Bullhorn-provided CMS, or a third-party careers page integration.

Whitecarrot.io job board posting configurations (which boards, which jobs, posting history) migrate as structured reference records in our migration manifest. Active posting URLs and authenticated job board credentials (LinkedIn, Indeed, niche boards) are tied to Whitecarrot's own integration account and do not transfer. The customer must re-authenticate each job board integration in Bullhorn. We provide a job board inventory checklist from the migration export to guide re-authentication.

Whitecarrot.io report definitions and historical analytics data export as static data snapshots (CSV or structured records). Bullhorn's reporting engine has a different schema and calculation model. We deliver the analytics data as exported CSV files mapped to Bullhorn's standard report fields where possible, and document any metrics that require manual re-creation in Bullhorn reporting.