Migrate from Candidate Manager to Recruit CRM & ATS

Candidate Manager candidate records map directly to Recruit CRM Candidate profiles. We extract name, contact details, email, phone, LinkedIn URL, resume file, application date, source attribution, and status stage. Ranking and pre-profiling scores transfer as numeric custom fields on the Candidate profile. The Candidate Manager stage label (Applied, Under Consideration, Interviewing, Hired) is preserved as a custom text property in Recruit CRM because the destination stage names are customizable and may differ from the source labels.

Candidate Manager job orders map to Recruit CRM Job records. We extract requisition title, department, location, open date, and status. Custom fields attached to job orders in Candidate Manager are discovered during scoping and mapped to equivalent Recruit CRM job custom fields or stored as notes if no direct equivalent exists. Active jobs are prioritized for migration with a delta pass for any job orders created during the migration window.

Candidate Manager's fixed stage names (Applied, Under Consideration, Interviewing, Hired) are preserved as stage labels and mapped to the nearest Recruit CRM pipeline stage. Because Recruit CRM allows customizable pipeline stages, we configure the destination pipeline to match the source stage sequence as closely as possible during the migration run, with the customer's input on any renaming or consolidation.

Numeric ranking scores and pre-profiling values stored as candidate properties in Candidate Manager transfer to Recruit CRM as custom number fields on the Candidate record. These are not native scoring fields in Recruit CRM and land as custom attributes that the recruiter can reference on the candidate profile. We flag these fields in the migration report so the customer's team knows where to find them post-migration.

Records created or modified via Candidate Manager's hiring manager self-service portal carry an owner attribution field identifying the hiring manager. We preserve this as a custom text field or map it to a Recruit CRM Contact if the hiring manager exists as a formal contact record. Hiring managers who do not have a Recruit CRM user account are flagged for the customer's admin to provision as Team Members or link to the corresponding Contact record.

Agencies submitting candidates through Candidate Manager's staffing portal are tracked as submission sources. We extract the agency name and submission ID and attach them to the candidate record as source attribution fields. If the agency exists as an organization in Recruit CRM, we create a Contact record under that organization and link it as the submission source. Agency-specific notes attached to candidate submissions are preserved as candidate notes.

Candidate Manager onboarding records for hired candidates include task completion status and document references. We migrate task completion status as custom fields on the Candidate record and document references as file attachments linked to the candidate. E-signature status, form-fill completion, and any dynamic onboarding form data that did not export cleanly are flagged in the migration report for manual reconciliation in Recruit CRM's document management section.

Candidate Manager's aggregate hiring funnel data exports from the reporting module are extracted as supplementary records and delivered as a structured CSV report alongside the migrated candidate and job data. These metrics reflect historical performance in Candidate Manager and do not map to live Recruit CRM reports. We recommend rebuilding key metrics as custom Recruit CRM reports post-migration using the migrated candidate data as the source.

Candidate Manager custom fields at the candidate level are not documented in a machine-readable schema. We discover them during the scoping call by reviewing sample candidate exports, map each to an equivalent Recruit CRM custom field, and flag any with unsupported data types (e.g., multi-select, formula fields) for customer review. Fields without a direct equivalent are stored as candidate notes with a prefix tag for post-migration cleanup.

Candidate Manager custom fields at the job order level are discovered during scoping by reviewing sample job exports. We map each to a corresponding Recruit CRM job custom field where a type-equivalent field exists. Fields with non-matching types (e.g., Candidate Manager uses a dropdown that Recruit CRM represents as free text) are flagged and mapped to text with a note in the migration log for the customer's admin to review post-migration.

Candidate Manager notes attached to candidate records migrate to Recruit CRM Notes on the Candidate profile. We preserve the original author attribution and timestamp where these are available in the export. Notes with attachments (e.g., evaluation forms, scorecards) are handled as file references in the migration log because file attachment migration requires separate file transfer handling.