Migrate from cvviz to Crelate

CVViZ Job records map to Crelate Job records with title, description, department, and job board distribution settings preserved. Active job status maps directly unless the job exceeds the target Crelate subscription tier's concurrent limit, in which case the job migrates as Inactive with a flag for post-migration activation. We preserve job posting metadata but note that the posting must be republished on the destination platform because job board distribution settings are platform-specific API connections that do not transfer.

CVViZ Candidate records map to Crelate Contact records, which is the Core Record that stores candidate data. Name, email address, phone, social profiles (LinkedIn, GitHub, Stack Overflow URLs), employment history, and source attribution map to standard Crelate Contact fields. Crelate's Logical Name API field naming convention is applied during import; we preserve the original CVViZ field names in custom documentation for the admin's reference during rebuild.

CVViZ Application records link a Candidate to a Job with a pipeline stage and timestamp. We map Applications to Crelate's Job Submission feature or, where the workflow requires pipeline tracking against a business entity, to the Opportunity Core Record. The stage assignment maps through the pre-migration stage name mapping, and the Application timestamp preserves the candidate journey timeline. If Crelate's Opportunity object is used for tracking, the Opportunity AccountId points to the relevant Client Company in Crelate.

CVViZ stores parsed resume data alongside the raw PDF/DOCX file as a binary attachment. We extract the raw file and attach it to the corresponding Crelate Contact record as a file attachment. The parsed structured fields (work experience entries, education, skills) migrate to Crelate custom fields on the Contact record or to a Crelate Notes section as structured text. Crelate does not perform AI resume parsing on ingest, so the parsed NLP fields from CVViZ are stored as a snapshot in text fields rather than as recalculable structured data.

CVViZ pipeline stages are fully customizable per organization with no universal stage schema. We capture the complete CVViZ stage map (names, order, and any conditional routing) during the pre-migration schema review, then apply a named mapping to Crelate's pipeline configuration. Stages with no Crelate equivalent are flagged as requiring manual configuration before the final import run. The mapping document becomes the stage configuration guide for the customer's Crelate admin.

CVViZ's Talent Pool maintains passive candidates not tied to a specific active job requisition. We migrate Talent Pool entries as Crelate Contacts with a Passive or Talent Pool lifecycle tag. Source attribution (where the candidate was originally sourced from) preserves as a custom field on the Contact. Candidates that appear in both the Talent Pool and active Applications are deduplicated at the Contact level during migration.

CVViZ's AI-generated candidate scores are proprietary to its NLP model and calculated against the job description and historical hiring decisions. We carry the numeric score value as a custom field on the Crelate Contact record as a migration-time snapshot. Crelate will not recalculate or update this score because it has no equivalent proprietary algorithm. We recommend documenting the scores as a time-stamped snapshot and setting expectations that ranking will re-normalize over time as Crelate's own AI features (if enabled) begin processing hiring patterns.

CVViZ stores job-specific pre-screening questions and candidate responses as key-value pairs on the Application record. We map these to Crelate custom fields on the Job record or the Application (Job Submission) record. If Crelate does not have a matching field type, we flag the response as unstructured text in a Crelate Notes field. The customer chooses the preferred target during scoping.

CVViZ custom field names, data types, and values migrate to Crelate custom fields on the equivalent Core Record (Job or Contact). Crelate requires pre-creation of custom fields in the Settings area under Core Records before import; we coordinate this during schema setup so that fields exist in Crelate with matching Logical Names before the data import run. Custom fields that do not have a Crelate equivalent are flagged for manual configuration before migration.

CVViZ users with role-based access control map to Crelate users. We extract user name and email and match by email against the Crelate destination tenant. Role permissions are documented as a written inventory for the customer's Crelate admin to reconfigure in Crelate's permissions model, since role structures are platform-specific and do not transfer directly. Active and inactive user status is preserved in the inventory.

CVViZ automation rules for email triggers, notifications, and stage transitions are platform-specific and do not map cleanly to Crelate's workflow model. We document the rule logic (trigger condition, actions, delays, and recipients) as a written inventory for the customer's admin to rebuild in Crelate. Automation rebuild is outside the migration scope and is a separate configuration engagement.

CVViZ job board distribution settings (LinkedIn, Google for Jobs, and other job boards) are stored as platform API connections that do not transfer. We document the distribution configuration as metadata for each Job so that the customer can re-establish the postings in Crelate. Job descriptions and requirements are fully migrated; only the posting delivery channel requires manual reconfiguration.