Migrate from CVWarehouse to Bullhorn ATS & CRM

CVWarehouse Vacancies map to Bullhorn JobOrder records. Each Vacancy carries job title, location, department, employment type, and a Vacancy Template with custom fields. We map standard fields directly and flag custom template fields for explicit Bullhorn field mapping during scoping. Vacancy status (Open, Closed, On Hold) maps to JobOrder status with a customer-confirmed status routing table. We create Bullhorn JobOrder records before candidate import so that the JobOrder ID is available for the Candidate-to-JobApplication association.

CVWarehouse Candidate records map to Bullhorn Candidate entities. CVWarehouse stores candidates across separate databases per brand or location, so a single individual may appear in multiple databases. We run cross-database de-duplication using email address as the primary key before writing to Bullhorn. Where the same email appears across multiple CVWarehouse databases, we merge into a single Bullhorn Candidate record and preserve the brand-location provenance in a custom field source_brand__c. Ambiguous records (same name, different email) go to a reconciliation queue for customer review.

CVWarehouse Applications (Candidate-to-Vacancy links) map to Bullhorn JobSubmission records. Each Application tracks submission date, source channel, and application status. We map applicationDate to JobSubmission dateAdded, applicationSource to JobSubmission source, and applicationStatus to JobSubmission status. Multiple Applications for the same Candidate-to-Vacancy pair are deduplicated during mapping.

CVWarehouse Selection Rounds define interview stages, reviewer assignments, and scoring per Vacancy. Bullhorn's pipeline stage model uses configurable stage names per JobOrder pipeline. We build a routing table mapping each CVWarehouse Selection Round name to the target Bullhorn pipeline stage name during scoping, asking the customer to confirm equivalents before the migration run. Stage ordering is preserved chronologically. Custom stage names that do not map to Bullhorn defaults are created as new pipeline stage values before migration.

Interviewer scorecards and structured ratings stored per Selection Round in CVWarehouse map to Bullhorn Candidate evaluation records or structured notes. Bullhorn ATS Growth limits custom objects to 2; Bullhorn ATS and Enterprise allow up to 10 custom objects with 55 fields each. We configure the destination custom object before migration if the customer's Bullhorn edition supports it, otherwise scorecards migrate as structured Note records with a defined body template (Reviewer, Round, Score, Comments). We flag the approach during scoping.

CVWarehouse stores CVs, cover letters, and portfolio files per Candidate or Application. We export these as binary blobs and write them to Bullhorn's Candidate record via the ContentDocumentLink object. The original filename and MIME type are preserved. Bullhorn's API accepts attachments up to the org's file storage limit. We batch large binary sets to avoid timeout and resume partial uploads on failure.

CVWarehouse Vacancy Templates standardize job postings with custom fields beyond the standard vacancy schema. These require explicit field mapping during scoping because they are per-account custom fields with no standard across CVWarehouse accounts. We inventory every Vacancy Template field, map each to a Bullhorn JobOrder custom field (customText1-20, customDate1-5, etc.), and configure the Bullhorn field mappings before vacancy import. If the template field count exceeds Bullhorn's 55-field custom object limit, we prioritize the most business-critical fields and document the remainder.

CVWarehouse recruiters, hiring managers, and administrators with role-based access map to Bullhorn User records. We resolve Users by email address match against the Bullhorn destination org's User table. Role names (Recruiter, Hiring Manager, Admin) map to Bullhorn UserType and Division assignments. Users without a matching Bullhorn User go to a reconciliation queue for the customer's Bullhorn admin to provision before record import resumes. Inactive CVWarehouse users are mapped to inactive Bullhorn Users with their original owner history preserved.

CVWarehouse organizations that manage employer brands or multiple client relationships map to Bullhorn ClientCorporation records. In CVWarehouse's multi-database model, each database may represent a distinct employer brand or subsidiary; we map each to a separate ClientCorporation record and preserve the original database name in a custom field cvw_database__c for audit. Company contact records map to ClientContact entities linked to the ClientCorporation.

CVWarehouse tracks how each Application entered the system (job board, referral, direct, career site). This source attribution maps to Bullhorn JobSubmission.source. We preserve the raw source string and, where CVWarehouse uses a structured source taxonomy, map to the nearest Bullhorn source picklist value. Unknown source values are written to a custom field original_source__c to preserve the raw data for post-migration segmentation.

CVWarehouse's GDPR-compliant candidate portal stores consent flags per employer brand. We map consent status to Bullhorn Candidate.hasOptedOutOfEmail (for email opt-out) and preserve the full consent record, including consent date, consent type, and employer brand, in a custom field or structured note. Bullhorn's GDPR tooling is available on Enterprise editions; we confirm availability during scoping.

CVWarehouse reporting is UI-based with no documented analytics export API. Built-in reports do not migrate. We recommend configuring equivalent Bullhorn reports (Standard Reporting on Team and Corporate, Advanced Reporting Dashboards on Enterprise) post-migration. During scoping, we inventory the five to ten most-critical CVWarehouse reports and deliver a written guide mapping their metrics to Bullhorn report builder equivalents for the customer's Bullhorn admin to configure.