Migrate from cvviz to Recruit CRM & ATS

CVViZ Job records map to Recruit CRM Job Orders with title, description, department, and job board distribution settings preserved. CVViZ pricing tiers cap active jobs (5 to 50 depending on tier); any jobs exceeding the Recruit CRM tier limit import as archived or inactive and are flagged for manual activation post-migration. We capture job status (active, on-hold, closed) from CVViZ and map to Recruit CRM job status equivalents during the import run.

CVViZ Candidate records map 1:1 to Recruit CRM Candidates using email address as the dedupe key. Name fields, contact information, social profile URLs, employment history, and custom Candidate fields transfer directly. We flag any Candidates with duplicate email addresses in the source for the customer to resolve before the final import to avoid unintended merges in Recruit CRM.

CVViZ Application records link a Candidate to a Job with a current pipeline stage and timestamp. We preserve the application date, last-modified date, and stage history as a snapshot on the Recruit CRM Application. The Candidate-to-Job lookup resolves at migration time using email-based Candidate resolution and job title matching against the pre-imported Job Order set.

CVViZ pipeline stages are fully customizable per organization, with no universal stage schema. We capture the complete stage name map during the pre-migration schema review, then apply a named mapping to the Recruit CRM pipeline stages, which are configured per Job Order. Any CVViZ stages with no Recruit CRM equivalent are flagged as unmapped and held for manual configuration before the final import run.

CVViZ stores resumes as parsed structured data alongside raw PDF or DOCX files. Resume files must be handled as binary attachments rather than simple field values. We extract the raw file, map the Candidate-to-Resume linkage via the application ID, and upload as a file attachment to the Recruit CRM Candidate record. If Recruit CRM's resume parser is enabled, the file re-parses on ingest; if disabled, candidates land with the raw file unparsed.

CVViZ maintains a Talent Pool of passive candidates not tied to a specific job requisition. We migrate these as Recruit CRM Candidates with a Passive or Inactive lifecycle stage tag and preserve the original source attribution field so that the customer can segment passive talent separately in Recruit CRM's candidate database. Multiple CVViZ talent pool entries for the same email address merge to a single Candidate record.

CVViZ AI ranking scores are calculated from its own NLP model against the job description and historical hiring data. We carry the score value as a custom numeric field on the Recruit CRM Candidate record. Recruit CRM will not recalculate or update this value; it functions as a static snapshot. We recommend documenting the scores as a reference baseline and setting expectations that Recruit CRM's own AI matching will generate new scores over time.

CVViZ stores job-specific pre-screening questions and candidate responses as key-value pairs on the Application record. We map these to equivalent custom fields on the Recruit CRM Job or Application record. Fields with no direct equivalent in Recruit CRM's standard schema are flagged as unmapped for manual configuration. The customer defines the data type (text, number, picklist, date) for each unmapped field during scoping.

CVViZ Users with role-based access control map to Recruit CRM Users. We resolve by email match. Role and permission mapping is documented in a written inventory because Recruit CRM's role model differs from CVViZ's permission set. Users without a matching Recruit CRM account are held in a reconciliation queue for the customer's admin to provision before record import resumes.

CVViZ custom fields on Job records map to custom fields on Recruit CRM Job Orders. We migrate the field name, data type, and values as structured data. The destination must have identically named fields or manually mapped equivalents to receive values without data loss. We flag any custom fields without a matching Recruit CRM field for manual schema configuration before the import run.

CVViZ custom fields on Candidate records map to custom fields on Recruit CRM Candidates. Multi-select picklists, date fields, numeric fields, and text fields transfer directly. Long-text or rich-text fields are mapped as textarea fields and may require truncation if character limits differ. We flag any custom field data types without a direct Recruit CRM equivalent for the customer to configure manually.

CVViZ distributes job postings to LinkedIn, Google for Jobs, and other major job boards natively. We migrate the job posting configuration as metadata on the Recruit CRM Job Order record. The actual posting must be re-published in Recruit CRM because distribution tokens and API connections do not transfer between platforms. We flag the re-publish step as a post-migration admin task.