Migrate from CVWarehouse to Crelate

CVWarehouse Vacancies include job details, location, department, and Vacancy Template fields. We map these to Crelate Job records, preserving job title, location, department, and job description. Any custom Vacancy Template fields that are not standard Crelate Job fields are migrated as Crelate custom fields on the Job object. The Vacancy status (open, paused, closed) maps to Crelate Job status. Vacancy Templates require explicit field mapping during scoping because they vary across accounts.

CVWarehouse Candidates stored across separate databases per brand or location are de-duplicated using email address as the primary key. Candidates with matching email addresses across databases are merged into a single Crelate Contact record, with Tags applied to indicate the source brand or location. Candidates with no email or ambiguous email addresses are flagged for customer review before writing. Contact profile fields (name, phone, address, work history, education, free-form notes) map to the corresponding Crelate Contact fields or custom fields.

Each CVWarehouse Application links a Candidate to a Vacancy and tracks submission date and source channel. We map Applications to Crelate's Job application records, preserving the application date and source attribution. Source channel (LinkedIn, referral, job board, direct) migrates as a custom field on the application record. We resolve the Contact reference (from Candidate de-duplication) and the Job reference (from Vacancy mapping) before writing each application record.

CVWarehouse Selection Rounds define interview stages with arbitrary names per Vacancy rather than enforcing a standard taxonomy. We build a routing table of existing stage names during scoping and confirm target Crelate pipeline stage equivalents with the customer before the migration run begins. Stage sequence order is preserved chronologically so the Crelate pipeline reflects the original hiring pipeline logic. Scorecards attached to Selection Rounds migrate as Crelate Activity Form responses linked to the application record.

Interviewer scorecards and structured ratings stored per Selection Round map to Crelate Activity Form responses. We identify whether Crelate supports structured scoring for the customer's plan tier and note any differences. If the destination supports rating fields, structured ratings migrate to those fields; otherwise, ratings are preserved as text in the Activity Form response body with the score value captured in a numeric custom field for reporting purposes.

CVWarehouse stores CVs, cover letters, and portfolio files as binary blobs per Candidate or Application. We export these as files and upload them to Crelate's document attachment fields, preserving original filenames and file types. The attachment links to the relevant Contact or Job Application record. Resume parsing (available on Crelate Business and above) can extract structured fields from uploaded CVs post-migration; we note this as a post-migration configuration step rather than part of the migration run.

CVWarehouse tracks application source channels (LinkedIn, referral, job board, direct, agency). Source attribution migrates as a Tag on the Crelate Contact or Job Application record. The customer chooses whether to use a single Source tag category or split into multiple tag categories during scoping. If the customer requires source reporting in Crelate's analytics, we configure a custom source field on the Job Application record in addition to Tag assignment.

CVWarehouse recruiters, hiring managers, and administrators have role-based access. We map CVWarehouse Users to Crelate User records by email match. Any CVWarehouse User without a matching Crelate User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Role names from CVWarehouse that do not have a direct Crelate equivalent are noted in the handoff document with a recommended Crelate role assignment.

Organizations using CVWarehouse Vacancy Templates have custom or shared fields that are not standard across accounts. These require explicit mapping during scoping. We identify every distinct Vacancy Template field, determine the appropriate Crelate field type (text, number, picklist, date, etc.), and pre-create the custom fields in Crelate before Job import begins. Template assignment (which template was used for which Vacancy) is preserved as a Tag or custom field on the Job record.

CVWarehouse stores employer brand information and company profiles for multi-brand organizations. These map to Crelate Company records, with the company name, website, industry, and size migrating to the corresponding Crelate Company fields. Company records are created before Contact import so that the lookup relationship is satisfied at the moment of Contact insert.

CVWarehouse reporting is UI-based and does not expose a documented analytics export API. Built-in reports do not migrate. We recommend configuring equivalent reports in Crelate's Advanced Reports and Analytics (available on Business tier and above) post-migration using the migrated data as the source. We deliver a written summary of the key metrics tracked in CVWarehouse reports (pipeline stage counts, time-to-hire, source conversion rates) with recommended Crelate report configurations.

CVWarehouse Selection Process features (pipeline routing rules) and any configured automations do not migrate. Crelate's Automation and Sequencing is available on the Business Plus tier and represents a different configuration model. We deliver a written inventory of every active CVWarehouse Selection Process with its routing logic, stage triggers, and recommended Crelate Automation equivalent. The customer's admin rebuilds these in Crelate post-migration.