Migrate from ELMO Suite to Bullhorn ATS & CRM

ELMO Employee records map to Bullhorn Candidate. Core fields (name, email, phone, address, employment type, start date) map directly to Candidate standard fields. The ELMO employment status (active, inactive, terminated) maps to Candidate status values. Any ELMO employee who is also a job applicant in the recruitment module migrates as a Candidate record with employment history carried as a Candidate custom object or note. The migration direction determines whether the Employee record is the primary artifact: if the destination is a staffing firm with Bullhorn as their ATS, Candidates are the primary record. We flag employees without recruitment context for manual Bullhorn User provisioning.

ELMO Employees who are internal recruiters, HR staff, or administrators map to Bullhorn Corporate Users. We resolve the mapping by email match. Any ELMO employee without a matching Bullhorn User goes to a reconciliation queue for the customer's Bullhorn admin to provision. OwnerId on Candidate and Job records must resolve to an active Bullhorn User, so User provisioning is a gate before record migration.

ELMO Recruitment module applicant records map to Bullhorn JobSubmission (also called Job Application in Bullhorn UI). Application status, source, submission date, and interview scores transfer to Bullhorn JobSubmission fields. Position title and department assignments reconcile during the field-mapping phase against the target Job record.

ELMO recruitment job postings and position records map to Bullhorn Job. Job title, description, requirements, salary range, and status map directly to Bullhorn Job fields. The ELMO job type (permanent, contract, casual) maps to Bullhorn employmentType. We create Bullhorn Job records before JobSubmission records so that the JobOrder lookup is satisfied at insert time.

ELMO onboarding task lists and document checklists map to Bullhorn Onboarding (formerly Able) if the customer has the Bullhorn Onboarding add-on active. Task names, assignees, due dates, and completion status migrate as Onboarding task records. If Bullhorn Onboarding is not licensed, we create a custom object with task fields and flag the missing module for the customer's admin to activate or rebuild in Bullhorn.

ELMO payroll records (pay groups, pay rates, salary history, superannuation) have no native Bullhorn equivalent. Bullhorn is not a payroll engine; it handles contractor invoicing via the Back Office add-on but not payroll processing. We create Bullhorn custom objects (up to 2 on ATS Growth, 10 on Enterprise) to hold compensation and superannuation records linked to Candidate or Placement. TFN declarations and Super Fund details export as structured data. ANZ-specific fields are preserved with field labels intact for compliance audit.

ELMO leave entitlements, accrual rules, and balance snapshots are source-system values that must be reconciled against the destination's accrual engine. Bullhorn has no native leave management. We export the leave balance as of the migration date and create a Bullhorn custom object linked to Candidate to store entitlement types (annual, sick, long service), accrual rates, and current balances. Leave approval workflows are not migrated; they require a separate HRMS or leave management tool post-migration.

ELMO performance review cycles, objectives, goals, and appraisal ratings require a Bullhorn custom object because Bullhorn has no native performance management module. Rating scales, competency frameworks, and custom review forms vary significantly between ELMO organisations. We export review responses as structured records in a custom object and flag custom forms for post-migration manual reconciliation. If the customer uses fewer than 2 custom objects on ATS Growth or 10 on Enterprise, we scope which review data is highest priority for migration.

ELMO course completions, certifications, and skill profiles migrate to a Bullhorn custom object on Candidate. Custom learning paths and due dates require field-level mapping. Completion status and expiry dates are preserved. Bullhorn has no native LMS; the custom object approach preserves the learning record as a candidate skill and certification reference without requiring an external LMS integration.

ELMO departments, cost centres, and business units map to Bullhorn Corporate User department and division fields, or to a custom field on User if the Bullhorn edition supports it. Reporting lines and manager assignments preserve as manager links on User records. The Bullhorn org chart does not replicate ELMO's full hierarchical structure; we map the business unit layer that is relevant for ATS workflow routing.

ELMO engagement records (candidate interactions, interview notes, communications) map to Bullhorn Note, Task, or Appointment records linked to the Candidate. Activity timestamps and engagement types preserve. Bullhorn's API supports all standard engagement entities; we use batch processing with rate-limit handling to move large engagement volumes. Note rich text and attachment links migrate as ContentDocument with ContentDocumentLink to the Candidate.

ELMO expense claims, receipts, approval workflows, and reimbursement status migrate as expense records if the customer has Bullhorn Back Office active. Category codes and approval routing re-map to Bullhorn expense categories. If Back Office is not licensed, we create a custom object for expense records and flag the module gap.