Migrate from Unicorn ATS to BambooHR

Unicorn ATS candidate records (name, contact information, resume, source channel, and application date) map to BambooHR Applicant records attached to Job openings. BambooHR flattens applicants as records directly linked to job postings rather than using a separate Candidate-to-Application split. We extract resume files as attachments linked to the Applicant record. Candidate source attribution migrates to BambooHR's standard source tracking fields. Any candidate status or stage history from Unicorn ATS is preserved as a note on the Applicant record because BambooHR does not natively store pipeline stage progression history per applicant.

Unicorn ATS job records (title, department, location, employment type, posting dates, and hiring manager) map to BambooHR Job Opening records. BambooHR's Job Opening object includes the posting content, hiring team, and applicant pipeline view. We map the Unicorn ATS requisition status (open, paused, closed) to BambooHR's job status. Department and location mapping requires configuration in BambooHR's organizational structure before migration.

Unicorn ATS pipeline stages (application through offer and hire) do not map directly to a named pipeline object in BambooHR. Instead, BambooHR uses per-job applicant status labels (Applied, Screening, Interview, Offer, Hired, Rejected) that are configurable per job opening. We document the current stage names and order from Unicorn ATS and create a BambooHR status configuration that mirrors the original funnel for each job. Stage automation rules from Unicorn ATS do not migrate; we inventory them for the customer's admin to configure in BambooHR's Hiring Settings.

If Unicorn ATS contains employee records (as distinct from candidate profiles), these map to BambooHR Employee records with fields including start date, department, job title, manager assignment, employment status, and compensation. BambooHR's employee data model includes tabs for Personal Info, Employment Info, Compensation, Time Off, and Benefits. We map source fields to their corresponding BambooHR employee fields and flag any custom employee fields that require BambooHR custom field configuration before migration.

Unicorn ATS custom candidate fields require explicit mapping to BambooHR Applicant custom fields or standard fields. BambooHR supports custom fields for Applicants with limitations: dropdown list fields require the exact option values to exist in BambooHR before migration; multi-select list fields are supported only if all values match; information fields and section headers do not migrate via API. We extract custom field definitions from Unicorn ATS, validate them against BambooHR's custom field type support, and pre-create the destination field schema in BambooHR before any applicant data imports.

Unicorn ATS employee custom fields map to BambooHR Employee custom fields. BambooHR limits which employee tabs accept custom fields (custom fields cannot be added to the Time Off, Benefits, Performance, or Onboarding tabs via API). We audit the source employee custom field set and map only to BambooHR-supported locations, flagging any source fields that have no valid BambooHR destination. Required-field constraints in BambooHR employee records must be satisfied at migration time or the record import fails.

Unicorn ATS interview records (scheduled date and time, interviewer assignments, interview type, and outcome notes) map to BambooHR Interview records attached to the Applicant. Interview scorecards from Unicorn ATS do not have a native BambooHR equivalent; we preserve scorecard data as a structured note attached to the Interview record. Interview scheduling data is mapped to BambooHR's interview scheduling fields, though BambooHR does not include native two-way calendar sync with external calendars for interview scheduling without third-party integration.

Unicorn ATS offer records (compensation details, start date, offer status, and approval workflow history) map to BambooHR Offer records associated with the Applicant. BambooHR offers an offer letter template feature with variable fields for compensation and start date. Approval routing logic from Unicorn ATS is not configurable in BambooHR in the same way; we document the original approval sequence and flag it for the customer's admin to configure within BambooHR's offer settings or through a separate approval tool. Offer history migrates as structured records with status preserved.

Unicorn ATS recruiter notes, email logs, and general activity history attached to candidates are among the hardest records to migrate. Most ATS platforms export activity logs as flat CSV with no linkage to the candidate record ID that can be automatically re-associated. We run a fuzzy-match process on candidate name, email, and application date to reattach activity history to the correct BambooHR Applicant record. We present the customer with a preview of unattached records (typically 5-15% in our experience with flat-CSV exports) before committing to the activity migration scope. Any activity records that cannot be confidently matched are exported as a separate reference file for manual lookup.

Unicorn ATS hiring manager assignments on job requisitions map to BambooHR Employee records added to the Hiring Team on the corresponding Job Opening. We resolve Unicorn ATS hiring manager references by email against BambooHR Employee records, provisioning any missing employee records if the hiring manager is not yet in the BambooHR system. BambooHR's hiring team permissions are job-specific rather than department-specific, which is a known limitation for matrixed organizations; we flag this during scoping for organizations with complex reporting structures.