Migrate from Candidate Manager to Zoho Recruit

Candidate Manager candidate records map to Zoho Recruit Candidates. We extract name fields, contact details (email, phone, address), resume reference, application date, source attribution, and status stage. Last Name is mandatory in Zoho Recruit; Candidate Manager records without a Last Name value are flagged for manual entry as 'Not Provided' or equivalent before import. Ranking scores and pre-profiling numeric values transfer to custom numeric fields in Zoho Recruit since the platform does not have a native ranking property at the candidate level.

Candidate Manager job orders map to Zoho Recruit Job Openings. We map requisition title, department, location, open date, and closing date. Job order status (Active, On Hold, Filled, Closed) maps to Zoho Recruit's Opening Status field. Custom fields attached to job orders in Candidate Manager require field-level discovery during scoping and individual mapping to Zoho Recruit custom fields on the Job Opening module.

Candidate Manager uses fixed stage names (Applied, Under Consideration, Interviewing, Hired) that cannot be reconfigured at the workflow level. We preserve the original stage label as a Zoho Recruit custom picklist field and map it to the nearest Zoho Recruit Candidate Status value. The customer chooses the target status mapping during scoping so that stage progression logic can be rebuilt as Zoho Recruit workflow rules post-migration.

Numeric ranking and screening scores from Candidate Manager transfer as Zoho Recruit custom number fields on the Candidate record. These fields are not natively supported in all ATS platforms and may appear as custom properties rather than standard score fields. We create the custom fields during schema setup, apply the field mapping during import, and document the field names for the customer's reporting team to include in dashboards.

Records created via Candidate Manager's hiring manager portal carry an owner attribution field. Zoho Recruit represents hiring managers either as Users (if they log in directly) or as Hiring Managers in the Hiring Manager module (for portal-only access). We preserve the original owner attribution as a text reference but flag that hiring managers without formal Zoho Recruit user accounts may not have activity tracking continuity. The customer provisions the appropriate Hiring Manager records during the user reconciliation phase.

Agencies submitting candidates through Candidate Manager's staffing portal are tracked as submission sources with agency name and submission ID. We map agency name to Zoho Recruit Vendor name or Client name depending on whether the agency relationship is vendor (supplying candidates) or client (using the staffing firm's services). Submission IDs are stored as reference fields on the candidate record for audit traceability.

The application record linking a Candidate to a Job Order maps to Zoho Recruit's Candidate-Job Opening association. Application date, source channel (direct, job board, referral), and current stage transfer to the Candidate record's application history. Multiple applications for the same candidate across different job orders create separate Candidate-Job mappings in Zoho Recruit.

Candidate Manager onboarding task completion status and document references migrate to Zoho Recruit as Task records linked to the Candidate. E-signature status and form-fill data that cannot be cleanly exported as structured data are flagged in the pre-migration inventory for manual reconciliation. Zoho Recruit's Employee Conversion feature (Professional+) can transition a Candidate to an Employee record in Zoho People if the customer's HR stack includes it.

Candidate Manager aggregate hiring funnel data from the reporting module transfers as supplementary records to preserve historical metrics. Zoho Recruit's native reporting covers forward-looking pipeline data; historical funnel metrics from Candidate Manager are documented as a reference dataset rather than native reports. The customer rebuilds funnel reports in Zoho Recruit's Standard or Custom Reports based on the migrated candidate and job opening records.

Candidate Manager custom fields at the candidate level require discovery during scoping because they are not documented in a machine-readable schema. We create matching custom fields in Zoho Recruit during schema setup, applying the appropriate field type (text, picklist, date, number, checkbox). Field-level mapping is validated during the sandbox migration phase before production import.

Candidate Manager custom fields at the job order level map to Zoho Recruit custom fields on the Job Opening module. Custom field limits vary by Zoho Recruit plan: 50 per module at Standard, 300 per module at Enterprise. We validate against the customer's target plan and flag any fields that would exceed the limit for discussion.

Resume files attached to Candidate Manager candidate records are mapped to Zoho Recruit's Resume field on the Candidate record. We extract resume files from the Candidate Manager export package, batch them by candidate ID, and attach them during the import phase. File format compatibility (PDF, DOCX, RTF) is validated before batch upload.

Candidate Manager owner references on records map to Zoho Recruit User records by email match. If a Candidate Manager owner does not have a corresponding Zoho Recruit User account, the record is held in a reconciliation queue. Users with existing separate Zoho Recruit accounts cannot be migrated into the destination account per Zoho's migration constraints and must close their separate account first.

Interview scheduling data from Candidate Manager (interviewer name, date, status) migrates to Zoho Recruit Interview records linked to the Candidate and Job Opening. Candidate Manager interview ratings or feedback scores map to Zoho Recruit's Interview Feedback Form fields if the customer is on Professional tier or above; otherwise they store as custom fields.