Migrate from Yello to BambooHR

Yello Candidates map to BambooHR Applicants. We extract name, email, phone, address, source, pipeline stage, tags, and engagement history from the Candidate CSV export. In BambooHR, Applicants are created via POST /employees/hire or tracked via the BambooHR ATS. We preserve the original Yello Candidate ID in a custom field yello_candidate_id__c for audit and reconciliation. Tags from Yello map to a multi-select picklist or text field in BambooHR depending on tag cardinality.

Yello Requisitions map to BambooHR Jobs. We extract job title, department, location, headcount, status, and description from the Requisition export. In BambooHR, Jobs are created via POST /jobs and track status (open, closed, filled). The Requisition status maps to BambooHR Job status values. If Yello has department and location as custom fields rather than native properties, we map them to BambooHR's department field and the Job's location string.

Yello Pipeline Stages map to BambooHR application status values. We extract the stage name and position from Yello's pipeline configuration and create corresponding application status entries in BambooHR via the ATS settings. Stage probability percentages from Yello (if exported) are stored in a custom field for reference. The stage ordering is preserved by sequencing the BambooHR status list to match the Yello pipeline order.

Yello Campus Events have no direct BambooHR equivalent. Events represent campus recruiting sessions with registration lists and multi-day scheduling that BambooHR does not model. We extract Event metadata (name, date, venue, registration count) and write it as a note on the related Job in BambooHR, or as a standalone reference document delivered alongside the migration. Candidate attendance records from Events are parsed and linked to the corresponding Applicant as tags or notes indicating event participation.

Yello Evaluations (structured feedback with scores and comments) do not have a native BambooHR equivalent. We split Evaluations into component parts: numeric scores map to custom numeric fields on the Applicant record (eval_score_1__c, eval_score_2__c, etc.), and free-text comments and evaluator attribution are written as Note records attached to the Applicant. We document the full evaluation schema during discovery and generate a field-mapping table covering each evaluation form field name and its BambooHR target.

Yello Notes migrate to BambooHR Notes attached to the Applicant record. We extract note body, author name, and timestamp. BambooHR supports notes on employees and applicants; we write the note via the API with the associated employee or applicant ID. If notes contain HTML formatting, we strip to plain text unless the target field supports HTML rendering.

Yello Attachments (resumes, cover letters, portfolio items) migrate to BambooHR Files attached to the Applicant record. We extract the file blob and original filename from the export. BambooHR stores files as Base64-encoded content in the File table linked to the employee or applicant. File type is preserved from the original extension. Binary attachments exceeding 25 MB require chunked upload handling.

Yello Tags (school, degree, role, recruiting season) are extracted as a flat list and mapped to a BambooHR custom multi-select picklist field on the Applicant record. If the tag list exceeds 150 values (BambooHR multi-select limit), we use a text field or create multiple single-select fields grouped by tag category. The customer confirms tag categorization strategy during scoping.

Yello Users (recruiters, admins) map to BambooHR Users by email match. We extract user name and email from the Yello export and match against BambooHR's user table. Any Yello User without a matching BambooHR User is placed in a reconciliation queue; the customer's BambooHR admin provisions missing users before final record assignment. Role and permission parity is out of scope for the data migration.

Yello custom Candidate properties migrate to BambooHR custom fields on the Applicant object. Without a schema API in Yello, we request a sample export or screenshots of all configured custom fields during discovery. Each custom field is audited for data type (text, number, date, picklist) and mapped to the equivalent BambooHR custom field type. Required field constraints are enforced during import; any missing required values block the record insert and are flagged for correction.

Yello custom Requisition properties migrate to BambooHR custom fields on the Job object or as linked custom fields on the associated Job record. We follow the same discovery and field-mapping process as for custom Candidate fields. Custom requisition fields that reference other records (e.g., department lookup) are flattened to text values in BambooHR if no equivalent lookup exists.