Migrate from Yello to Recruit CRM & ATS

Yello Candidates map directly to Recruit CRM Candidates. We extract the full Candidate record including contact information, source attribution, pipeline stage, tags, and engagement history. Custom Candidate properties discovered during the discovery pass are mapped to equivalent Recruit CRM custom fields. Any Yello Candidate appearing across multiple Requisitions (duplicate detection) is flagged and reconciled before import to prevent Recruit CRM duplicate records.

Yello Requisitions represent open positions with metadata including department, location, headcount, and status. They link to Candidates via a many-to-one relationship. We preserve this association by importing Jobs first, then resolving the Job reference when Candidates are imported so that the Candidate-to-Job linkage is maintained in Recruit CRM. Requisition status (Open, On Hold, Filled, Cancelled) maps to Recruit CRM Job status values.

Yello Campus Events spanning multiple days require flattening. The standard Yello export represents a multi-day Event as a single record with a date range. We parse the date range, split into individual day records, and write each as a separate Event in Recruit CRM. Event metadata (name, venue, description) and registration lists migrate as-is. Attendance records linking Candidates to Event days are preserved as Candidate Event participation entries in Recruit CRM.

Structured Evaluation records in Yello include scores, comments, evaluator attribution, and the associated pipeline stage. Custom evaluation forms may use non-standard field names that require a field-mapping table before migration. We extract the evaluation body, score values, and evaluator name and write to Recruit CRM as either formatted Note records (for free-text evaluations) or as structured custom fields if the customer configures an evaluation object in Recruit CRM during discovery.

Free-text conversation history and recruiter commentary attached to Candidates migrate as plain-text or HTML Notes in Recruit CRM. We extract the note body, author name, and timestamp and write as a Note record linked to the corresponding Candidate. The original author attribution is preserved in the Note body or a custom Note metadata field.

Flexible Candidate labels in Yello (typically used for school, degree, role, or recruiting season categorization) are extracted as a flat tag list. These are written to Recruit CRM as tag or label values attached to the Candidate record. Tag grouping and hierarchy are not preserved if Yello uses nested tag structures; we document the flat output and recommend manual grouping in Recruit CRM if needed.

Configurable hiring stage names and ordering are extracted from Yello including stage name, position in the sequence, and active/inactive status. Stage ordering is preserved in Recruit CRM by writing stages in ascending position order during the pipeline configuration pass. Any custom stage names (non-standard labels) are mapped to Recruit CRM stage equivalents or retained as-is if the destination allows custom stage names.

Binary files associated with Candidates including resumes, cover letters, and portfolio items are extracted from Yello exports. We write each file blob with its original filename and MIME type to Recruit CRM's document or attachment object, preserving the Candidate-to-Document linkage. Large attachment archives may require batch processing and are scoped separately during discovery.

Internal recruiter and admin user accounts are mapped from Yello user names and email addresses to Recruit CRM User records. We resolve users by email match against the destination org's user table. Any Yello user without a matching Recruit CRM account goes to a reconciliation queue for the customer's admin to provision before Candidate migration resumes. Role and permission parity is out of scope for the data migration.

Both Candidate-level and Requisition-level custom properties are audited during the discovery phase. We request sample Yello data exports and screenshots of all configured custom fields to build a complete field-mapping table covering field name, data type, and Recruit CRM target field. Custom fields missed during discovery will appear as unmapped blanks in Recruit CRM and require a correction pass. Recruit CRM supports custom fields on both Candidate and Job objects.