Migrate from Zoho Recruit to BambooHR

Zoho Recruit Candidates map to BambooHR Applications. The key structural difference is that BambooHR Applications must attach to a Job Opening; standalone candidate records without a job are rejected on import. We create Job Opening stubs for any candidate without a linked job, preserving the Zoho Recruit pipeline stage as a custom field zr_original_stage__c on the BambooHR Application record. Candidate email, phone, skills, and source are mapped to the corresponding BambooHR Application fields.

Zoho Recruit Job Openings map directly to BambooHR Job Openings. We migrate job title, department, location, employment type, and job description. Postings linked to job boards in Zoho are noted but not re-created; BambooHR's hosted career page receives new job posts manually after migration. Active versus closed status is preserved from Zoho's job stage.

Zoho Recruit's Clients module is agency-specific and holds external hiring-company records. BambooHR does not have a standalone Clients/Organizations object for agencies. For staffing agencies migrating to BambooHR, we map Clients to the Organization field on the Employee record or create a separate reference spreadsheet. Corporate HR customers typically do not use the Clients module, so this mapping is a no-op for that segment. The mapping approach is determined during discovery scoping.

Zoho Recruit Contacts (hiring managers, references, candidate secondary contacts) map to BambooHR Employee records with an employment status set to inactive or a custom Contact type. The employee's primary role is recorded in the jobTitle field. If the Contact is also a Candidate in Zoho Recruit, we create both an Application and an Employee record with a shared custom identifier to prevent duplicate data entry in BambooHR.

Zoho Recruit Users map to BambooHR Employees with system access. Zoho Recruit's native migration tool caps user imports at 2,000 records; we flag this ceiling during discovery. For accounts exceeding 2,000 users or employee history, we migrate primary owner records as active BambooHR Employees and create archived Employee records for historical assignees without system access, preserving attribution chains in a custom field zr_original_user_id__c. Role and profile assignments from Zoho Professional/Enterprise migrate as BambooHR system access levels.

Zoho Recruit Interviews map to BambooHR Notes attached to the corresponding Application record. Interviewer name, scheduled time, interview type, and feedback are preserved in structured custom Note fields. BambooHR does not have a native interview scheduling object; teams relying on Zoho Recruit's interview calendar sync may need to adopt BambooHR's built-in scheduling integration or a third-party calendar tool post-migration. We flag this as a recommended rebuild area in the automation inventory handoff.

Zoho Recruit Notes attached to Candidates, Job Openings, Clients, and Contacts migrate to BambooHR Notes on the corresponding Application or Employee record. Plain-text notes migrate as-is. Rich-text notes in HTML format migrate as HTML Notes where BambooHR supports them, or as plain text with HTML tags stripped where compatibility requires simplification.

Zoho Recruit Tasks (calls, events, to-dos) map to BambooHR To-Do records linked to the Application or Employee. Task status, priority, due date, and description migrate directly. Call logs from Zoho's Tasks with Call subtype migrate as To-Dos with call duration recorded in a custom field. BambooHR To-Dos do not support the same conditional assignment rules as Zoho Recruit, which we note for the customer's admin during the rebuild planning phase.

Zoho Recruit resume attachments require extraction with folder hierarchy preserved before import. BambooHR's document system stores files up to 10 MB per file with a 100 MB total storage cap; we verify storage allocation during discovery and flag if the customer's attachment volume exceeds BambooHR's limits. Files are uploaded to BambooHR's document system first, then linked to the corresponding Employee record via BambooHR's employee document association API. Any files orphaned by missing candidate-job linking are held in a reconciliation queue.

Zoho Recruit Campaigns hold sourcing initiatives linked to job boards or specific openings. BambooHR does not have a Campaign equivalent. We map the campaign source as a custom field source_campaign__c on the Application record, preserving the original sourcing attribution. For agencies using Campaigns to track job board spend, we recommend a post-migration spreadsheet or BambooHR's reporting add-on to replicate the analysis.

Zoho Recruit custom fields (available in Professional and Enterprise tiers only) migrate as BambooHR custom fields on the corresponding object (Application or Employee). We inspect the source account's edition during discovery to confirm custom field availability. BambooHR caps custom fields at 50 per object; we verify this ceiling is not exceeded during scoping. Customers on Zoho Recruit Free or Standard with no custom fields have a no-op mapping for this object.