Migrate from Cornerstone Recruiting to Zoho Recruit

Cornerstone Job Requisition records (RequisitionId, RequisitionName, PositionId, DivisionId, and custom fields) map to Zoho Recruit Job Opening. We extract all requisition metadata via the GET Requisition API, map the requisition title to Zoho's Job Title field, and map the requisition status to a Zoho Job Opening status value (Open, On Hold, Closed). Division, Location, and Position data from Cornerstone's OU hierarchy map to Zoho custom picklist fields that we create during schema setup.

Cornerstone Candidate records (Name, Email, Phone, Address, Ethnicity, and custom fields) map directly to Zoho Recruit Candidate records. A single candidate can have multiple applications across requisitions, and we preserve the full candidate profile during migration. Note that Zoho Recruit requires Last Name as a mandatory field for all candidate imports; any Cornerstone candidate record missing a Last Name value must be populated with a placeholder such as 'Not Provided' or 'None' before import, or the record will be skipped.

Cornerstone Job Applicant records are the intersection of a Candidate and a Requisition, containing ApplicationReceivedDateLocal, AverageRating, CandidateType, and PositionId. We preserve the application relationship by creating the candidate in Zoho Recruit first, then associating the candidate with the corresponding Job Opening via the Candidates subform or related list. Application metadata migrates to Zoho candidate fields or a linked interview/assessment record.

Cornerstone Application records link candidates to requisitions with their own workflow status progression. We map application status values to Zoho Recruit status equivalents (Applied, Screening, Interview, Offer, Hired, Rejected). The Application Workflow API in Cornerstone retrieves stage transitions; we document the full stage sequence and map it to Zoho's pipeline stage configuration during schema setup.

Cornerstone Application Workflows define stage progression through the hiring process with portal-specific stage names and probabilities. Zoho Recruit uses a pipeline model with status values per job opening but does not have a direct Application Workflow equivalent. We retrieve the full stage sequence from Cornerstone's GET Application Workflow API and document it as a Zoho pipeline stage configuration guide for the customer's admin to implement post-migration. Stage mapping is informational only; no workflow logic migrates.

Cornerstone organizes all recruiting data through a configurable OU hierarchy with types including Cost Center, Division, Grade, Legal Entity, Location, Position, and custom types. The Bulk API schema endpoint returns all valid OU types per portal. Zoho Recruit has no native OU hierarchy. We map each Cornerstone OU type to a corresponding custom picklist field in Zoho Recruit (e.g., cs_division__c, cs_location__c, cs_position__c) and populate values from the source OU records during candidate and requisition import.

Both requisitions and applications in Cornerstone support custom fields defined per portal and returned by the GET Job Requisition Custom Field API. We retrieve the custom field schema per portal during discovery, create matching custom fields in Zoho Recruit via Setup with equivalent field types, and map values during import. Any custom field flagged as sensitive PII in Cornerstone is excluded from bulk load per Cornerstone's Bulk API restriction and documented for manual re-entry in Zoho Recruit.

Resume files, cover letters, and supporting documents attach to candidate profiles and applications via Cornerstone's Attachment API, which returns file metadata. We extract all attachments and store them locally with reference to the parent candidate or application ID. After candidate records are assigned Zoho Recruit IDs during import, we upload each file to the corresponding Zoho record via the CRM attachment endpoint and re-associate it with the candidate or job opening. File type, size, and original filename are preserved.

Once a candidate is hired in Cornerstone, the record transitions to Core HR as an Employee with employment status, compensation history, and manager assignment. Zoho Recruit is an ATS focused on the pre-hire pipeline and does not natively manage employee records post-hire. We map employee data to a Zoho Recruit Candidate record with custom fields capturing employment status and last known position, or to a Zoho People record if the customer licenses Zoho People. The migration scope for employee records is limited to preserving the hire record for reference; ongoing employee management remains outside Zoho Recruit's ATS scope.

Cornerstone Owners map to Zoho Recruit Users. We resolve owners by email match against the destination Zoho Recruit account's user list. Owners without a matching Zoho Recruit user are held in a reconciliation queue; the customer must provision any missing Zoho users before record import resumes. Note from Zoho Recruit's migration documentation: users who already have a separate individual Zoho Recruit account must close that account before being imported into the company's Recruit account.

Cornerstone Recruiting includes client-facing features for staffing agencies managing client relationships alongside candidate pipelines. If the source portal includes client organization records, we map them to Zoho Recruit's Client module, which is available in Professional and Enterprise tiers. Client name, contact information, and associated job requirements migrate as separate client records linked to corresponding job openings.

Cornerstone captures interview schedules and feedback as part of the application workflow. We map interview records to Zoho Recruit Interview objects, preserving candidate name, job opening association, scheduled date and time, interviewer assignment, and feedback ratings. Interview status (Scheduled, Completed, Cancelled) maps to Zoho's Interview status field. Zoho Recruit's Video Interviews add-on ($12/job opening) may be relevant if the customer activates this feature post-migration.