Migrate from JazzHR to BambooHR

JazzHR Jobs map to BambooHR Job Openings. The JazzHR job title, location, department, description, and status map to BambooHR Job Opening fields. The hiring lead (hiring_lead_id) remaps to a BambooHR Employee record. Active job caps on the destination BambooHR plan (5 on Core, 25 on Pro, 50 on Elite) must be verified before migration because BambooHR does not allow unlimited openings on any tier. Archived JazzHR jobs can be migrated as closed records if historical data preservation is required, or excluded from the active count.

JazzHR Prospects (the candidate-job association record) map to BambooHR Applications. The prospect status (applied, screened, interviewed, offered, hired, rejected) maps to the BambooHR Application status. The source field and referral field from JazzHR preserve as metadata on the BambooHR Application. prospect_id is the join key between Candidates and Jobs and is preserved in a custom field jh_prospect_id__c for audit and reconciliation.

JazzHR Candidate profiles map to the personal data section of the BambooHR Application record. Name fields, email, phone, address, work history (as free-text or structured depending on field availability), and education history map directly. JazzHR's education level codes (36 enumerated values) must be normalized to text during transformation because BambooHR education fields use open text rather than codified values. Custom fields on the JazzHR profile (including startDate with its specific camelCase key and YYYY-MM-DD formatting) migrate to BambooHR custom fields on the Application.

Resume files and document attachments on JazzHR candidate profiles migrate as files on the BambooHR Application. JazzHR's Candidate Export Webhook delivers documents as base64-encoded blobs with a MIME type, and these URLs expire 2 hours and 30 minutes after the export event fires. We stream and decode all documents immediately upon receipt, uploading to BambooHR storage within the expiry window. Resume files map to the primary resume field on the Application; additional documents attach as supporting files.

JazzHR Departments migrate as a BambooHR Department entity. Job-to-department assignments in JazzHR map to the Department field on BambooHR Job Openings. If the destination BambooHR account has a pre-existing department taxonomy, we reconcile against it and merge rather than duplicate. Any departments referenced on JazzHR jobs that do not exist in BambooHR are created during the migration phase before job imports begin.

JazzHR hiring_lead_id references a user who owns the job. We resolve the hiring lead email against the BambooHR Employee directory and assign the BambooHR Employee record as the Job Opening owner. If no matching BambooHR Employee exists for the hiring lead, we assign the job to a designated migration administrator and flag the record for the customer to reassign post-migration. JazzHR user accounts with no corresponding BambooHR employee record require the customer to provision those employees before job assignment migration.

JazzHR workflow stages define the sequence a candidate moves through per job. Each JazzHR workflow_id maps to a BambooHR Hiring Stage configuration. Stage names and ordering are preserved, and we generate a written stage mapping document for the customer to configure the equivalent Hiring stages in BambooHR if they differ from the source. We do not recreate the workflow trigger logic; the stages are migrated as data, and BambooHR's stage progression is handled by the customer's admin post-migration.

JazzHR source and referral fields on the Prospect record are free-text or codified strings. We preserve them as-is and map to the BambooHR Application source field. If the destination BambooHR account uses a restricted source picklist, any source values that do not match the picklist options are stored in a custom text field jh_original_source__c for reference.

JazzHR job board codes (Indeed, LinkedIn, ZipRecruiter, etc.) identify where a job was syndicated. BambooHR has no job board code field. We extract the active board codes per job, store them as a comma-separated custom field jh_board_codes__c on the BambooHR Job Opening, and flag which boards were active so the customer can re-establish job board connections manually in BambooHR. The board integrations themselves do not migrate.

JazzHR supports custom fields on candidate profiles with values that vary by account. We map these to BambooHR custom fields on the Application object. BambooHR requires that dropdown field values exactly match the enumerated options defined in the destination account; any value in JazzHR that does not match is flagged and either normalized to the closest BambooHR option or placed in a free-text catch field. startDate uses the specific camelCase key and YYYY-MM-DD format from JazzHR and is mapped to a BambooHR date custom field.

JazzHR user accounts (recruiters, hiring managers, admins) with access to the ATS do not have a direct BambooHR equivalent as standalone ATS users because BambooHR assigns access based on the Employee record and HR role model. We extract all JazzHR user records, match them to BambooHR Employees by email, and assign the corresponding BambooHR Hiring permissions (can view jobs, can manage hiring, etc.) post-migration. Users who had ATS access in JazzHR but no BambooHR Employee record are flagged for the customer to provision.

JazzHR interview scorecards and interviewer feedback are stored as structured data on the candidate record. BambooHR's Application object does not have a native scorecard structure. We extract all scorecard responses and interviewer notes, format them as structured text, and attach them as internal notes on the BambooHR Application. The customer may choose to rebuild formal scorecards in BambooHR's Feedback feature post-migration if the structured format is critical to their hiring process.