Migrate from eBoss to Zoho Recruit

eBoss Candidate records map 1:1 to Zoho Recruit Candidate. We preserve the candidate's name, email, phone, current company, current title, skills, source channel, status within the pipeline, and all custom properties. Zoho Recruit requires Last Name on every Candidate import; we pre-validate the eBoss export and flag any record missing a last name, replacing it with a placeholder value ('Not Provided') per Zoho's import documentation. Skills from eBoss map to Zoho Recruit's Skills multi-select picklist. Resume attachments migrate as Zoho Recruit file attachments linked to the Candidate record.

eBoss Job Postings map to Zoho Recruit Job Openings with direct field mapping: job title, department, location, employment type, description, requirements, and hiring manager. Open and closed status maps to Zoho Recruit's status field. Active job limits vary by Zoho Recruit plan (1 on Free, 10 per recruiter on Standard, 20 per recruiter on Enterprise); we verify the customer's plan supports their job opening count before migration and flag any excess as out-of-scope for active migration.

eBoss Users (recruiters, hiring managers, admins) map to Zoho Recruit Users. We match by email address. A hard constraint: Zoho Recruit will not import a User who already holds a separate personal Zoho Recruit account — they must close that account first before the migration user can be created. We run a pre-flight check against the Zoho Recruit tenant for duplicate emails and raise a reconciliation item for each conflict. Additionally, Zoho Recruit requires at least two users to be present in the tenant before CSV import begins; we ensure this is satisfied before initiating the User module load.

eBoss Applications (the join record between a Candidate and a Job Opening, tracking stage, submission date, and interview status) map to the Zoho Recruit Candidate record with its Job Opening association. The application stage from eBoss becomes the candidate's pipeline stage within the relevant Job Opening. We resolve the foreign key from eBoss (Candidate ID + Job Opening ID) into Zoho Recruit's candidate-to-job relationship using the Candidate ID as the primary insert and the Job Opening ID as the lookup reference.

eBoss Interview records (scheduled interviews, interviewer assignments, feedback, scores, outcome) map directly to Zoho Recruit's Interview module. Interview date, time, duration, interviewer name, interview type, and outcome status migrate as typed fields. Feedback forms and scoring data from eBoss migrate as notes attached to the Interview record, since Zoho Recruit's Interview module does not have a native structured scoring sub-object at the Standard tier.

eBoss Notes attached to Candidates, Job Openings, or Applications migrate to Zoho Recruit Notes linked to the corresponding record via ContentDocumentLink. Note body content, author, creation date, and modification date are preserved. We set the ActivityDate on each note to the original eBoss timestamp to maintain chronological ordering in the Zoho Recruit activity timeline.

eBoss Task records (hiring follow-ups, screening steps, offer-letter tasks) map to Zoho Recruit Task with Status, Priority, Subject, Due Date, and Assigned To preserved. Task ownership resolves from eBoss owner email to Zoho Recruit User ID via the User mapping. Recurring tasks from eBoss do not have a native Zoho Recruit equivalent and are migrated as a series of individual Task records with a custom recurrence note field.

eBoss file attachments (resumes, cover letters, portfolio documents, offer letters) migrate as Zoho Recruit file attachments linked to the relevant Candidate, Job Opening, or Interview record. We validate file size against Zoho Recruit's attachment limits (50 MB per file) and chunk any oversized files. File name and original upload date are preserved in the Zoho Recruit file metadata.

eBoss Client records (staffing agency clients or corporate hiring companies) map to Zoho Recruit Client. Client name, industry, address, primary contact name, and billing contact migrate as typed fields. If eBoss stores client hierarchy or multi-level organizational contacts, the top-level client maps to Zoho Recruit Client and any sub-contacts map as Zoho Recruit Contact records linked to the Client.

eBoss Contact records associated with recruitment operations (hiring manager contacts, referral sources, agency contacts) map to Zoho Recruit Contact. Contact name, email, phone, title, company, and relationship type migrate directly. Contact records linked to a Client map with the Client lookup resolved after the Client module loads, per Zoho Recruit's dependency order.

eBoss custom fields (industry-specific properties, compliance flags, regional sourcing channels) store as name-value pairs in eBoss. We migrate them by either creating matching typed Custom Fields in Zoho Recruit (subject to the 50 per module limit on Standard or 300 on Enterprise) or preserving them as a JSON blob in a Zoho Recruit Notes field for admin review post-migration. We flag any eBoss tenant exceeding Zoho Recruit's custom field ceiling during scoping so the customer can decide whether to upgrade tiers or consolidate fields before migration begins.

eBoss Skills or Competencies attached to a Candidate record (certifications, technical stack, language proficiencies, clearance levels) map to Zoho Recruit's Skills multi-select picklist on the Candidate object. If eBoss stores skills as a structured sub-object with expiry dates or issuing authority, those additional attributes migrate as name-value custom fields on the Candidate rather than a standalone module, since Zoho Recruit Standard does not expose a structured skills-with-metadata sub-object.