Migrate from Dover to Zoho Recruit

Dover candidate records map to Zoho Recruit Candidate with a transformation step for the mandatory Last Name field. Dover allows candidates without a last name; Zoho Recruit silently skips any record missing Last Name during import. We scan the Dover CSV export for empty last_name values, flag them to the customer, and apply a 'Not Provided' placeholder before ingest so no candidate record is lost. Email, phone, source, current stage, and application date map directly to their Zoho Recruit equivalents.

Dover Jobs (title, department, location, description, status) map to Zoho Recruit Job Openings. Job-to-candidate linkage is preserved via Zoho's Candidates module linking to Job Opening ID. We map each Dover job status (Open, Closed, Draft) to Zoho's Job Opening status values. If the Dover instance has department tags on jobs, these map to Zoho's Department field or a custom multi-select picklist.

Dover AI scorecards and manually created evaluation templates are Dover-specific objects with no direct Zoho Recruit equivalent. We export scorecard values as custom fields in the CSV and map them to Zoho Recruit custom fields (up to 50 on Standard, 300 on Professional/Enterprise). Alternatively, we create Zoho Interview Forms to replicate the scorecard structure and link completed forms to the candidate record. The choice depends on the customer's Zoho plan tier and whether they prefer free-text score values or structured form fields.

Dover pipeline stages (Applied, Screening, Interview, Offer, Hired, Rejected, and any custom stages) vary per job in Dover. We extract the stage taxonomy per job, map each stage to a Zoho Recruit Candidate Status value, and configure the mapping at import time. Any Dover stage with no Zoho equivalent is flagged and the customer chooses whether to map it to an existing status or create a custom status value in Zoho Recruit before migration.

Dover's stage history table records each time a candidate moved between pipeline stages with a timestamp. Zoho Recruit does not have a native stage history audit object. We create Zoho Activity records (type: Note) for each stage transition, timestamped to the original Dover change date, linked to the candidate record. This preserves the historical progression context in the candidate timeline without losing the chronological record.

Dover user accounts (name, email, role) map to Zoho Recruit Users. We match Dover users to Zoho users by email address. Zoho requires at least two users in the account before importing Candidates; if the customer has only one Dover user, we flag this before migration begins. Inactive Dover users are imported as inactive Zoho users so that historical record ownership is preserved. Any Dover user without a corresponding Zoho account is placed in a reconciliation queue for the customer to provision.

If Dover contains custom fields beyond the standard scorecard values (for example, custom rating scales, interview rubrics, or sourcing-channel fields), we recreate these as Zoho Recruit custom fields on the Candidate module. Standard plan supports up to 50 custom fields per module; Professional and Enterprise support 300 per module. We confirm the target plan's field limit during scoping and flag any overflow before migration.

Dover supports custom properties on candidate and job records. We export all Dover custom fields from the CSV, classify each by data type (text, number, date, picklist), and create equivalent Zoho Recruit custom fields of matching type before migration. If a Dover custom field has no Zoho equivalent type, we default to free-text and flag the mapping for the customer's review.

Dover attachments (resumes, cover letters, portfolio files) stored on candidate records export via Dover's CSV export. We transfer these as file attachments to the corresponding Zoho Recruit Candidate record. Zoho Recruit supports attachments up to 10 MB per file; we flag any attachment exceeding this limit before ingest and advise on splitting or compressing the file.

Dover notes attached to candidate records export as free-text entries in the candidate CSV. We create Zoho Recruit Notes linked to each candidate record, preserving the note body and original creation timestamp. If Dover notes contain embedded formatting, we strip to plain text for Zoho compatibility.

Dover interview records (scheduled interviews linked to candidates and jobs) map to Zoho Recruit Interviews. Interviewer assignments from Dover map to Zoho Recruit Interviewer records, and we link each interview to the correct candidate and job opening. If Dover stores interview scorecards as separate records, these follow the scorecard mapping described above.

Dover tasks (action items, follow-ups) linked to candidates map to Zoho Recruit Tasks. Task status, priority, due date, and assigned user transfer directly. Task assignment resolves via the User mapping by email match. Tasks without a valid Dover user assignment are imported under the migration service account and flagged for manual reassignment.