Migrate from JobDiva to Bullhorn ATS & CRM

JobDiva Candidates map directly to Bullhorn Candidates. We extract parsed resume fields (skills, employment history, education, certifications) and map them to Bullhorn Candidate attributes and custom fields. Resume binary files (PDF/DOCX) attach to the Candidate record via Bullhorn's attachment model. If a JobDiva Candidate has a parsed record but no attached file, we flag that gap during scoping and the customer chooses whether to re-parse in Bullhorn post-migration or retain the structured fields as-is.

JobDiva CRM Contacts map to Bullhorn Contacts, which are separate from Candidates. The Contact stores hiring manager information, client relationships, and company affiliations. We preserve contact attributes and their associated company linkage at the destination. JobDiva Contacts and Candidates are distinct objects with different schemas; we do not merge them unless the customer specifically requests a unified model in Bullhorn.

JobDiva Companies map to Bullhorn ClientCorporation. Company records with multiple associated Contacts migrate with the company-contact relationship graph preserved through Bullhorn's ClientCorporation-to-Contact link. The JobDiva company record is the primary key for client-level data including address, industry, and billing configuration.

JobDiva Job orders map to Bullhorn JobOrder, which tracks open requisitions with status, requirements, assigned recruiters, and the hiring manager reference. The JobOrder is the parent object for all candidate submissions in Bullhorn. We map job status values to Bullhorn JobStatus equivalents (Open, Placed, Cancelled, On Hold) and preserve requirements, pay rates, and shift details.

This is the most significant structural mapping in a JobDiva-to-Bullhorn migration. JobDiva's Submittal is a single object tying a Candidate to a Job with status and interview data. Bullhorn splits this into JobSubmission (the submission event, including submission date, status, and submission notes) and CandidateWorkHistory (the employment record when a placement occurs, including start date, end date, pay rate, and bill rate). We split each JobDiva Submittal into two Bullhorn records linked by Candidate and JobOrder references. Submittal status values from JobDiva map to Bullhorn JobSubmission status values using the organization's custom status mapping table built during scoping.

JobDiva interview schedules associated with Submittals map to Bullhorn Interview records. Each Interview links to the corresponding Candidate and JobSubmission. We preserve interview date/time, interviewer reference, location, outcome status, and any interviewer notes. If JobDiva stores interview scorecards or rating data as user-defined fields, we map those to Bullhorn custom Interview fields.

JobDiva user-defined fields exist on Candidates, Jobs, Submittals, Contacts, and Companies. We extract the complete UDF schema during scoping, including field names, data types, and picklist values where applicable. We pre-create Bullhorn custom fields in the customer's Bullhorn instance before any record migration begins, matching field types (text, number, date, picklist, checkbox) and preserving any picklist value sets from JobDiva UDFs.

JobDiva Hotlists are curated candidate lists with ordered membership. Bullhorn has no direct hotlist object; we map Hotlists to Bullhorn Lists with candidate membership and ordered sequence preserved. Each List in Bullhorn receives the original Hotlist name and its ordered member set. Hotlist membership changes are not live-synced post-migration; we deliver a written list of active Hotlists with their candidate rosters for the customer's admin to rebuild as automated Lists or manual working lists in Bullhorn.

JobDiva's CRM Sales Pipeline stores business development deals with configurable stages tracked separately from the ATS job pipeline. These map to Bullhorn Opportunities in the CRM layer. Each JobDiva deal stage becomes a Bullhorn Opportunity Stage value remapped via a stage mapping table. We preserve original stage names in a custom field so the customer's admin retains the source pipeline terminology for reporting continuity. Note that Bullhorn Opportunities are CRM objects distinct from the ATS JobOrder pipeline.

JobDiva CRM Leads map to Bullhorn Leads for early-stage prospects not yet attached to a JobOrder. We preserve lead status, source, and rating. We run a dedupe check against existing Bullhorn Candidates before inserting to prevent duplicate records since Bullhorn can auto-create Candidates from Leads. The customer's Bullhorn admin configures the dedupe rule (email-based or other) before migration.

JobDiva Events map to Bullhorn Activity records with timestamps, linked entities (Candidate, Job, Contact), and reminder settings preserved. Event type (meeting, call, reminder) maps to Bullhorn Activity type. Calendar sync settings do not migrate; we restore them post-migration through Bullhorn's native calendar integration configuration.

JobDiva email engagements migrate to Bullhorn Email records linked to the corresponding Candidate, Contact, or JobOrder. Email body content, timestamp, direction (sent/received), and associated user (owner) transfer to Bullhorn's standard email fields. Email attachments migrate as file attachments on the email record.

JobDiva call engagements migrate to Bullhorn Task records with TaskSubtype set to Call. Call duration, disposition, outcome notes, and original timestamp transfer to Bullhorn Task fields. We set the Task status and link it to the associated Candidate or Contact by resolving the JobDiva owner and candidate references.

JobDiva meeting engagements map to Bullhorn PlacementInterview records for scheduled interview events or to Activity records for general meetings. The mapping depends on whether the meeting is tied to a candidate-job submission (PlacementInterview) or a general client/candidate interaction (Activity). We distinguish based on the presence of a job reference in JobDiva's meeting record.

JobDiva notes migrate to Bullhorn Note records linked via ContentDocumentLink to the parent Candidate, Contact, ClientCorporation, or JobOrder. Rich text formatting in JobDiva notes converts to plain text with inline styling preserved where Bullhorn's Note model allows. Note timestamps and owner references transfer to maintain the activity timeline.

JobDiva timesheet records track hours worked for placed candidates. Bullhorn Middle Office handles timesheet capture, compliance, and invoice generation as a separate product tier. If the customer licenses Bullhorn Middle Office, we migrate timesheet records into that module. If not, timesheets map to custom fields on the Placement record or remain as a written inventory for the customer's payroll admin to reconstruct. We flag timesheet migration as conditional during scoping.