Migrate from Recruitee to Recruit CRM & ATS

Recruitee Jobs map directly to Recruit CRM Job records, preserving title, department, location, and status. Job custom fields migrate as custom fields in Recruit CRM. Teams on Recruitee's Start plan (5 active job cap) must stage migration in batches of 5 or fewer concurrent active positions; we coordinate upgrade to Advance or Optimize before migration or run a two-pass import. Closed and archived jobs migrate without the cap constraint.

Recruitee Candidate records map to Recruit CRM Candidate with name, email, phone, social profiles, and source attribution preserved. Custom candidate properties map directly to Recruit CRM custom fields by name match; conflicting field names receive a renamed target field. CV and resume files migrate as attachments linked to the candidate record.

Recruitee Applications link a Candidate to a Job with a specific stage and timestamp. We preserve the candidate-to-job linkage, application creation date, and application status. Application history (stage transitions with timestamps) migrates as activity entries in Recruit CRM to preserve pipeline velocity analytics.

Recruitee's per-job customizable pipeline stages require extraction per pipeline configuration and remapping to Recruit CRM's stage structure. Stage order, names, and probability values migrate. If Recruitee's pipeline has stages that do not map cleanly to Recruit CRM defaults, we create custom stage values during schema setup before job import.

Recruitee Offer records (status, salary details, start date, candidate linkage) map to Recruit CRM Offer records with the candidate relationship preserved. Offer status history migrates as structured notes attached to the offer so reporting can be rebuilt in Recruit CRM.

Recruitee Talent Pools are named collections of candidates. Each pool maps to a Recruit CRM Candidate List with membership migrated as list entries linked to the candidate record. Pool-level tags and notes migrate as list metadata or candidate tags. Candidates appearing in multiple pools generate entries in each corresponding Recruit CRM list.

Recruitee scorecard data lives inside application activity as attribute-level ratings attached to a specific interviewer and timestamp. There is no standalone scorecard object in the export. We serialize each scorecard as a structured evaluation note with parseable attribute-rating pairs (for example, 'Technical Skills: Strong Yes') and preserve the interviewer identity and timestamp. Recruit CRM's evaluation fields receive this as structured notes if no native scorecard object is available in the destination plan tier.

Recruitee Users map to Recruit CRM Users by email match. Role terminology differs: Recruitee's Admin, Recruiter, and Hiring Manager map to equivalent Recruit CRM roles. We reconcile by extracting all distinct user references in migrated records and matching against the destination User table before record import.

Recruitee Departments migrate as Recruit CRM Departments, preserving the job-to-department linkage. Department-level reporting structures survive migration intact.

Recruitee Notes (free-text entries attached to candidate profiles) migrate as Notes in Recruit CRM with timestamp and author attribution preserved. Notes linked to specific applications carry the candidate linkage in Recruit CRM.

File attachments (resumes, cover letters, portfolio files) stored in Recruitee's document store export as binary files and re-upload to Recruit CRM linked to the candidate record via filename and candidate ID resolution.

Recruitee's CareersHub career site pages (page content, job board configurations, domain settings) do not live in the same API schema as Jobs and Candidates. We export CareersHub content as a structured archive and either import it to Recruit CRM's career site module if available in the customer's plan tier, or deliver it as a documented archive for manual republishing. This is a low-severity gap; most teams rebuild the careers page in Recruit CRM's builder.