Migrate your JazzHR data

Jobs is the top-level container in JazzHR, carrying title, location, description, salary range, status, department, hiring lead, and board codes. The API returns all standard fields as documented and stable. We migrate Jobs with their associated workflow and stage metadata intact.

Prospects represent the candidate-job association with a status, source, referral field, and apply date. The prospect_id is the join key between candidates and open positions. We migrate Prospects preserving the linked job_id and the workflow step at time of export.

Candidate profiles include name, email, phone, address, work history, education with codified education levels (36 enumerated values), and a startDate custom field if set. The educationLevelCodes enum is explicit and migrates as-is. We extract all standard profile fields and map them to destination schema.

Documents attached to candidate profiles are returned as base64-encoded blobs with a MIME type via the Candidate Export Webhook. Document URLs expire 2 hours 30 minutes after the export event fires. We handle this by streaming attachments immediately after export rather than queuing them separately.

JazzHR supports custom fields on profiles and candidate exports. A startDate custom field uses a specific camelCase key (startDate) and YYYY-MM-DD formatting. Other custom fields vary by account. We enumerate and map each custom field explicitly before writing to the destination.

Departments are returned as a filterable entity in the Jobs API. We migrate the department taxonomy so job-to-department assignments are preserved in the destination system.

Every job has a designated hiring_lead_id tied to a user. We migrate the hiring lead reference and remap it to the corresponding user in the destination system. If no matching user exists, we assign it to the migration owner and flag it for review.

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 the destination pipeline structure, merging or creating stages as needed.

The source and referral fields on a prospect record are free-text and codified strings. We preserve them as-is and map them to the destination's equivalent fields or store them as custom properties.

Each job carries board codes identifying where it was posted (Indeed, LinkedIn, ZipRecruiter, etc.). We do not recreate job board connections during migration but flag which boards were active so you can re-syndicate after cutover.