Migrate from Bullhorn Connexys ATS to Zoho Recruit

Bullhorn Candidate records map directly to Zoho Recruit Candidates. Core fields (name, email, phone, address, skills, work history, education) map to Zoho's standard Candidate fields. We handle Bullhorn's tax information and compliance custom fields as Zoho custom fields, and flag any GDPR consent data for explicit mapping to Zoho's consent-tracking custom fields, which the customer's admin configures before migration because Zoho Recruit has no pre-built consent-management module.

Bullhorn JobOrders map to Zoho Recruit Jobs. Job title, requirements, salary range, location, and job status transfer as standard Job fields. Bullhorn job fields such as employment type, remote policy, and benefits information map to Zoho custom fields. We resolve the JobOrder-to-Job status mapping during scoping because Bullhorn and Zoho use different stage naming conventions.

Bullhorn Accounts (representing client companies) map to Zoho Recruit Clients. Company name, industry, billing address, and contact associations transfer to the Client record. We preserve the one-to-many relationship between Client and multiple Contacts. The Account's primary billing contact maps to the Client's primary contact field in Zoho.

Bullhorn Contact records (hiring managers and client-side contacts linked to Accounts) map to Zoho Recruit Contacts. We preserve the Account-Client association during migration and flag any Contact records that lack a parent Account so the customer's admin can link them to the correct Client in Zoho after migration.

Bullhorn Placements (the final hire outcome linking Candidate to JobOrder with start date, salary, and status) map to Zoho Recruit Candidates with a placement status indicator. Because Zoho Recruit does not have a dedicated Placement object, we model the placement outcome as a Candidate record with custom fields capturing start date, salary, job reference, and placement status. The original JobOrder reference is preserved in a custom field for reporting.

Bullhorn's Job Reporting junction object tracks each candidate's movement through pipeline stages (Application through Submittal, Interview, Offer, Placement) with timestamps and associated User. Zoho Recruit has no equivalent junction object. We reconstruct stage history as a series of custom fields on the Candidate record: stage_name_1, stage_date_1, stage_name_2, stage_date_2, and so on, up to the maximum number of stages configured in the source Bullhorn pipeline. If Job Reporting records are incomplete in Bullhorn (a known Connexys gotcha), we flag the gaps and reconstruct what source data allows.

Bullhorn User records representing recruiters, administrators, and managers map to Zoho Recruit Users. We resolve by email match. Bullhorn Owner assignment on Candidate, JobOrder, and Placement records migrates by resolving the Bullhorn User reference to the corresponding Zoho User record. Any Bullhorn Owner without a matching Zoho User is held in a reconciliation queue for the customer's admin to provision before Candidate import begins.

Bullhorn Opportunities track potential placements or client deals with revenue estimates. They map to Zoho Recruit Jobs with revenue-related fields. Bullhorn Opportunity custom fields vary by instance and require field-level mapping to Zoho's equivalent custom fields or notes.

Bullhorn Custom Objects (extending Candidates, Contacts, Accounts, Jobs, and Placements with up to 55 fields each; limits 2 on Bullhorn ATS, 10 on Front Office Growth/Enterprise) map to Zoho Recruit Custom Modules. We pre-create the destination Custom Module schema in Zoho Recruit before data import, mapping each Bullhorn Custom Object API name to a Zoho Custom Module with equivalent field types. Bullhorn lookup relationships to standard objects resolve to Zoho Lookup fields during import. Edition tier differences matter: if the customer has built extensive custom data on a lower-tier Bullhorn instance and is moving to a Zoho Recruit edition with fewer custom module allowances, we scope data culling before migration begins.

Bullhorn resume parsing extracts structured data from uploaded files, and file attachments export via REST API. We preserve parsed resume data as structured Candidate fields and resume files as Zoho Recruit attachments linked to the Candidate record. Large attachment volumes require chunked handling given Zoho's API credit costs per Bulk Write operation. We batch attachments in groups of 100 records per API call as specified by Zoho's API documentation.

Bullhorn activity feeds and notes on Candidate, Contact, JobOrder, and Placement records export via API. We preserve note body text and timestamps as Zoho Recruit Notes linked to the appropriate Candidate, Client, or Job record. Activity timestamps are preserved as Activity records in Zoho with the original Bullhorn timestamp carried forward.

Bullhorn represents pipeline stages as a configurable sequence from Application through Placement. Zoho Recruit uses a Candidate status field and Job Submission status. We map each Bullhorn stage to a Zoho status value (Applied, Screening, Interview, Offer, Hired, Rejected) and configure Zoho's pipeline view to display equivalent stages. The mapping is stored as a configuration document for the customer's admin to validate against their specific Zoho Recruit setup.