Migrate from Cornerstone Recruiting to Crelate

Cornerstone Candidate records map to Crelate Contact records. The Candidate object exposes Name, Email, Phone, Address, and Ethnicity fields along with any standard profile fields. We extract candidates via the Candidate API and map to Crelate Contact fields with email as the dedupe key. Custom candidate fields from Cornerstone map to Crelate custom fields on Contact, noting that Crelate supports Short/Long Answer, Date, Numeric, and Picklist types but not all Cornerstone custom field data types may have a direct Crelate equivalent.

Cornerstone Job Requisitions map to Crelate Job records. Requisition metadata including RequisitionId, RequisitionName, PositionId, and DivisionId transfers to Crelate's job title, description, and location fields. The Cornerstone Requisition workflow status maps to the Crelate job publishing status (Draft, Active, On Hold, Closed). Custom Requisition fields migrate to Crelate Job custom fields.

Cornerstone Job Applicant records (the intersection of Candidate and Requisition) map to Crelate Opportunity records attached to a Contact. ApplicationReceivedDateLocal, AverageRating, CandidateType, and PositionId transfer to Crelate Opportunity fields. The Opportunity links to the mapped Contact (Candidate) and the mapped Job (Requisition). CandidateType (Employee Referral, Agency, Direct) maps to a Crelate custom field or tag.

Cornerstone Application Workflows define stage progression through the hiring process. Each workflow's stages map to Crelate Opportunity pipeline stages. We retrieve the full workflow state list via GET Application Workflow API and create corresponding Crelate stages in the Opportunity pipeline. Stage transition rules are documented for the customer's admin to rebuild as Crelate workflow automation if needed.

Cornerstone organizes data through OUs including Cost Center, Division, Legal Entity, Grade, Position, and Location. Crelate does not have an equivalent OU hierarchy. We map Division and Cost Center values to Crelate custom fields on Contact and Job, and map Location OUs to Crelate Location records where they represent physical office locations. Custom OU types require discussion with the customer to determine the appropriate Crelate destination.

Cornerstone Applications link Candidates to Requisitions with their own workflow status values. In Crelate, this is represented by the Opportunity (application) linked to the Contact (candidate) and Job (requisition). Application status values from Cornerstone's workflow stages map to the Crelate Opportunity stage set defined during pipeline configuration.

Cornerstone attachments (resume files, cover letters, supporting documents) attach to Candidate profiles and Applications. The Attachment API returns file metadata. We extract attachments and re-associate them with migrated Crelate Contacts and Opportunities. File types and sizes are preserved; Crelate's Business Plus tier includes increased data storage limits.

Cornerstone Job Requisition custom fields, retrieved via GET Job Requisition Custom Field API, map to Crelate Job custom fields. We extract the schema per portal to identify field names, types, and whether any are marked as secure (excluded from bulk operations). Non-secure custom fields transfer as Crelate custom fields of the equivalent type (Short Answer to Text, Picklist to Picklist, Date to Date, Numeric to Numeric).

Cornerstone Application custom fields map to Crelate Opportunity custom fields. These capture structured data specific to the application process (interview scores, screening results, offer details). Field type mapping follows the same rules as Requisition custom fields, with picklist values preserved as Crelate picklist options.

Once a Cornerstone Candidate is hired, the record transitions to Core HR as an Employee with employment status, compensation history, and manager assignment. Crelate is an ATS and recruiting CRM, not an HCM. We migrate the Employee record as a Contact with custom fields capturing employment status, start date, and manager reference. Full HR data (compensation, benefits) does not have a Crelate equivalent and is flagged for the customer's HR team to manage separately.

Cornerstone stores engagement history on Candidate and Job Applicant records. Activity data (notes, calls, emails, interviews) migrates to Crelate Activity records attached to the Contact. Each activity type maps to the corresponding Crelate activity form type. Engagement timestamps and content transfer as-is; engagement-driven automation triggers do not migrate.

Cornerstone OU-linked hiring managers and recruiters map to Crelate User records by email match. Any Cornerstone owner without a matching Crelate User is held in a reconciliation queue for the customer's admin to provision before record import completes. Owner references on Requisitions and Job Applicants are resolved at migration time.