Migrate from JazzHR to Recruit CRM & ATS

JazzHR Jobs (title, location, description, salary range, status, department, hiring_lead_id, board codes) map to Recruit CRM Job records. The job_id in JazzHR is the top-level container. We preserve the active/inactive status and department taxonomy from JazzHR and map the hiring lead reference to a corresponding user in Recruit CRM. Board codes identifying original job board posts are stored as a custom text field for reference rather than recreated as active connections.

JazzHR Candidate profiles (name, email, phone, address, work history, education with educationLevelCodes) map directly to Recruit CRM Candidate records. Education level codes from JazzHR (36 enumerated values) are stored as a custom picklist field in Recruit CRM. The startDate custom field (camelCase key, YYYY-MM-DD formatting) migrates to a custom date field on the Candidate record. We resolve email deduplication using the candidate's email address as the unique key.

JazzHR Prospects represent the candidate-to-job association with status, source, referral, and apply date. prospect_id is the join key. We create a corresponding pipeline entry in Recruit CRM linking the Candidate to the Job, preserving the original status (new, screened, interviewed, offered, hired, rejected), source, and referral information. The apply date migrates as the submission timestamp.

JazzHR document attachments are returned as base64-encoded blobs via the Candidate Export Webhook with MIME type. Document URLs expire 2 hours and 30 minutes after the export event fires. We stream all documents immediately upon receipt, decode the base64 payload, and upload to Recruit CRM as candidate attachments before URL expiry. This requires immediate processing rather than batch queuing.

JazzHR Departments are returned as a filterable entity in the Jobs API and define the organizational taxonomy for job assignments. We migrate the full department list and preserve the job-to-department assignments in Recruit CRM's department or team configuration.

Every JazzHR job carries a hiring_lead_id tied to a user account. We extract all hiring_lead_id references and remap them to corresponding users in Recruit CRM by email match. If no matching user exists in Recruit CRM, we assign the record to a designated migration admin user and flag the entry in the reconciliation report for the customer to update post-migration.

JazzHR supports custom fields on profiles and candidate exports. The startDate field uses a specific camelCase key and YYYY-MM-DD formatting. Other custom fields vary by account. We inventory every distinct custom field during scoping, map each to an equivalent custom field in Recruit CRM, and preserve the original field values. Account-specific custom fields that have no equivalent in Recruit CRM are stored as custom text properties with a naming prefix indicating their JazzHR origin.

JazzHR source and referral fields on prospect records are free-text and codified strings. We preserve them as-is and map them to Recruit CRM's equivalent source and referral fields. If Recruit CRM does not have a matching field for a specific source value, we store it as a custom property on the candidate record.

JazzHR workflows define the stages a candidate moves through per job. Custom workflow IDs (workflow_id) are required when creating jobs via API. We map the full stage sequence and stage names to Recruit CRM pipeline stages. We deliver a written stage-by-stage mapping document rather than configuring Recruit CRM workflows directly; the customer's admin applies the mapping during Recruit CRM onboarding.

Each JazzHR job carries board codes identifying where it was posted (Indeed, LinkedIn, ZipRecruiter, etc.). We do not recreate job board connections during migration since Recruit CRM manages job distribution separately. We flag which boards were active on each job as a custom text property so the customer knows which job boards to reconnect in Recruit CRM after migration.