Migrate from JobScore to BambooHR

JobScore Candidate records map to BambooHR Employee records. Core fields (firstName, lastName, email, phone, address) migrate directly. Date fields (dateOfBirth, hireDate) map from JobScore's candidate birth date and accepted offer date. Ethnicity and gender migrate to BambooHR EEO fields if the destination account has EEO enabled. We reattach the candidate's resume and cover letter as Employee Document records under a 'Documents from JobScore' folder, matching the folder naming convention used by the native integration.

JobScore Applications (the join table between Candidate and Job) map to BambooHR's Hiring module. The application date becomes the candidate submission date in BambooHR's hiring pipeline. JobScore stage history (New, Active, Declined, Withdrawn, Hired) maps to BambooHR Hiring Status values. Custom application form field responses stored at the Application level migrate as BambooHR custom employee fields with types preserved (text, date, dropdown, checkbox).

JobScore published Jobs map to BambooHR Job Openings. Only published jobs appear in JobScore's API and job feeds — we scope the export to the published set and flag any Draft or Unpublished jobs for manual capture. Job title, location, and department migrate to BambooHR's Job Opening fields. Active vs filled vs closed status maps to BambooHR's open/closed Hiring status.

JobScore Interview records (date, interviewer assignment, interview type, outcome) have no direct BambooHR object equivalent. We migrate interviews as structured notes on the Employee record, preserving the date, interviewer name, interview type, and outcome text. This keeps interview history accessible on the employee profile in BambooHR after migration.

JobScore Scorecards (interviewer ratings, comments, and evaluation forms) have no direct BambooHR object equivalent. We export scorecard data as structured notes or as PDF file attachments on the Employee record, depending on whether the scorecard contains rich formatting. The parent Interview reference is embedded in the note body so the evaluation chain is reconstructable.

JobScore custom application form fields (created per job) store responses at the Application level. We extract the full custom field schema from the source account, map field types to their nearest BambooHR custom employee field equivalents (text, date, dropdown, checkbox, number), and pre-create the custom fields in BambooHR before application data loads. Dropdown values migrate as list options.

JobScore Tags are freeform labels applied to Candidates with unlimited tagging. We extract all tag associations and store them as a comma-separated text field on the Employee record in BambooHR. For customers with fewer than 50 distinct tags, we evaluate whether a multi-select picklist is feasible based on BambooHR's field type support.

JobScore Location records (address, city, state, country) map directly to BambooHR Locations. Location is assigned at the Job level in JobScore and at the Employee level (via Job Info) in BambooHR. We map JobScore Locations to their BambooHR equivalents during job migration and attach the correct location to the corresponding Employee record post-hire.

JobScore Users assigned as interviewers, owners, or recruiters are mapped by email to BambooHR Employee records. BambooHR uses email as the user identifier. Any JobScore user without a matching BambooHR Employee goes into a reconciliation queue for the customer's admin to provision before record import. We preserve the interviewer assignment on Interview notes migrated to the destination.

JobScore document blobs (resumes, cover letters) are exported as binary files and reattached to the corresponding BambooHR Employee record. File type (PDF, DOCX, RTF) is preserved. The native integration creates a 'Documents from JobScore' folder — we use the same folder convention to avoid creating duplicate structures. Documents without a matched Employee record are held in a document queue for manual resolution.