Migrate from Unicorn ATS to Crelate

Unicorn ATS candidate records map to Crelate Contact records, which serve as the primary candidate entity in Crelate's Core Record model. We map candidate name fields (first_name, last_name), contact information (email, phone, address), resume files (as ContentDocument linked via ContentDocumentLink to the Contact), application date (as a custom field or note), source channel (as a custom text field or tag), and current pipeline stage assignment (as Opportunity association). The Contact serves as the ATS candidate and CRM contact simultaneously, eliminating duplication that occurs when candidate and contact are separate entities.

Unicorn ATS job records map to Crelate Opportunities representing job orders. We map job title, department, location, employment type, posting dates, and hiring manager assignment. The Opportunity's name field receives the job title and client reference. Crelate Opportunity Stages are configured to match the Unicorn ATS pipeline stage set, and each Opportunity gets a Record Type representing the job category. The Opportunity lookup to the related Contact (candidate) is resolved at migration time through the candidate mapping.

Unicorn ATS pipeline stage names and ordering are extracted and mapped to Crelate Opportunity Stages. We configure Crelate Stages with corresponding probability percentages and stage type (Open, Won, Lost). Stage automation rules (if any exist in Unicorn ATS) are documented for rebuild as Crelate Workflows post-migration. The stage configuration happens before any Opportunity records are imported so that the stage values are valid at insert time.

Unicorn ATS employee records (start date, department, job title, manager, employment status, compensation) map to Crelate Contact records with custom fields added under the Contact Core Record. We split active employees from former employees into separate Contact groups using the employment_status field, preserving start_date as a custom field and department as a tag or custom picklist. Manager assignment resolves to a Contact lookup if the manager is also a Contact in the system, or to a text field if not.

Unicorn ATS custom fields added to candidate records are exported with their definitions and values. We create corresponding custom fields in Crelate under the Contact Core Record using Crelate's Settings and Core Records configuration. Field types are mapped: text properties become Crelate Text fields, numeric properties become Integer or Decimal fields, date properties become Date fields, and multi-select properties become Crelate multi-select picklist fields. A Logical Name is assigned to each custom field for API access during migration. The customer reviews the custom field ordering and grouping before deployment.

Unicorn ATS custom fields added to job requisitions are exported with their definitions and mapped to custom fields on Crelate Opportunity records. We create the fields under the Opportunity Core Record in Crelate before migration, matching the field types and adding Logical Names for API access. Job-specific custom fields (e.g., pay range, remote policy, security clearance) map to Opportunity custom fields that appear on the job order record alongside the standard fields.

Unicorn ATS interview records (scheduled date and time, interviewer assignments, interview type, scorecard, outcome notes) map to Crelate Event records linked to the Contact (candidate) and the related Opportunity (job order) via WhatId. We resolve the interviewer assignments to Contact records (if internal) or to a text field (if external), and preserve the interview type and outcome in Event custom fields. Interview scorecards migrate as Note records attached to the Event or to the Contact.

Unicorn ATS offer records (compensation details, start date, offer status, approval history) map to the Crelate Opportunity record representing the job order. We add custom fields to the Opportunity for compensation_amount, start_date, offer_status (extended, accepted, declined, withdrawn), and any approval workflow notes. The Opportunity Stage is set to reflect the offer outcome: Closed Won for accepted, Closed Lost for declined. Offer PDFs migrate as ContentDocument attached to the Opportunity.

Unicorn ATS activity notes and email history present the highest migration risk because they export as flat CSV with no candidate record ID linkage. We run a fuzzy-match process on candidate name, email, and application date to re-associate activity records with the correct Crelate Contact. Emails migrate as Crelate Tasks or EmailMessage records; recruiter notes migrate as Note records; general activity logs migrate as Task records with TaskSubtype set appropriately. We present the customer with a preview of unattached records before committing to the migration scope and document any permanently unresolvable activity as a data loss disclosure item.

Unicorn ATS company records associated with candidates map to Crelate Company Core Records. We map company name, website, industry, employee count, and address fields. The Company record is created before Contact import so that the Contact-to-Company lookup is satisfied at Contact insert. If Unicorn ATS stores only a company text field on the candidate record without a separate company entity, we create the Company record during migration using the text value as the name.

Unicorn ATS tags applied to candidates (source tags, skill tags, status tags) map to Crelate Tags on the Contact record or to a multi-select custom field if the customer prefers structured field storage over tag-based categorization. The customer chooses the tag strategy during scoping based on how Crelate's tag and search model will be used post-migration.

Unicorn ATS placement records (placed candidate, job, client, placement date, fee) map to Crelate Opportunity records with Stage set to Closed Won and custom fields for placement_fee, placement_date, and client_reference. The Opportunity is linked to the Contact (placed candidate) and the Company (client). Placement history is preserved as a structured record rather than a note, allowing reporting on placement volume and revenue in Crelate analytics.

Unicorn ATS candidate source tracking (job board source, referral source, career page application) migrates to a custom field on Crelate Contact named candidate_source__c with a text or picklist value. If the source data contains structured sub-fields (e.g., job board name, specific posting URL), these map to additional custom fields for reporting accuracy. Source tracking is important for Crelate analytics on candidate acquisition cost and source effectiveness.

Unicorn ATS resume files and candidate attachments migrate as ContentDocument records linked via ContentDocumentLink to the Crelate Contact. We extract the file from the source export, upload it to Crelate's document storage, and create the ContentDocumentLink with LinkedEntityId pointing to the Contact and ShareType set to V (View). File metadata (filename, upload date, file size) is preserved in ContentVersion fields. The file type is validated against Crelate's supported resume parsing formats.

Unicorn ATS owner records (recruiters, hiring managers) map to Crelate User accounts. We extract all distinct owner references from candidate, job, and activity records and match by email against the Crelate User table. Owners without a matching Crelate User go to a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on migrated Opportunities and Contacts points to the resolved User record.

Unicorn ATS custom objects beyond the standard entity set (e.g., background check records, drug screening records, onboarding task lists) are exported with their full schema. We evaluate whether each custom object maps to existing Crelate Core Record custom fields (preferred for simple properties) or requires a custom object relationship if the object has sub-records. Crelate's custom field model on Core Records handles most single-entity custom objects; multi-record custom objects require custom object creation in Crelate, which is scoped separately during migration design.