Migrate from Jobsoid to Bullhorn ATS & CRM

Jobsoid Candidate records map directly to Bullhorn Candidate. The primary challenge is that Jobsoid has no Candidates write API: we export candidates via Jobsoid's native CSV or Excel export, parse all fields (name, email, phone, address, custom fields, skills, source attribution), then push into Bullhorn via the Bullhorn REST API. Jobsoid's multi-job assignment (one candidate assigned to multiple jobs with a designated primary) maps via JobSubmission records linking each Candidate-Bullhorn to the corresponding JobOrder-Bullhorn. We carry the primary job flag as a custom Candidate field candidate_primary_job_id__c and create JobSubmission records in dependency order (Candidates first, then JobOrders, then JobSubmissions).

Jobsoid Job records map to Bullhorn JobOrder. We extract title, description, status (open/closed/draft), employment type, and pay rate fields. Jobsoid's Job API exposes published jobs and job details; we map the source status to Bullhorn's jobStatus field (Open, Closed, Deleted, Draft, OnHold). The source job's linked Location and Department assignments carry over as JobOrder address and businessSectorLookupId references. JobOrder title and description transfer as-is; HTML-formatted descriptions are cleaned and re-rendered in Bullhorn's rich text fields.

Jobsoid Locations map to Bullhorn Location records. Jobsoid auto-resolves addresses via Google Maps; we preserve the full address string and geocoordinates where present. Bullhorn Location is a standard lookup entity used by JobOrder for placement and interview scheduling. We migrate all Locations before JobOrder import so that the LocationId reference is satisfied on insert.

Jobsoid Departments are organizational lookup values that categorize jobs and candidates. Bullhorn does not have a direct Department equivalent; we map departments to Bullhorn's BusinessSector lookup or, if the customer's Bullhorn org uses Divisions, to the corresponding Division. The customer chooses the strategy during scoping. We preserve the full department list and reassign affected JobOrders post-migration if the mapping requires adjustment.

Jobsoid Divisions represent top-level organizational units and map to Bullhorn Division records if the customer's Bullhorn edition includes division-level security. We migrate Division records first so that Department assignments can reference them. If Bullhorn Division is not enabled in the customer's tier, we map Division to a custom picklist field on JobOrder.

Jobsoid Functions categorize job types (e.g., Engineering, Sales, Operations) and map to Bullhorn Category. Jobsoid exposes Functions as lookup values; we carry them as Category records and link them to JobOrder via the categoryID reference. If a Jobsoid Function does not have a matching Bullhorn Category, we create the category during migration before JobOrder import.

Jobsoid tracks candidate source (job board, referral, direct application, etc.) as a field on the Candidate record. Source values migrate to Bullhorn Candidate's source field or to a custom source picklist. We map source values field-to-field but flag any unrecognized source labels that require a new picklist value in Bullhorn. If the customer uses custom source taxonomy in Jobsoid, we create the corresponding picklist values in Bullhorn before migration.

Jobsoid surfaces interviews, emails, and notes as an activity block within each candidate profile, but activities are not a standalone API resource. We extract activity text from candidate profile CSV or Excel exports, reconstruct a best-effort timestamped timeline per candidate, then push into Bullhorn as Task records (calls, emails, general tasks) and Event records (interview schedules). Interview date, time, location, interviewer name, and outcome notes transfer as separate fields on the Event. We flag this as a best-effort migration: the richer the source export, the more complete the Bullhorn activity timeline.

Jobsoid's pipelines are fully customizable with per-account stage names and counts. Bullhorn uses configurable status picklists tied to Record Types and Sales Processes. We normalize the source pipeline stages into a Bullhorn Record Type with a corresponding Sales Process that whitelists the relevant stage values. If the destination Bullhorn org has fewer stages than the source, we consolidate by mapping multiple source stages to a single destination stage; the customer approves the consolidation table during scoping. Stage probability percentages migrate to Bullhorn StageProbability values rounded to the nearest integer.

Jobsoid allows custom fields on candidate records; Bullhorn supports custom fields natively on Candidate. We map custom field values field-to-field where field names and data types match. Text fields map to Bullhorn text fields, date fields to date fields, and picklist fields to Bullhorn picklists. If a Jobsoid custom field has no Bullhorn equivalent, we create a matching custom field on the Candidate object before migration. Custom object types (entities rather than fields) require Bullhorn support ticket setup per the Bullhorn Custom Object documentation and are scoped separately.

Candidate profiles in Jobsoid include uploaded resumes and attachments. We relocate binary attachments separately from record data. Each attachment is downloaded from Jobsoid (via authenticated session for file retrieval), stored with a UUID referencing the source candidate ID, then uploaded to Bullhorn as a ContentDocument linked via ContentDocumentLink to the target Candidate record. Resume files are linked to the Candidate's primary resume field where Bullhorn exposes it. Attachment types, file names, and upload dates are preserved in the ContentVersion metadata.

Jobsoid integrates with email and calendar for interview scheduling; interview records appear as activities on the candidate profile. We migrate interview dates, times, locations, interviewer names, and interview type as Bullhorn Event records linked to the Candidate via EventRelation. Calendar invites and Zoom/Teams join links are not transferable across platforms and are flagged for the customer's admin to resend from Bullhorn after migration. We carry the original interview notes in the Event description field.

Jobsoid Owner records map to Bullhorn User. We match by email address. Any Jobsoid Owner without a matching Bullhorn User is held in a reconciliation queue for the customer's Bullhorn admin to provision before record import resumes. Inactive Jobsoid owners map to inactive Bullhorn users to preserve assignment history without generating live notifications.