Migrate from JazzHR to Zoho Recruit

JazzHR Jobs map to Zoho Recruit Job Openings with title, location, description, salary range, and department preserved. The hiring_lead_id on the JazzHR job is remapped to the Zoho Recruit user who will own the requisition. If the source job references a department_id, we resolve it against the migrated Departments taxonomy before inserting the Job Opening. Active versus archived status on the source job sets the Zoho Recruit Job Opening status field.

JazzHR Candidate profiles (name, email, phone, address, work history, education) map directly to Zoho Recruit Candidate records. The educationLevelCodes enumeration in JazzHR (36 codified values) is stored as a custom picklist field in Zoho Recruit rather than a free-text field. Zoho Recruit requires a Last Name on every Candidate; source records without one receive a placeholder value (marked in the migration log) so the record is not silently skipped during import.

JazzHR Prospects are the join entity linking a Candidate to a Job with status, source, referral, and apply date. Zoho Recruit does not have a standalone Application object as a top-level entity; instead, Applications attach to the Candidate record as a related list entry. We restructure this by inserting Candidates first (with a lookup back to the migrated Job Opening), then creating Application records linked to the Candidate and the corresponding Job Opening. The prospect status maps to the Zoho Recruit Candidate Status field, and the apply date becomes the Submission Date.

JazzHR Departments migrate as Zoho Recruit Departments. The department taxonomy is inserted before Jobs so that the department assignment on each Job Opening resolves correctly at import time. Departments with no associated jobs are migrated as inactive to avoid cluttering the Zoho Recruit setup.

Every JazzHR job carries a hiring_lead_id tied to a user. We extract all hiring lead IDs, match them by email against Zoho Recruit's User table, and build an OwnerId lookup map. Any hiring lead without a matching Zoho Recruit User is flagged for the customer to provision before the Job Opening import phase. Until the user is provisioned, the job is assigned to the Zoho Recruit admin user and the original owner is preserved in a custom field jazzhr_hiring_lead__c for audit.

JazzHR workflows define stages per job via workflow_id. Each unique JazzHR workflow configuration maps to a Zoho Recruit pipeline workflow. Stage names and order are preserved; stage probability percentages migrate to Zoho Recruit's stage weight fields if the destination plan supports them. If Zoho Recruit's pipeline count on the destination plan is insufficient for the number of unique JazzHR workflow_ids, we consolidate by role type and flag the overlap for the customer to resolve post-migration.

JazzHR custom fields on candidate profiles, including the startDate field (camelCase key, YYYY-MM-DD format), are pre-created as matching custom fields in Zoho Recruit before any record insert. Other account-specific custom fields are enumerated during scoping, typed (text, date, picklist, number), and created via Zoho Recruit's field management UI or API. We validate that picklist values in JazzHR map to existing Zoho Recruit picklist options and flag any mismatches for the customer to resolve before migration.

JazzHR document attachments are base64-encoded blobs delivered via the Candidate Export Webhook. These must be streamed immediately because the document URLs expire 2.5 hours after the export event fires. We decode the base64 payload, derive the MIME type from the source metadata, and upload to Zoho Recruit's document storage as a ContentDocumentLink attached to the parent Candidate record. We do not queue attachments for later processing.

JazzHR source and referral fields (free-text and codified strings) are preserved and mapped to Zoho Recruit's Candidate Source picklist. Where the JazzHR source value has no matching Zoho Recruit picklist option, we create a new picklist value during field setup to avoid data loss. Referral information is stored in a custom text field jazzhr_referral__c on the Candidate record if Zoho Recruit's standard fields do not accommodate the value.

JazzHR user accounts (recruiters, hiring managers, admins) are enumerated during scoping. Active JazzHR users map to active Zoho Recruit users by email. We flag any JazzHR user referenced on a record but not present in the destination as a user-provisioning gap. Zoho Recruit's role-based access (Recruiter, Hiring Manager, Admin) is assigned based on the JazzHR user's role, with the customer confirming the mapping during scoping.

JazzHR job board codes identify which job boards a job was posted to (Indeed, LinkedIn, ZipRecruiter, etc.). We capture the board code list per job and store it as a custom text field jazzhr_board_codes__c on the Job Opening so the customer knows which boards were active. We do not recreate job board connections during migration; the customer must re-establish board integrations in Zoho Recruit post-migration.

JazzHR education records include institution, degree type, field of study, and dates. The educationLevelCodes enum (36 codified values) is mapped to Zoho Recruit's candidate education fields where a matching option exists, or stored as a custom picklist value. We migrate all education history entries per candidate as individual education sub-records to preserve the full academic background.

JazzHR notes attached to candidate profiles migrate as Zoho Recruit Notes linked to the corresponding Candidate record. We preserve the note author (resolved via email to Zoho Recruit User) and the creation timestamp. Notes containing HTML formatting are migrated as rich text to preserve structure.

JazzHR interview feedback and scorecards attached to prospects map to Zoho Recruit Interview Feedback Forms on the related Application. If the source scorecard uses a rating scale not natively supported by Zoho Recruit, we store the raw score in a custom number field and note the original scale in a description field. Feedback text migrates as-is to the feedback form response.