Migrate from Dover to Recruit CRM & ATS

Dover Candidate records map directly to Recruit CRM Candidate records. The Dover candidate_id is preserved as an external reference field. Name, email, phone, LinkedIn URL, source attribution, current stage, and application date transfer as standard fields. We flag any Dover candidates with no email address or with duplicate email addresses for the customer's admin to resolve before final import.

Dover Job postings map to Recruit CRM Job records with title, department, location, employment type, and description preserved. Job status (open, paused, closed) transfers to Recruit CRM status. We preserve the job-to-candidate linkage by loading Jobs first and using Dover's job_id as an external key referenced on the Candidate import phase.

Dover scorecard values export as custom fields on the candidate record in CSV. AI-generated scorecards on Dover's Premium tier store scores in a proprietary format that does not map to a standard Recruit CRM field type. We export them as free-text custom fields or numeric custom properties depending on the score format, and document any scorecards that cannot be parsed cleanly for the customer's admin to verify post-migration.

Dover stage names vary per job because teams create custom stage taxonomies. We extract the complete stage set across all Dover jobs during discovery, map each named stage to a corresponding Recruit CRM pipeline stage, and flag any Dover stages that have no clear Recruit CRM equivalent for admin decision. Stage-change timestamps migrate as activity history entries on the candidate record.

Dover user accounts export from team settings as name, email, and role. We map Dover owner assignments on candidate and job records to Recruit CRM user records by email match. Any Dover user with no corresponding Recruit CRM user goes to a reconciliation queue for the admin to provision before record import resumes.

Dover's stage history exports as a separate CSV table with candidate_id, stage_name, and timestamp. We reconstruct the stage progression timeline in Recruit CRM by inserting candidate activity records with type 'stage_change' and the original timestamp. This preserves hiring context without requiring Recruit CRM's native stage history feature.

Dover's job board integrations (LinkedIn, Indeed, Glassdoor, and 100+ others) are OAuth-linked credentials stored in Dover settings, not records in the candidate data model. We do not migrate job board API credentials. We document each active job board posting for the customer's admin to reconnect in Recruit CRM after migration.

Dover's Gmail and Calendar OAuth integrations store scheduling and email history in Google, not in Dover's database. These records are not included in the CSV export. We document which candidate records had linked Google activity and flag them for the customer to reconnect the Recruit CRM Google Calendar integration post-migration to resume scheduling continuity.

The Dover Recruiting Marketplace connects companies with external fractional recruiters and is a separate service from the core ATS data model. Candidate and job records in the marketplace context are not part of the standard export. We do not migrate marketplace relationships or hourly recruiter credentials.

Dover's candidate source attribution (organic, referral, job board, agency) migrates to a Recruit CRM custom field on the Candidate record. Source is preserved as a string value so that the customer's admin can configure a source taxonomy in Recruit CRM to match their historical reporting categories.