Migrate from Cornerstone Recruiting to Recruit CRM & ATS

Cornerstone Candidates (persistent profile records with Name, Email, Phone, Address, and Ethnicity fields) map to Recruit CRM Candidate records. A single Candidate can have multiple Job Applicants; we preserve all application associations. Custom fields defined on the Candidate object via the GET Job Requisition Custom Field API are retrieved per portal and mapped to Recruit CRM custom fields, excluding any flagged as secure or PII by Cornerstone's schema. Source candidate IDs are preserved in a custom field cs_candidate_id__c for audit and cross-reference.

Cornerstone Requisitions (with RequisitionId, RequisitionName, PositionId, and DivisionId) map to Recruit CRM Job records. We pull full requisition metadata including status, department assignment, location, and hiring manager via the GET Requisition API. If Cornerstone uses custom OU types beyond standard Divisions, we map them to Recruit CRM custom fields or tags. PositionId is preserved in cs_position_id__c for cross-reference.

Job Applicants represent the intersection of a Candidate and a Requisition, including ApplicationReceivedDateLocal, AverageRating, CandidateType, and PositionId. Each Job Applicant migrates as an application entry linked to the corresponding Candidate and Job records in Recruit CRM. ApplicationReceivedDateLocal becomes the submission date; AverageRating maps to a custom numeric field in Recruit CRM.

Cornerstone Application Workflows define stage progression through the hiring process, with portal-specific states and transitions returned by the GET Application Workflow API. These portal-specific stages map to Recruit CRM Kanban pipeline stages during migration. We document the full stage-to-stage mapping and deliver it as a configuration reference so the customer's admin can validate or adjust stage ordering in Recruit CRM's pipeline builder post-migration.

Cornerstone's OU hierarchy (Cost Center, Division, Grade, Legal Entity, Location, Position, and custom types) does not have a direct structural equivalent in Recruit CRM's flat agency model. We split the OU structure: Location maps to Recruit CRM's built-in location field on Job; Division maps to a custom Department field; Cost Center and Legal Entity map to tag-based or custom fields. We retrieve all valid OU types from the Cornerstone Bulk API schema endpoint during discovery and design the split strategy with the customer before extraction.

Resume files, cover letters, and supporting documents attached to Candidate profiles and Applications are extracted via the Attachment API and re-associated with migrated Candidate and application records in Recruit CRM. We extract file metadata (filename, MIME type, upload date, size) and the binary content. Re-association uses Candidate email or candidate ID matching against the destination system. Large attachment volumes may require staged import sequencing.

Once a Candidate is hired, the Cornerstone record transitions to Core HR as an Employee with employment status, compensation history, and manager assignment. We map Employee data to Recruit CRM Placement records for customers who track hired candidates as placements in Recruit CRM. Compensation fields (salary, bonus structure) migrate as custom fields. Manager assignment maps to the Recruit CRM recruiter or consultant field if available.

Both Cornerstone Requisitions and Applications support custom fields defined per portal. We retrieve all custom field definitions via the GET Job Requisition Custom Field API, identify their types (text, numeric, picklist, date), and configure equivalent custom fields in Recruit CRM before import. Any fields marked as secure or containing PII in Cornerstone's schema are excluded from migration per the Bulk API restriction and flagged for manual re-provisioning in Recruit CRM by the customer's admin.

Cornerstone Owners (recruiters and hiring managers associated with requisitions, applications, and candidate records) are resolved by email match against Recruit CRM Users. We extract every distinct owner referenced across requisitions and applications during discovery and match them to destination users. Any Cornerstone Owner without a matching Recruit CRM User is held in a reconciliation queue for the customer to provision before record import resumes.

Cornerstone's Bulk API explicitly excludes loading data to secure custom fields and sensitive personally identifiable information (SPII) fields. We identify which custom fields are marked sensitive in the schema and exclude them from extraction. Post-migration, the customer must manually re-enter or securely re-provision these fields in Recruit CRM. We flag every excluded field with its name, type, and recommended Recruit CRM field configuration in the migration handoff document.