Migrate from Yello to Zoho Recruit

Yello Candidate records map directly to Zoho Recruit Candidate. We extract first name, last name, email, phone, address, source, pipeline stage, tags, and all custom Candidate properties. Zoho Recruit requires Last Name as a mandatory field on every Candidate; any Yello Candidate without a last name (e.g., mononyms or corporate entity names) receives a placeholder value of 'Not Provided' per Zoho's import specification. Custom Candidate fields from Yello map to Zoho custom fields, which must be pre-created during the schema design phase because Zoho's Standard plan limits custom fields to 50 per module.

Yello Job Requisitions map to Zoho Recruit Job Opening. We extract title, department, location, headcount, status, and any custom Requisition fields. The Requisition-to-Job Opening mapping is sequenced first in the migration order because Job Opening ID is a required lookup on Candidate records (via the Apply for a Job module). Active Requisitions map to Zoho's Open status; closed and filled Requisitions map to Closed status.

Yello Campus Events map to Zoho Recruit Event records. Yello Events can span multiple days and venues in a single record; the standard export represents a multi-day Event as a single record with a date range. We parse the date range, split into individual daily Event records, and write each as a separate Zoho Event with a reference to the parent Event name for grouping. Registration lists and Candidate attendance records attach to the Event via Zoho's Candidate_Event linkage.

Yello Evaluations (structured feedback records including scores, comments, and evaluator attribution tied to a specific Pipeline Stage) map to Zoho Recruit Interview Feedback Form records. Custom evaluation forms with non-standard field names require a field-mapping table generated during discovery. We map each Yello evaluation score field to a corresponding Zoho custom field or standard rating field, and preserve evaluator name and timestamp.

Yello Notes (free-text conversation history and recruiter commentary attached to Candidates) migrate to Zoho Recruit Note records. We extract the note body, author name, and timestamp. Notes are written to the Candidate's record via Zoho's Note module with the Parent ID set to the migrated Candidate ID. HTML formatting in Yello notes is preserved as rich text where Zoho supports it.

Yello flexible candidate labels (typically school, degree, role, or recruiting season tags) migrate to Zoho Recruit Tag records. Tags are extracted as a flat list per Candidate and written to Zoho as Tag records with a Candidate_Tag linkage. Tag names longer than Zoho's character limit are truncated to 50 characters per Zoho field specification.

Yello configurable hiring stage names and ordering map to Zoho Recruit Hiring Pipeline stages. We extract the stage name, position in the sequence, and active/inactive status. Stage ordering is preserved by writing stages in ascending position order during Zoho pipeline configuration. Zoho Recruit allows multiple pipelines (each with its own stage sequence) which mirrors Yello's pipeline configuration for teams using multiple concurrent recruiting tracks.

Yello binary attachments (resumes, cover letters, portfolio items) associated with Candidates migrate to Zoho Recruit's Candidate document storage. We extract the file blob, filename, and MIME type, and write to Zoho's Candidate Resume field or Document module depending on the destination Zoho edition. Files exceeding 25 MB per Zoho upload limits are flagged for manual re-upload by the customer's admin.

Yello internal recruiter and admin user accounts map to Zoho Recruit User records by email address match. Zoho Recruit requires each migrating user to not have an existing separate Zoho Recruit account (per Zoho's migration documentation); users with pre-existing Zoho accounts are placed in a reconciliation queue for the customer's admin to close before import. Role and permission parity is out of scope for the data migration.

Yello Candidate-level custom properties are audited during the discovery phase and mapped to Zoho Recruit custom Candidate fields. We generate a field-mapping table covering Yello field name, data type, and Zoho equivalent field type (text, number, date, picklist, checkbox). Zoho Standard limits custom fields to 50 per module; Enterprise raises this to 300 per module. Custom fields that exceed the plan limit are flagged and the customer must upgrade or omit fields before migration.

Yello Requisition-level custom properties map to Zoho Recruit custom Job Opening fields. Same discovery and mapping process as Candidate-level custom fields. The mapping table is reviewed with the customer's admin before schema creation to ensure field type compatibility (e.g., date fields in Yello map to Zoho date fields, not text).

Yello Candidate source attribution (LinkedIn, Referral, Job Board, Event, etc.) migrates to Zoho Recruit Candidate Source field. We extract the source label and write as a Zoho picklist value, creating the picklist entry if it does not already exist. Sources without a match in Zoho's existing picklist are created as new picklist values during the migration.

Yello engagement history (interview scheduling activities, recruiter interactions tied to Candidates) maps to Zoho Recruit Tasks, Calls, and Events. We extract the activity type, subject, date, and outcome, and write to the appropriate Zoho module. Tasks map to Zoho Task; phone-based interactions map to Zoho Call; meeting-based interactions map to Zoho Event. All activities are linked to the migrated Candidate via Zoho's Candidate lookup.