Migrate from JobDiva to BambooHR

JobDiva Candidates split into two BambooHR record types based on employment status. Active placed Candidates (those with a completed placement or start date) migrate to BambooHR Employee records with employment dates, job title, department, and compensation fields. Unplaced Candidates who are still in the recruiting pipeline migrate to BambooHR Applicant records in the ATS module. The original candidate source (LinkedIn, job board, VMS) from JobDiva's parsed resume metadata migrates as a custom text field on the Employee or Applicant record for audit purposes.

JobDiva CRM Contacts (hiring managers, client relationships, company affiliations) migrate to BambooHR Employee records when they represent internal HR contacts or to a separate contacts export when they represent external client contacts without an employee record. We separate internal from external during scoping by checking the contact's associated Company affiliation against BambooHR's organizational hierarchy.

JobDiva Company records map to BambooHR's Company Directory entries. Each JobDiva Company with multiple associated Contacts migrates as a single Company entry with the primary address, industry, and size fields populated. Associated Contacts attach via BambooHR's employee directory linking rather than a separate Contact object. Client Companies without any active placed candidates become archived Company entries.

JobDiva Job orders (requisitions with pipeline stages, assigned recruiters, and requirements) have no direct BambooHR equivalent because BambooHR's ATS module tracks Applicants against Job requisitions but does not support multi-stage pipeline tracking, recruiter assignment, or client billing tied to job orders. We export Job records as a CSV inventory delivered to the customer's admin for manual reference or rebuild in BambooHR's Jobs module if the ATS add-on is purchased.

JobDiva Submittals (candidate submissions to specific job orders with status transitions and interview outcomes) do not have a direct equivalent in BambooHR. The Submittal record's status history, submission date, and interview outcomes attach to the migrated Applicant record as custom fields or as a linked notes document. Custom submittal status values defined per organization are extracted during scoping and mapped to BambooHR ATS status equivalents (Applied, Interview, Offer, Hired, Rejected) based on the customer's status mapping table.

JobDiva interview schedules (candidate, job, interviewer, date/time, outcome) migrate to BambooHR ATS Interview records linked to the corresponding Applicant. The interview date, interviewer name, and outcome migrate as structured fields. JobDiva interview rounds (first, second, final) map to a custom interview type field in BambooHR.

JobDiva Hotlists (curated candidate lists for specific roles or talent pools) have no BambooHR equivalent. We extract Hotlist membership during scoping and deliver it as a tagged candidate report where each candidate record carries the Hotlist name as a custom tag field. The customer's admin rebuilds active recruiting hotlists as BambooHR ATS candidate tags or as static candidate lists manually maintained post-migration.

JobDiva resume files (PDF, DOCX) stored as binary attachments migrate to BambooHR file storage linked to the corresponding Employee (for placed candidates) or Applicant (for active candidates). Resume parsing metadata (skills, work history, education) extracted from JobDiva's parsed resume fields migrates as structured data into BambooHR's employee or applicant record fields and as an attached parsed-summary document for reference.

JobDiva user-defined fields on Candidates, Jobs, Submittals, and other objects are extracted during scoping and mapped to BambooHR custom fields. BambooHR supports custom fields on Employee, Job, and Dependent objects via the API. We create the destination custom fields before migration, map their types (text, date, number, dropdown), and migrate the values. Any user-defined fields on recruiting objects (Jobs, Submittals) with no BambooHR equivalent are archived to a custom fields inventory document.

JobDiva Owners (assigned recruiters, sales reps, account managers) map to BambooHR Employee records with User access. We resolve owners by email match against the BambooHR User table. Any JobDiva Owner without a matching BambooHR User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

JobDiva Timesheet records (hours worked by placed candidates, tied to billing configuration) have no direct BambooHR equivalent because BambooHR's Time Off module tracks employee time-off requests rather than contractor timesheets. We export timesheet records as a CSV deliverable for the customer's billing or payroll system. If BambooHR Payroll is active, timesheet export is formatted for import into that module as a separate post-migration step.

JobDiva CRM Sales Pipelines (configurable stages for business development tracking) have no BambooHR equivalent since BambooHR is not a sales CRM. Pipeline stage names and deal associations are extracted as a CSV inventory delivered to the customer's admin for reference. The customer may choose to import this as custom fields on Employee records or archive it as a reference document.