Migrate from CATS to Recruit CRM & ATS

CATS candidate records map directly to Recruit CRM candidate profiles. Core fields including name, email, phone, current company, title, source, status, and tags migrate as typed fields. CATS custom fields on candidates export with their schema (text, dropdown, date, checkbox) and are re-created in Recruit CRM before import. Candidate source attribution preserves the original referral channel (LinkedIn, Job Board, Referral, Direct) as a typed picklist field.

CATS job orders map to Recruit CRM job records. Fields including job title, department, location, status, description, requirements, and salary range transfer directly. Pipeline stage assignments from CATS map to Recruit CRM job status values (Open, In Progress, On Hold, Closed, Filled). CATS job order custom fields migrate using the same schema-export-then-recreate approach used for candidates.

CATS call activity records migrate to Recruit CRM call log entries linked to the corresponding candidate. Call disposition, duration, timestamp, and owner attribution transfer to equivalent typed fields. Activity ordering is preserved by setting the call timestamp to the original CATS record timestamp.

CATS email activity records migrate to Recruit CRM email log entries attached to the candidate record. Email subject, body content, direction (sent/received), timestamp, and owner attribution migrate directly. We preserve the original email body as a rich text field so recruiters can read the full conversation in context.

CATS notes migrate to Recruit CRM note entries linked to the candidate. Note body, created timestamp, and owner attribution transfer directly. If CATS notes contain attachments, those are exported separately and re-uploaded to the corresponding note record in Recruit CRM.

CATS interview activity records map to Recruit CRM interview entries attached to the candidate and job. Interview date, time, type (phone, video, in-person), interviewer name, and outcome transfer to typed fields. Interviewer attribution uses the CATS user-to-Recruit CRM user mapping established during discovery.

CATS user accounts (name, email, role, department) export and map to Recruit CRM user accounts. We match by email address as the primary key. Any CATS user without a matching Recruit CRM account goes to a reconciliation queue for the customer's admin to provision before record import. Owner assignments on candidates and job orders resolve through this user mapping.

CATS departments export as a standalone list and are created in Recruit CRM before any job order or user import. Job orders in CATS that reference a department carry the department reference forward into Recruit CRM's department field. Users are also tagged with their department in Recruit CRM for reporting by division.

CATS tags on candidates and job orders export as comma-separated values and map to Recruit CRM tag fields. Tags used for candidate segmentation (industry, skill, clearance level) migrate as typed tag entries so filtering and reporting work without manual re-tagging in Recruit CRM.

CATS candidate source values (LinkedIn, Referral, Job Board, Agency, Direct, Career Site) migrate to Recruit CRM's source picklist. If CATS uses custom source values not in Recruit CRM's standard list, we add them as custom source options during schema setup before migration begins. Source attribution on candidates is preserved for reporting on recruitment channel effectiveness.

CATS resumes and cover letters linked to candidates export as files and re-upload to the corresponding candidate record in Recruit CRM. File names and association metadata (document type, upload date) are preserved. We download attachments via the export tool or API, store them temporarily, and re-upload with the correct candidate association during the import phase.

CATS pipeline stages (New, Screening, Interview, Offer, Hired, Rejected, and any custom stages) are extracted during discovery and mapped to Recruit CRM job status values. Custom stage labels from CATS are added to Recruit CRM's status picklist before migration so that no stage value is lost or defaulted incorrectly during import.