Migrate from Dover to Crelate

Dover Candidate records map to Crelate's Person object, which functions as a unified contact and candidate record. We extract name, email, phone, current stage, source, and application date from the Dover CSV and map each to the corresponding Crelate Person field. Stage history (Applied, Screening, Interview, Offer, Hired, Rejected) migrates as Crelate activity timeline entries with timestamps preserved. We flag any Dover custom candidate fields (sourced from Premium AI scoring or manual recruiter notes) for mapping to Crelate custom fields before ingest.

Dover Job postings including title, department, location, employment type, and description map directly to Crelate Job records. Each Dover job-to-candidate linkage migrates as a Crelate submission or candidate-job association. We preserve the Dover job status (Open, Paused, Closed) and any job owner mapping. The job-to-candidate relationship is resolved at migration time using the candidate email as the dedupe key.

Dover scorecards (AI applicant scores from Premium tier and manually created evaluation templates) do not have a direct Crelate equivalent. We export scorecard values as custom fields on the candidate record in CSV, then map them to Crelate custom fields of the matching type (number, rating, or text). If the customer used Dover's structured evaluation templates with multiple criteria, we map them to Crelate Questionnaires attached to the Person record. We flag any Dover proprietary scoring format that cannot be typed into a standard Crelate field.

Dover pipeline stages (Applied, Screening, Interview, Offer, etc.) vary by job template. We extract the complete stage taxonomy per job from Dover's CSV exports, then configure Crelate's Pipeline Stage values to match the customer's stage names and order. Stage probability percentages, where set in Dover, map to Crelate stage probabilities. Any Dover stages with no Crelate equivalent go to a reconciliation list for the customer to define before production migration.

Dover interview guides and structured interview templates are Dover-specific objects without a direct Crelate equivalent. We export the guide criteria as structured text and map them to Crelate Questionnaires or as multi-line custom fields on the Person record. The customer chooses between questionnaire format (reusable for future candidates) or custom field format (historical-only) during scoping.

Dover User accounts including name, email, and role export from Dover's team settings CSV. We map each Dover user to a Crelate User record by email match. Inactive or pending-invite Dover users go to a reconciliation queue for the customer's admin to resolve before User import. User roles (Admin, Recruiter, Hiring Manager) map to Crelate's role and permission structure.

Dover's stage history table (separate CSV export) records every candidate stage transition with a timestamp and optionally the recruiting team member who made the change. We map each stage transition to a Crelate activity entry on the Person record with the activity type set to reflect a stage change. Original stage names and timestamps are preserved as the activity description. This ensures the candidate's progression history is visible in Crelate's timeline without requiring manual re-entry.

Dover's candidate source field (LinkedIn, Referral, Job Board, Direct, etc.) maps to Crelate's Source Tracking field on the Person record. We preserve the original source value for reporting purposes and map it to Crelate's standard source taxonomy, flagging any Dover-specific source values that need customer confirmation.

Dover candidate tags export as a multi-value field in the CSV. We map each tag to Crelate's tag taxonomy on the Person record. Tags used for segmentation or pipeline filtering in Dover are preserved so that Crelate's filtering and list-building tools can replicate Dover's tagging workflow post-migration.

Dover candidate notes export from the candidate CSV as plain text or rich text fields. We map them to Crelate Notes linked to the Person record with the original author and timestamp preserved. Note attachments (documents stored in Dover) migrate as file links if URLs are present in the CSV; otherwise we flag for manual re-upload.

If Dover tracks offer details as a structured record, we map them to Crelate's Opportunity object at the job or placement level. Offer amount, start date, and offer status map to corresponding Crelate Opportunity fields. For teams using Dover's offer stage only (without a full opportunity object), we map the offer data as custom fields on the Person record to preserve the offer context.

Dover job board integrations (LinkedIn, Indeed, X/Twitter, Glassdoor, and 100+ others) are API-linked credentials stored in Dover settings, not records in the candidate data model. We do not migrate job board API keys or credentials. We document every active Dover job board connection for the customer's admin to reconfigure in Crelate's integrations section post-migration, providing a checklist of the posting URLs to re-authenticate.