Migrate from VidCruiter to Crelate

VidCruiter Candidate records map to Crelate Person records. We extract full contact details, application history, pipeline status, profile fields, and tags. Email address and phone number serve as the dedupe key during import. Any VidCruiter custom candidate fields map to Crelate custom fields on the Person record. Video interview response URLs, assessment scores, and rating metadata attach as linked notes or custom fields on the Person.

VidCruiter Requisitions map to Crelate Jobs. We extract all posting content, pipeline stage configurations, and hiring team assignments. Job status (Draft, Active, Closed, On Hold) maps to Crelate's job status field. The job description and requirements migrate as structured fields on the Job record. VidCruiter's per-requisition stages are extracted separately and normalized into Crelate's stage model before job import.

Pre-recorded and live video interviews are hosted media assets in VidCruiter. We download each video file via the API or signed URL, preserving the original filename and format. The downloaded file is attached as a File or Document record on the migrated Candidate Person record in Crelate, with the interview metadata (question asked, duration, submission timestamp) stored in a custom field or linked note for reference. Storage and re-hosting costs should be factored in, especially for organizations with large video libraries.

VidCruiter allows each requisition to have a different set of pipeline stages, unlike Crelate's shared stage taxonomy. We extract the full stage map per job during scoping, identify which stages are semantically unique versus duplicative across requisitions, and normalize them into Crelate's stage model. Stages that cannot map directly are flagged for customer review and collapsed or renamed to match Crelate's available stage slots. Active pipelines with unique stage sets require coordinated timing to avoid mid-process disruptions.

VidCruiter custom interview question sets and AI-generated interview guides are templates. We migrate them as structured question lists attached to the Job as Crelate Activity Forms with Field Mappings configured. The structured nature of VidCruiter's scorecard questions maps to Crelate's form field definitions. Note that Crelate Activity Forms support field-to-field mapping to Person or Job records, but the scoring logic requires manual rebuild in Crelate's evaluation workflow.

VidCruiter scorecard evaluations submitted by interviewers contain structured ratings and free-text feedback per question or overall. We map these to Crelate Note records linked to the Person record, preserving reviewer name, submission date, and individual question ratings as structured content. Numeric summary scores and overall ratings migrate to custom fields on the Person record for reporting queries. Raw scorecard templates migrate as standalone Activity Forms for reference by Crelate admins.

Skills test results and automated scoring stored per candidate per job in VidCruiter are extracted as numeric scores and pass/fail thresholds. We map these to custom fields on the Crelate Person record with appropriate field types (number, boolean, picklist). Assessment name and test date migrate alongside the score. The raw assessment content (questions, answer keys) does not migrate as these are VidCruiter-hosted evaluation tools with no direct Crelate equivalent.

Reference check data lives in VidCruiter's separate reference checking sub-module. We extract reference responses, reference provider details (name, relationship, contact), and verification status as structured fields. These attach as custom record entries or detailed Notes on the Person record in Crelate. If the customer uses Crelate's activity logging, reference check status may be tracked as a custom activity type.

VidCruiter user accounts with role assignments (Admin, Recruiter, Hiring Manager) map to Crelate User records. Role names differ between platforms; we map VidCruiter roles to the closest Crelate role equivalents and flag any access discrepancies for the customer's admin to review. Users must be provisioned in Crelate before record migration begins because OwnerId references are required on most record imports.

VidCruiter requisition-level hiring team assignments (interviewers, approvers, sourcers) map to Crelate User assignments on the Job or Person record. We extract assignment roles and match VidCruiter users to Crelate users by email during the lookup resolution phase. Any VidCruiter user without a matching Crelate user goes to a reconciliation queue for the customer to provision.

Tags applied to candidates or jobs for segmentation and workflow routing in VidCruiter migrate as flat tag fields on the corresponding Crelate record. Crelate's tag model is a flat taxonomy; if VidCruiter tags carry hierarchical or multi-value semantics, we flatten them and note the loss of hierarchy for the customer's awareness.

Candidate-attached documents including resumes, cover letters, portfolio files, and other supporting materials migrate as Files linked to the Person record in Crelate. We preserve original filenames, file types, and attachment dates. The file binary transfers alongside metadata so that recruiters can open attachments in Crelate without additional retrieval steps.