Migrate from CVWarehouse to Recruit CRM & ATS

CVWarehouse Vacancies map to Recruit CRM Jobs. Job title, location, department, employment type, and description fields transfer directly. Custom Vacancy Template fields (shared or account-level) map to Recruit CRM associated custom fields via field_id lookup after we retrieve the destination field structure during scoping. We flag any Vacancy with missing required Recruit CRM fields and route them to a reconciliation queue before migration begins.

CVWarehouse Candidates map to Recruit CRM Candidates with contact info, work history, education, and free-form notes transferred to the equivalent Candidate profile fields. CVWarehouse stores candidates across separate databases per brand or location, so we run cross-database de-duplication using email address as the primary key before writing. The most complete profile (most fields populated) wins for each unique email address, and duplicates are flagged for customer review.

A CVWarehouse Application links a Candidate to a Vacancy and tracks submission date and source channel. We map this to Recruit CRM's candidate-job association, preserving the application source (referral, job board, direct) as a custom field. The Application status (applied, screened, interviewed, rejected, offer, hired) maps to the corresponding Recruit CRM application status value.

CVWarehouse Selection Rounds define interview stages with reviewer assignments and configurable stage names per Vacancy. Each Selection Round becomes a Recruit CRM pipeline stage entry against the candidate's application record. We build a routing table of all existing CVWarehouse stage names and ask the customer to confirm the equivalent Recruit CRM stage during scoping. Stages without a confirmed mapping go to a customer-review queue.

Interviewer scorecards and structured ratings stored per Selection Round map to Recruit CRM's evaluation or rating object. We map score values, reviewer name, and feedback comments to the equivalent fields. If Recruit CRM does not support structured scoring for the customer's tier, we store the scorecard data as a custom Note attached to the candidate record with a standardized prefix for identification.

CVWarehouse stores CVs, cover letters, and portfolio files per Candidate or Application. We export these as binary blobs and write them to Recruit CRM's document attachment field, preserving the original file name and MIME type. File size and count are logged during scoping; files exceeding Recruit CRM's attachment size limit are flagged for the customer to decide whether to link via external URL instead.

Organizations using CVWarehouse Vacancy Templates have custom or shared fields that vary per account. These require explicit field mapping during scoping because they are not standard across accounts. We retrieve the full Vacancy Template field list from the source data dump, map each to a Recruit CRM associated custom field or standard Job field, and configure the destination field schema before migration. Any template field with no Recruit CRM equivalent is noted for customer decision.

CVWarehouse recruiters, hiring managers, and administrators with role-based access map to Recruit CRM Users. We match by email address and map role names to the closest Recruit CRM permission equivalent. Users without a matching email in the destination are held in a reconciliation queue for the customer to provision before record import resumes.

CVWarehouse stores company records associated with Vacancies or as stand-alone records. These map to Recruit CRM Clients with company name, industry, website, and address transferred. Client records are created before candidate records that reference them so that the Client-Candidate association is satisfied at insert time.

CVWarehouse reporting is UI-based and does not expose a documented analytics export API. We do not migrate built-in reports. We deliver a written inventory of CVWarehouse report names, filters, and scheduled recipients for the customer's admin to configure equivalent reports in Recruit CRM post-migration.

CVWarehouse workflows, automation rules, and email sequences do not have documented migration paths to Recruit CRM's automation model. We do not migrate them as code. We deliver a written inventory of every active CVWarehouse workflow with its trigger, conditions, and actions, plus a recommended Recruit CRM automation equivalent. The customer's admin rebuilds them post-migration.