Migrate from Candidate Management System to Recruit CRM & ATS

Candidate Manager Job records export with status, department, location, posting dates, and internal job ID. We map Job records 1:1 into Recruit CRM Job, preserving the original internal job ID as a reference field. Active and inactive job status migrates as-is; any jobs with no associated applications are flagged for customer review before migration.

Candidate profiles export with name, contact details, work history, education, skills, and social profiles. We handle multi-record deduplication by email address and flag duplicate candidates for customer review before insert. Recruit CRM's candidate profile supports custom fields that map from Candidate Manager's tenant-specific custom properties.

Applications link Candidates to Jobs and carry status, source, submission timestamp, and custom application properties. We preserve the application-to-candidate and application-to-job relationships explicitly in Recruit CRM rather than inferring them. Application status values are mapped to Recruit CRM stage names during configuration.

Candidate Manager's configurable stage names and order per Job or globally map to Recruit CRM's pipeline stage configuration. We enumerate every active stage across all pipelines during discovery, map stage sequences explicitly, and flag any applications in stages that have no equivalent in Recruit CRM's default pipeline configuration. The customer chooses whether to use Recruit CRM's default pipeline or create custom pipelines matching their existing stage logic.

Each Candidate Manager tenant configures its own custom Candidate properties. We enumerate all custom fields during discovery, map them to Recruit CRM custom candidate fields by name or inferred type (text fields used as numeric scores become number fields), and flag any orphaned custom fields without a clear destination for customer review. Ambiguous fields (e.g., a text field used as a picklist) require explicit mapping decisions before migration.

Application-level custom properties (ranking scores, pre-profiling data, screening results) migrate to Recruit CRM custom application fields. Numeric scores migrate directly; textual scoring rubrics that lack structured fields in Recruit CRM are flagged for manual re-entry or stored as text notes. Any custom properties referencing Lookups to other objects require destination object existence before migration.

Recruiter notes attached to Candidates or Applications export as free-text blobs. We preserve note content, authorship, and timestamp, and insert them into Recruit CRM's note structure linked to the corresponding Candidate or Application record. Non-structured note fields cannot automatically map to structured destination fields; we store the full note body as-is.

Resume files, cover letters, and portfolio documents export as binary blobs. We extract text content where parsable and re-upload original file types to Recruit CRM's document storage attached to the corresponding Candidate record. File naming conventions are normalized during upload to avoid duplicates.

Ranking scores and pre-profiling data live as properties on the Application or Candidate record in Candidate Manager. Numeric scores migrate to Recruit CRM custom number fields on the candidate or application object. Textual scoring rubrics that cannot map to structured fields are flagged for manual rebuild using Recruit CRM's scorecard or custom form feature.

Candidate Manager Owners map to Recruit CRM Users. We resolve owners by email match. Any Candidate Manager Owner without a matching Recruit CRM User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Active versus inactive status is preserved in a custom field for audit.

Candidate Manager's staffing agency portal access supports external client companies. Recruit CRM maintains a separate Client database for client relationship management. If Candidate Manager stores client company data alongside candidate data, we split client records into Recruit CRM's Client object, preserving company name, contact details, and portal access configuration.

Application source tracking (job board referral, direct application, agency referral) migrates to Recruit CRM's source field on the Application record. Source values are normalized to match Recruit CRM's predefined source list or extended with custom source values during configuration.