Migrate from Sloneek to Bullhorn ATS & CRM

Sloneek employee profiles map to Bullhorn Corporate User records for internal staff and to Candidate records for employees who are also being tracked as talent in the Bullhorn system. Standard fields (name, email, phone, department, job title) map to Bullhorn user fields. We resolve the Bullhorn Corporate User by email match and create any missing user accounts in the reconciliation queue before record import. Custom fields on Sloneek employee profiles migrate to Bullhorn User custom fields.

Sloneek ATS Candidate records (from both ATS 1.0 and ATS 2.0 schemas if both exist) map to Bullhorn Candidate records. Sloneek's candidate name, email, phone, resume (as file attachment), GDPR consent flags, hiring pipeline stage, and notes transfer directly. We detect which ATS schema each Sloneek record belongs to at export time and route both schemas through the same Bullhorn Candidate import. Sloneek's GDPR consent storage (consent date, consent type, consent version) maps to Bullhorn custom fields on Candidate because Bullhorn does not have a native GDPR consent object.

Sloneek job positions and open requisitions map to Bullhorn JobOrder records. Fields including job title, job description, location, employment type (full-time, contract, part-time), and salary range transfer to Bullhorn JobOrder fields. JobOrder status (open, filled, closed) maps to Bullhorn's status field. If Sloneek job positions are tied to specific ATS pipeline stages, we map those to Bullhorn JobOrder status and a corresponding Bullhorn custom field.

Sloneek's recruitment pipeline stages (application, screening, interview, offer, hired, rejected) map to Bullhorn's Rush Process stages. We configure the Rush Process in Bullhorn during the schema setup phase to match the Sloneek pipeline exactly. Each Sloneek stage maps to a corresponding Rush Process status value with the same order index preserved.

Sloneek employee documents and candidate resume files migrate to Bullhorn. Bullhorn supports multiple file types (unlike Sloneek's PDF-only restriction), so we transfer files in their original format. We flag any Sloneek PDF documents that the customer uploaded in a non-standard way (scanned images embedded in PDF, password-protected PDFs) for pre-migration remediation. Resume files attach to the Bullhorn Candidate record via ContentDocumentLink.

Sloneek departments, cost centers, and org chart hierarchies map to Bullhorn Corporate Department records. Employee reporting lines (manager relationships) transfer to Bullhorn User managerId references. Bullhorn's org structure is simpler than Sloneek's; if the Sloneek tenant uses multi-level cost center hierarchies, we flatten them to a single department level in Bullhorn and document the original hierarchy for the customer's admin to rebuild as Bullhorn custom fields or a separate organizational chart tool.

Sloneek attendance data is currently split between the old attendance schema and Attendance 2.0 in active tenants. We detect which schema applies to each attendance record at export time and map both schemas to a Bullhorn custom attendance object or the Bullhorn Time module if the customer licenses it. Attendance 2.0 fields (clock-in, clock-out, break duration, overtime flag) map to custom fields in the destination. Old schema fields map to equivalent custom fields where possible; we flag any fields with no Bullhorn equivalent during scoping.

Sloneek time-off balances, absence requests, leave type classifications, and accrual history map to a Bullhorn custom Absence object or to note records on the Corporate User if no custom object is configured. Leave type (vacation, sick, personal) maps to a Bullhorn custom picklist field. Accrual balances transfer as of the migration date; we flag that future accrual calculation resets in Bullhorn and recommend the customer's admin sets accrual rules post-migration.

Sloneek salary, bonus, and payroll history (available on higher plan tiers) map to Bullhorn Candidate custom fields or Placement record fields if the candidate has a placement in Bullhorn. We map current salary, salary currency, and pay frequency to Bullhorn custom fields on Candidate. Historical pay changes migrate as separate dated entries if the customer requires full compensation history; otherwise, only the most recent compensation record migrates.

Sloneek 360-degree feedback records, goals, and completed review cycles map to a Bullhorn custom Performance Review object or to note records attached to the Corporate User. Draft or in-progress reviews are flagged as not migrating because they require an active Sloneek session to finalize. Completed review ratings migrate to Bullhorn custom fields with a review date and reviewer reference; the customer's Bullhorn admin rebuilds the review template structure post-migration.

Sloneek custom fields on employee profiles, candidate records, and ATS objects migrate to Bullhorn custom fields on the corresponding Bullhorn object. Bullhorn supports text, number, date, picklist, and reference (lookup) field types. We discover the full custom field schema during scoping, map each to a matching Bullhorn field type, and pre-create fields in the Bullhorn destination org before any data import begins. Any Sloneek custom fields without a Bullhorn equivalent are documented in the migration scope with a recommended workaround.

Sloneek company assets assigned to employees (equipment, access cards, licenses) map to Bullhorn Corporate User custom fields or note records. We export the asset-to-employee assignment mapping and recreate it in Bullhorn as a comma-separated list in a custom text field or as separate note records per asset. The customer may prefer to manage asset tracking in a dedicated ITAM tool post-migration; we document the asset assignment data for that decision.

Sloneek time entries (where used for project billing or timesheet tracking) map to Bullhorn Time module if licensed, or to a custom timesheet object. We map employee, project, date, hours, and entry type to Bullhorn custom fields. If the customer does not license Bullhorn Time, we deliver a written export of all time entry records that the customer can import into a third-party timesheet tool.

Sloneek approval chains for time-off requests, document signing, and expense approvals do not migrate. Bullhorn's workflow model differs structurally from Sloneek's. We document every active Sloneek approval chain (trigger, approver chain, conditions, actions) in a written inventory delivered to the customer's admin. The admin or a Bullhorn partner rebuilds approval rules in Bullhorn Workflow or a Bullhorn-certified automation tool post-migration.