Migrate from CVWarehouse to BambooHR

CVWarehouse Vacancies map to BambooHR Jobs. Each Vacancy's job title, location, department, employment type, and description map to BambooHR's corresponding job fields. We flag any custom Vacancy Template fields for explicit mapping since they are not standard across CVWarehouse accounts and may require a custom field to be created in BambooHR before migration. BambooHR enforces active job opening limits by plan tier (Essentials 5, Pro 25, Advantage 50), so we verify the customer's tier against their vacancy count and flag any customer exceeding their tier limit before migration begins.

CVWarehouse Selection Rounds define interview pipeline stages using arbitrary names set per Vacancy, with no enforced taxonomy. BambooHR uses a fixed set of Application Status values: Applied, Phone Screen, Interview, Offer, Hired, and Rejected. We build a routing table mapping each CVWarehouse Selection Round name to the nearest BambooHR status during scoping, confirm it with the customer, and apply it across all vacancies during migration. Any non-standard stage names that cannot map cleanly are preserved as notes on the candidate record for manual follow-up.

CVWarehouse Candidates map directly to BambooHR Candidates, with CVWarehouse contact fields (first name, last name, email, phone, LinkedIn, address) mapping to BambooHR's standard candidate fields. CVWarehouse Candidates are stored across separate databases per brand or location, so we deduplicate across these pools using email address as the primary key before writing to BambooHR. We flag ambiguous records (same email, conflicting names or data) for customer review and add a custom source_database__c field to track which CVWarehouse database the record originated from.

Each CVWarehouse Application links a Candidate to a Vacancy and tracks submission date, source channel, and application status. We map Applications to BambooHR's Job Applications with the Candidate and Job lookups resolved at migration time. The application submission date and source channel (referral, job board, direct) migrate to BambooHR's created_at and source fields. If a Candidate was rejected at a specific Selection Round in CVWarehouse, we write the Application with the rejected status and a note referencing the round name.

CVWarehouse stores structured interviewer scorecards and ratings per Selection Round. BambooHR does not have a native structured scorecard or evaluation object in its ATS, so we map scorecard data to a formatted Note attached to the candidate record in BambooHR. The Note captures interviewer name, round name, rating value (where applicable), and free-text feedback. If the customer uses structured numerical ratings, we create a custom BambooHR field (customFieldType=short_text or number depending on the scale) and flag it as a setup dependency before migration.

CVWarehouse stores CVs, cover letters, portfolio files, and other documents per Candidate or Application. We export these as binary files and write them to BambooHR's file attachment area on the corresponding Candidate record. BambooHR organizes files into categories (Resume, Cover Letter, Portfolio, Other) that we map based on the file extension and original CVWarehouse file label. We flag any files without a recognizable type for manual categorization post-migration. BambooHR's Advantage plan includes more file storage than Essentials; we verify storage allocation against the customer's attachment volume before migration.

CVWarehouse Users (recruiters, hiring managers, administrators) with role-based access map to BambooHR Employee records. We map the recruiter and hiring manager roles to BambooHR's employee department and job title fields, and flag any role names that do not have a direct equivalent in BambooHR's permission model. Active CVWarehouse users with candidates or vacancies assigned to them require a matching BambooHR Employee record with an email match before migration can resolve owner assignments on candidate and job records.

Organizations using CVWarehouse Vacancy Templates have custom or shared template fields applied across multiple vacancies. These require explicit mapping during scoping because they vary per account and are not part of the standard CVWarehouse schema. We identify every distinct Vacancy Template field used across the account, map it to a BambooHR Job custom field or a job description section, and create the corresponding custom field in BambooHR before migration. Vacancy Templates themselves (as reusable template objects) do not have a direct BambooHR equivalent; we deliver a template mapping document listing which fields map to which BambooHR Job fields for manual recreation if needed.

CVWarehouse's separate talent databases per brand or location create a migration challenge where a single logical candidate may appear in multiple databases under different records. We merge these records into a single BambooHR Candidate using email as the dedupe key and append a source_database__c field listing all originating databases. The customer reviews ambiguous cases during the deduplication review phase before final import. This N:1 merge is a manual review gate that adds scope and time to multi-database migrations, which we account for in the timeline and price estimate during discovery.

CVWarehouse built-in reports are UI-based and do not expose a documented analytics export API, so reports cannot migrate programmatically. We do not attempt to migrate CVWarehouse reports. Instead, during scoping we document the key reports the customer relies on (time-to-hire, source effectiveness, vacancy funnel, selection round throughput) and recommend equivalent configurations in BambooHR's Standard and Custom Reports. BambooHR's reporting covers employee data, hiring funnel, and EEO aggregate data; the customer's HR admin rebuilds the specific report views post-migration using BambooHR's report builder.