Migrate from Cornerstone Recruiting to BambooHR

Cornerstone Requisitions map to BambooHR Jobs. The RequisitionId and RequisitionName transfer to BambooHR's Job ID and Job Title. PositionId and DivisionId from Cornerstone map to BambooHR's Department field with Division used as the primary Department. Location from Cornerstone maps to BambooHR's Location field. Job status (Open, On Hold, Closed) migrates directly. We pull the full requisition schema via Cornerstone's GET Requisition API including any custom fields defined at the portal, and map each to a BambooHR custom field or standard field as appropriate.

Cornerstone Candidate records (the persistent profile object containing Name, Email, Phone, Address, and Ethnicity) map to BambooHR Applicant records. A single Candidate who applied to multiple Requisitions in Cornerstone creates multiple Applicant records in BambooHR, each tied to its respective Job. We use Candidate email as the dedupe key during import. The Candidate's most recent application status becomes the Applicant's current stage in BambooHR.

The Cornerstone JobApplicant object (the intersection of Candidate and Requisition, containing ApplicationReceivedDateLocal, AverageRating, CandidateType, and PositionId) maps to a BambooHR Application record. We link each Application to its corresponding BambooHR Job and Applicant by resolving the CandidateId and RequisitionId through the lookup tables we built during extraction. ApplicationReceivedDateLocal preserves the original application timestamp.

Cornerstone Application Workflows define portal-specific stage progressions that vary by recruiting process and geography. We retrieve the full workflow state list via GET Application Workflow API during discovery, enumerate every distinct stage value across all active workflows, and map each to a corresponding BambooHR stage name (Applied, Phone Screen, Interview, Offer, Hired, Rejected). Stages with no BambooHR equivalent become configurable stages added to the BambooHR job before migration.

Cornerstone Division OUs map to BambooHR Departments. The OU schema endpoint returns all valid OU types per portal, and we identify which OU type corresponds to the customer's intended Department structure. If the customer uses multiple OU types (e.g., Division and Legal Entity both feeding a reporting hierarchy), we use the top-level OU (Division or Legal Entity) as Department and flag the secondary for manual setup. Cornerstone's configurable OU types require early identification during scoping because the schema varies by customer.

Cornerstone Location OUs map directly to BambooHR Locations. Both platforms use a flat location list, so the mapping is straightforward. We extract all unique Location values from Cornerstone OUs, deduplicate, and create the corresponding Locations in BambooHR before requisition import so that the Location field is satisfied at import time.

Cornerstone Position OUs map to BambooHR Job Title fields on the Employee record (post-hire) or as a custom field on the Applicant record. For active requisitions, PositionId becomes a custom field or maps to the Job's designated title field depending on the customer's BambooHR configuration. Position is a second-level OU in Cornerstone's hierarchy and may also inform the Department mapping in cases where Division is not explicitly set.

Candidate attachments (resumes, cover letters, portfolio files) are extracted via the Cornerstone Attachment API which returns file metadata and binary content. We re-associate each file with the corresponding migrated Applicant record in BambooHR. BambooHR's document attachment limit and file size restrictions are verified during scoping. We note the original file name and MIME type from Cornerstone to preserve document type classification in BambooHR.

Custom fields defined on Cornerstone Job Requisitions (returned by GET Job Requisition Custom Field API) map to BambooHR custom fields on the Job record. We retrieve the full custom field schema per portal during discovery, identify the field type (text, number, date, dropdown), and create matching custom fields in BambooHR before migration. Dropdown custom fields require value mapping between Cornerstone picklist values and BambooHR options list.

Custom fields on Cornerstone Applications map to BambooHR custom fields on the Applicant record. Same schema-retrieval approach via the custom field API. Note that sensitive PII fields (SPII fields marked secure in Cornerstone) are excluded from migration per the Bulk API restriction; we deliver a written list of which fields were excluded for the customer's admin to manually re-create in BambooHR.

Cornerstone Employee records (Core HR data: employment status, compensation history, manager assignment) map to BambooHR Employee records if the customer also migrates core HR data. If only the ATS module is in scope, we migrate the hired candidate as an Employee record with Name, Email, hire date, Department, and Job Title populated from the requisition and application data. Manager assignment maps by resolving the manager's Employee ID from Cornerstone's Core/HR API.

Cornerstone captures EEOC voluntary disclosure fields (ethnicity, veteran status, disability) on the Candidate record. BambooHR provides aggregate EEO reporting at the organization level rather than tied to individual candidates (per legal requirements). We migrate the EEO response status (responded, declined) at the candidate level into a custom field in BambooHR for compliance records, while the disclosure values themselves are mapped to BambooHR's aggregate reporting categories.