Migrate from Yello to Crelate

Yello Candidate records map directly to Crelate Person records with the Candidate subtype. We extract contact fields (name, email, phone, address), source attribution, pipeline stage, tags, and engagement history. Custom Candidate properties discovered during scoping map to Crelate custom fields on the Person record. The dedupe key is email address; any Candidates sharing an email across multiple Yello Requisitions are flagged as duplicates and held in a reconciliation queue for the customer's admin to resolve before final insert.

Yello Job Requisitions map to Crelate Job records. The Requisition's department, location, headcount, status (Open/Closed/Draft), and description fields transfer directly. We preserve the many-to-one relationship to Candidates by writing Jobs before Candidates and populating the Candidate-to-Job association during Candidate import using the Job's Crelate ID as a foreign reference. Multi-requisition workflows in Yello map to Crelate's Job record types if multiple hiring processes are configured.

Yello Campus Events spanning multiple days require splitting into individual day records in Crelate. We parse the Yello Event's date range, generate a separate Event record for each scheduled day, and preserve the parent Event name as a prefix so that all split records are identifiable as a cohort. Venue, registration links, and attendance counts migrate to each split Event. Registration lists migrate as Event invitee records linked to the corresponding daily Event.

Yello Evaluations containing scores, comments, and evaluator attribution tied to a Pipeline Stage map to Crelate Activity records with Form responses. Custom evaluation forms may use non-standard field names, so we build a field-mapping table during discovery before writing. The evaluator's name maps to the Activity author, and the evaluation timestamp preserves for chronological ordering in the Candidate's activity timeline.

Yello free-text notes attached to Candidates migrate as Crelate Activity records with the Note type. We extract the note body, author, and timestamp, writing as plain-text content. Notes without a timestamp receive the record creation date from Yello export. HTML-formatted notes from Yello render as rich-text notes in Crelate where the destination supports it.

Yello tags used to categorize Candidates by school, degree, role, or recruiting season migrate as Crelate Tags. Tags are extracted as a flat list from the Yello export and written to Crelate's Tag object, then linked to the corresponding Person records via TagAssignment records. If the customer uses Yello tags for segmentation, we preserve the full tag vocabulary so that reporting groups survive the migration.

Yello configurable hiring stage names and ordering migrate to Crelate Pipeline and Stage configuration. We extract the stage name, its position in the sequence, and whether the stage is active. Stage ordering is preserved by setting the sort_order value in Crelate's Pipeline stage configuration. If Yello stages use custom names (e.g., 'Campus Screen' or 'Recruiter Review'), we create Crelate Pipeline Stages with matching names rather than defaulting to Crelate's standard stage vocabulary.

Yello binary Attachments (resumes, cover letters, portfolio items) associated with Candidates migrate to Crelate Document records linked to the Person. We extract the file blob and original filename, preserving the upload timestamp from Yello. If the Yello export delivers attachments as URLs rather than blobs, we note this as a limitation and flag which Documents require manual re-upload in Crelate.

Yello internal recruiter and admin user accounts map to Crelate User records by email match. We extract user names and email addresses from the Yello export and match against the Crelate destination's User table. Any Yello User without a matching Crelate User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Role and permission parity is out of scope for the data migration; the customer's admin configures Crelate's role-based access post-migration.

Yello custom Candidate properties discovered during discovery scoping map to Crelate custom fields on the Person record. We audit the full field list from the sample export, generate a field-mapping table covering field name, data type, and destination field ID, and pre-create the custom fields in Crelate before any Person records are written. Fields missed during discovery appear as unmapped blanks and require a correction pass.

Yello custom Job Requisition properties map to Crelate custom fields on the Job record. We apply the same discovery and field-mapping process used for Candidate custom fields, creating Crelate custom fields before Job import and flagging any fields that require a data-type decision (e.g., a Yello text field storing a numeric value that should become a Crelate number field).

Yello Event registration records linking Candidates to Events migrate to Crelate Event Attendee records. We resolve the Candidate's new Crelate Person ID and the Event's new Crelate Event ID at migration time and write the attendee association. Registration status (Registered, Attended, No-Show) migrates to the attendee record. If the Yello export delivers registrations as separate CSV passes, we coordinate the ordering so that Candidates and Events exist before attendee records are inserted.