Migrate your Unicorn ATS data

Candidate records typically include name, contact information, resume files, application date, source channel, and pipeline stage assignment. The research corpus contains no platform-specific schema documentation for Unicorn ATS. We handle field mapping by aligning to standard ATS candidate field names and flagging any custom properties that require explicit mapping during scoping.

Job records include requisition title, department, location, employment type, posting dates, and associated hiring managers. Job schemas vary by platform edition. We export the full job record set and map fields to the destination schema, flagging any deprecated or non-standard fields.

Pipeline stages define the candidate journey from application through offer and hire. Stage names, order, and automation rules are frequently customized. We extract the current stage configuration and map it to equivalent stages in the target ATS, noting any stages that have no direct equivalent.

In HRMS contexts, employee records may be distinct from candidate profiles. Employee records typically include start date, department, job title, manager assignment, employment status, and compensation. The research does not confirm Unicorn ATS object naming. We probe for a distinct employee object during migration scoping.

Custom fields added by the customer to Candidates, Jobs, or Employee records require explicit field-level mapping. We export custom field definitions alongside their values and document any validation rules or picklist constraints that must be replicated in the destination.

Interview records include scheduled date and time, interviewer assignments, interview type, scorecards, and outcome notes. These records often reside in a separate object with a master-detail relationship to the candidate. We extract interview history and map it to the destination's equivalent object, flagging any scorecard templates that need manual recreation.

Offer records include compensation details, start date, offer status, and approval workflow history. Approval routing logic is often platform-specific. We export offer data as structured records and note any custom approval chains that cannot be auto-replicated in the destination.

Recruiter notes, email logs, and general activity history attached to candidates are often stored as flat text or linked records. The research confirms that activity logs and notes are consistently reported as the hardest data to migrate cleanly, as most platforms export them as flat CSV. We extract all available activity history and attempt to associate it with the correct candidate record, noting any gaps.