Migrate from LogicMelon to Bullhorn ATS & CRM

LogicMelon Jobs map directly to Bullhorn JobOrder records. The job advert content (title, description, requirements, salary) migrates to Bullhorn's title, description, and publicDescription fields. Bullhorn JobOrder does not replicate the multi-posting action; instead, we preserve the list of targeted job boards from LogicMelon's per-job board-association list as Bullhorn tags on the JobOrder record. The original job reference ID from LogicMelon is stored in a custom field lm_job_id__c for audit and reconciliation.

LogicMelon Application records are the structural pivot point in this migration. Each LogicMelon Application references one Candidate and one Job. Bullhorn maintains a single Candidate record linked to multiple JobSubmission records (one per job applied to). We deduplicate LogicMelon Applications by candidate email and phone during extraction, create one Bullhorn Candidate, and generate a JobSubmission for each original application tied to the corresponding JobOrder. The application status (Applied, Screened, Interviewed, Offered, Placed) migrates to JobSubmission status with a reference back to the original LogicMelon application date and status transition history.

LogicMelon Candidate profiles (name, email, phone, skills, work history, location) map to Bullhorn Candidate. The Bullhorn Candidate is the canonical record created in the Application split step above. Structured profile fields migrate to typed Bullhorn Candidate fields; any fields that do not map directly become custom fields pre-created in Bullhorn before import. The original candidate reference lm_candidate_id__c is stored for reconciliation.

LogicMelon stores CVs as binary file attachments (PDF, DOCX) linked to Application or Candidate records. We extract the raw file and attach it to the Bullhorn Candidate record using Bullhorn's file attachment API. The CV file name and upload date are preserved. Bullhorn's resume parsing runs on the file after attachment, populating Bullhorn's standard resume fields (education, employment history, skills). We do not parse or transform CV content during extraction; the file is the source-of-truth backup where structured fields are incomplete.

LogicMelon organisation or client records map to Bullhorn ClientCorporation. If LogicMelon stores staffing-client details alongside candidate records, these migrate as ClientCorporation with billing contact, address, and industry. ClientCorporation is created before Candidate import so that the client reference on JobOrder is satisfied at insert time.

LogicMelon stores the list of targeted job boards as a per-job board-association object rather than a global posting template. Bullhorn has no native per-job board list object; we preserve this as Bullhorn tags on the JobOrder record (one tag per targeted board). Tags are created from the LogicMelon board list at migration time and appear on the JobOrder in Bullhorn. The multi-posting action itself is not replicated; tags serve as a record of original posting distribution for audit and reporting.

Recruiter screening notes, scoring, and evaluation comments attached to LogicMelon Applications migrate to Bullhorn Note records linked to the corresponding JobSubmission or Candidate. Bullhorn Note supports text content with timestamps and owner attribution. The original note type (screening score, shortlist reason, client feedback) is preserved in the note body or in a custom field lm_note_type__c if a structured type field exists in LogicMelon.

LogicMelon's configurable pipeline stages (Applied, Screened, Interviewed, Offered, Placed) map to Bullhorn JobSubmission status values. We extract the customer's specific stage name configuration during discovery, map each stage to the nearest Bullhorn status, and configure Bullhorn's JobSubmission status picklist accordingly. Any custom stage names that have no Bullhorn equivalent are added as custom status values or preserved in lm_stage_name__c on the JobSubmission.

LogicMelon Users are tied to the organisation hierarchy via API credentials (EMEA or US instance, scoped to sub-unit). We extract every User referenced on Jobs, Applications, and Notes, and match by email against Bullhorn's User table in the destination org. Users without a Bullhorn match enter a reconciliation queue for your admin to provision before record import resumes. Inactive LogicMelon users are mapped to inactive Bullhorn users to preserve historical assignment.

LogicMelon's multi-tenant hierarchy (agency-level versus client-level sub-units) maps to Bullhorn's Corporate User structure. If Bullhorn Enterprise or higher is in use, we map LogicMelon sub-units to Bullhorn Divisions. If Professional is the destination tier, we document the hierarchy for your admin to configure post-migration in Bullhorn's Settings > Corporate Structure.

LogicMelon talent pools (grouped candidate collections for active or passive sourcing) map to Bullhorn Candidate Lists. We extract the talent pool name, membership, and any pool-level notes, and create Bullhorn Candidate List records with the original members linked. Talent pool category or tag assignments migrate as Bullhorn Candidate tags for ongoing segmentation.

LogicMelon allows custom fields on Jobs and Applications. We identify all active custom fields during discovery, map them to Bullhorn custom fields on the corresponding entity (JobOrder, JobSubmission, or Candidate), and pre-create the Bullhorn schema (including field type, picklist values, and visibility settings) before migration begins. Any custom fields that exceed Bullhorn's field count limits per entity are flagged in the discovery report for your admin to resolve.