Migrate from Unicorn ATS to Recruit CRM & ATS

Unicorn ATS candidate records map to Recruit CRM Contact records, which serve as the primary candidate entity in Recruit CRM's unified ATS-CRM model. We extract candidate name, contact information, resume files, application date, source channel, and pipeline stage assignment. Custom fields added to candidates in Unicorn ATS migrate to Recruit CRM's custom field model, preserving field type (text, number, date, picklist) and validation rules. We use email address as the primary dedupe key during import.

Job records from Unicorn ATS (requisition title, department, location, employment type, posting dates, hiring manager assignment) map directly to Recruit CRM Job records. We preserve the job status (open, closed, on hold) and any custom fields attached to the job object. Job-to-candidate associations are resolved during the candidate import phase using the Unicorn ATS application record linking.

Unicorn ATS pipeline stages define the candidate journey from application through offer and hire. We extract the current stage configuration (stage names, order, and any automation rules) and map them to Recruit CRM's pipeline stage model. Stage names are recreated in Recruit CRM, and stage order is preserved. Automation rules attached to stages (such as automatic email triggers) are documented for manual rebuild in Recruit CRM's workflow builder since automation rules do not migrate as code.

In HRMS contexts, employee records distinguish from candidate profiles. Unicorn ATS employee records (start date, department, job title, manager assignment, employment status, compensation) map to Recruit CRM Contact records with a status flag distinguishing employees from candidates. If the customer uses Recruit CRM's HRMS module, employee records map to the equivalent employee object. We preserve the employment status and start date fields during migration.

Custom fields added by the customer to Candidates, Jobs, or Employee records in Unicorn ATS require explicit field-level mapping. We export custom field definitions alongside their values, document field types and validation rules, and recreate them in Recruit CRM's corresponding objects before data import. Multi-select picklist values, date formats, and numeric formats are normalized during the transform phase to match Recruit CRM's field type constraints.

Interview records in Unicorn ATS include scheduled date and time, interviewer assignments, interview type, scorecards, and outcome notes. We map these to Recruit CRM's calendar event records linked to the corresponding Contact (candidate) and Job. Scorecard responses migrate to custom fields on the candidate record. We preserve the scheduled date and time ordering during import.

Offer records in Unicorn ATS include compensation details, start date, offer status, and approval workflow history. These map to Recruit CRM's Offer object if the customer's Recruit CRM plan includes offer management. Approval routing logic from Unicorn ATS is documented separately for the customer's admin to rebuild in Recruit CRM's approval workflow configuration. We preserve offer status and compensation details as structured fields.

Recruiter notes, email logs, and general activity history attached to candidates in Unicorn ATS require special handling. Most ATS platforms, including Unicorn ATS, export activity notes as a flat CSV file with no linkage to the candidate record ID in an automatically re-associable format. We run a fuzzy-match process using candidate name, email, and application date to reattach historical activity to the correct Contact record in Recruit CRM. We flag any unmatched activity records before committing to migration scope and present the customer with a preview of unattached records. This step is the most migration-specific gotcha for this pair.

Resume files and candidate attachments from Unicorn ATS migrate to Recruit CRM's document attachment model linked to the corresponding Contact record. We preserve file names, upload dates, and file types. Binary file transfer is handled separately from the CSV data migration using Recruit CRM's file upload API. We document the file format support (PDF, DOCX, etc.) against Recruit CRM's accepted formats.

Unicorn ATS users and owners referenced on candidate, job, and activity records map to Recruit CRM User records. We resolve users by email match and preserve the user's display name and role assignment. Any Unicorn ATS user without a matching email in Recruit CRM goes to a reconciliation queue for the customer's admin to provision before record import resumes.