Migrate from Zoho Recruit to Bullhorn ATS & CRM

Zoho Recruit Candidates map directly to Bullhorn Candidate records. Standard fields (First Name, Last Name, Email, Phone, Skills, Status) translate to Bullhorn's firstName, lastName, email, phone, skillIDs, and status. Zoho Candidate Status values (New, Active, On Hold, Dead, Joined) map to Bullhorn's Candidate status enumerations. Zoho's subforms—Employment History, Education, Certifications—are the primary transformation challenge: we flatten these into Bullhorn custom fields on the Candidate object or attach them as structured Candidate Note records during the transform phase. Custom fields require a Professional or Enterprise Bullhorn tier; we provision matching custom fields before candidate import.

Zoho Recruit's Clients module (agency-specific) maps to Bullhorn's ClientCorporation entity. Standard fields including Client Name, Website, Industry, and Address map to ClientCorporation fields directly. Client-specific custom fields (fee structures, preferred categories, tier classifications) migrate to Bullhorn custom fields on ClientCorporation. We create the ClientCorporation records first in the dependency order so that Candidate-to-Client lookup relationships can be resolved at insert time rather than through a separate update pass.

Zoho Recruit Contacts (hiring managers, client representatives) map to Bullhorn Contact records linked to the corresponding ClientCorporation. First Name, Last Name, Email, Phone, Title, and Department migrate directly. The Zoho Contact-to-Client lookup relationship maps to Bullhorn's Contact.ClientCorporationId reference. Custom fields on Zoho Contacts (Extended certifications, Preferred communication method) migrate to Bullhorn Contact custom fields. Any Zoho Contact without a corresponding ClientCorporation is created as a standalone Contact; we flag these during scoping for customer review.

Zoho Recruit Job Openings map to Bullhorn JobOrder records. Title, Description, Employment Type, and Address map to JobOrder fields directly. Zoho pipeline stages map to Bullhorn JobOrder status values (Open, Pending, Closed, Cancelled). We configure Bullhorn JobOrder status values before migration so that the stage translation is deterministic. Job Order custom fields migrate to Bullhorn JobOrder custom fields. Zoho's job board posting history does not migrate; we document the posting URLs and boards for the customer to reconfigure in Bullhorn's job distribution settings.

Zoho Recruit Interviews are subforms within the Candidate record with scheduled time, interview type, interviewer, and feedback fields. Bullhorn separates interview history into the JobSubmission object (which tracks a candidate's journey through a specific job order) and candidate notes for qualitative feedback. We transform each Zoho interview subform row into a Bullhorn JobSubmission record for the associated JobOrder, then attach interview feedback as a Candidate Note linked to the submission. Interviewer name and interview type (Phone Screen, Technical, Onsite, Panel) map to JobSubmission custom fields or note content.

Zoho Recruit Notes attached to Candidates, Job Openings, Clients, and Contacts migrate to Bullhorn Note records linked via ContentDocumentLink to the corresponding Bullhorn entity. Plain-text notes migrate as-is. Rich-text notes preserve HTML formatting where the destination Bullhorn instance supports it. We preserve the original note author and creation timestamp in Bullhorn note metadata. Notes attached to Zoho subforms (Employment History, Education) that we flatten into candidate custom fields are linked back to the candidate via structured note content referencing the flattened field data.

Zoho Recruit Tasks map to Bullhorn Task records with Status, Priority, Subject, Due Date, and assigned Owner preserved. Task type discriminator (General, Screening, Submission Follow-up) maps to Bullhorn Task custom fields or category tags. Zoho's assignment rules are not migrated; we preserve the task owner by resolving Zoho Owner email to Bullhorn User ID during the Owner reconciliation phase. Tasks without a matching Bullhorn User are assigned to the migration admin for manual reassignment.

Zoho Recruit Events (calendar-based meetings and interviews) map to Bullhorn Event records. Start Date/Time, End Date/Time, Location, Description, and attendees migrate directly. We link Bullhorn Events to the corresponding Candidate and JobOrder via the WhatId reference. Events without a parent JobOrder (general recruitment meetings) are created without a WhatId and linked to the primary recruiter's User record. All-day event flags and event series (recurring meetings) are not preserved; we migrate individual event instances only.

Zoho Recruit Call Logs map to Bullhorn Task records with TaskSubtype = Call. Call duration, disposition, phone number dialed, and caller type (Inbound/Outbound) migrate to Bullhorn Task custom fields. Call recording URLs stored in Zoho are preserved as Bullhorn ContentDocument records linked via ContentDocumentLink to the Task. Call log timestamps are preserved in the Activity Date field to maintain the candidate engagement timeline order.

Zoho Recruit attachments require exact folder hierarchy preservation: /Attachments/Candidates/[candidate_id]/, /Attachments/JobOpenings/[job_id]/, /Attachments/Clients/[client_id]/. Bullhorn uses ContentDocument with ContentDocumentLink to the parent entity. We reconstruct the Zoho folder tree under Bullhorn's document storage path during pre-flight preparation, then map each file to the corresponding Bullhorn Candidate, JobOrder, ClientCorporation, or Contact record. Any attachment with an unresolvable parent record is held in a reconciliation queue. Resume files attached to Candidates are prioritized and mapped to the Candidate resume field where Bullhorn's data model supports it.

Zoho Recruit Users (recruiters, admins, hiring managers) map to Bullhorn User records. We match by email address as the dedupe key. Zoho's 2,000-record User import cap applies to Zoho's native migration tool; FlitStack AI handles larger user counts by migrating the primary Owner records (those actively assigned to Candidates, Jobs, and Clients) as Bullhorn Users and associating any remaining historical assignees as Candidate custom field values or Contact associations, preserving the attribution chain without triggering any cap. Role and profile assignments require Professional or Enterprise Bullhorn and are mapped from Zoho's role structure.

Zoho Recruit Campaigns (sourcing initiatives linked to job boards or specific job openings) map to Bullhorn JobOrder records when the campaign has a direct job focus, or to Candidate tags for sourcing-wide campaigns. Campaign fields (Name, Type, Start Date, Budget) that have no Bullhorn native equivalent are stored as custom fields on the associated JobOrder or as a Campaign custom field on Candidate. The customer's Bullhorn admin reviews the campaign mapping during sandbox validation and can create a Campaign custom object in Bullhorn CRM if reporting by sourcing initiative is required.

Zoho Recruit custom fields (available in Professional and Enterprise tiers only) are not available in Free or Standard editions, which means some records may have no custom field data to migrate. We inspect the source account's Zoho edition during discovery. For paid-tier accounts with custom fields, we create matching Bullhorn custom fields on the appropriate entity before importing records, using the Zoho field type to determine the Bullhorn field type (text, picklist, number, date, checkbox). Lookup fields in Zoho require a separate migration phase to resolve the referenced record ID to the Bullhorn equivalent ID at migration time.

Zoho Recruit Assessment results attached to Candidates (pre-screening scores, skills assessments, psychometric results) do not have a direct Bullhorn native equivalent. We migrate assessment results as structured Candidate Note records with the assessment name, date, score, and evaluator in a consistent format, or to Bullhorn custom fields on the Candidate object if the assessment output is a numeric score or pass/fail flag. Assessment question banks and scoring rubrics require manual recreation in Bullhorn; we document the assessment schema from Zoho for the customer's Bullhorn admin to reference.