Migrate from ClearCompany to Bullhorn ATS & CRM

ClearCompany Candidate records map directly to Bullhorn Candidate. We map name fields, contact information, address, employment history, education, skills, and custom fields. Candidate status from ClearCompany (applied, screening, interview, offer, hired, rejected) maps to a Bullhorn Candidate status field or custom picklist. The candidate's source and the associated Job reference migrate to preserve submission history. Bullhorn's Candidate object uses a numeric candidateID as the primary key; we use this as the reference anchor for all child records.

ClearCompany Employees do not have a direct Bullhorn equivalent because Bullhorn is a recruiting and staffing ATS, not an HRMS. We handle this gap by creating a Bullhorn custom object or using a custom field set on the Candidate record to store historical employee data for clients who use ClearCompany for both ATS and HRMS functions. We confirm during scoping whether the customer needs to track internal employees in Bullhorn or will use a separate HRIS. Department, manager, start date, and employment status migrate as custom fields on the appropriate entity.

ClearCompany Job records map to Bullhorn JobOrder. We map title, department, location, employment type (full-time, contract, temp), status, description, and requirements. ClearCompany's job status (open, on hold, filled, cancelled) maps to Bullhorn JobOrder status. The job-to-candidate association migrates to preserve historical submissions as JobSubmission records in Bullhorn, linking the Candidate to the JobOrder with submission date and status.

ClearCompany organizational units (departments, offices, divisions) have no native Bullhorn equivalent. We map departments to Bullhorn custom fields on JobOrder and ClientCorporation, or to a Division field if the Bullhorn edition supports it. For customers with complex org hierarchies, we create a department reference table and attach it as a custom entity or picklist. We preserve parent-child relationships in a separate mapping document for the customer's admin to configure in Bullhorn's settings.

ClearCompany User accounts (with role, permissions, and active/inactive status) map to Bullhorn User records. We match by email address. Bullhorn User records include firstName, lastName, email, ownership, and a status field. The Bullhorn migration team must provision the destination users before migration; any ClearCompany user without a matching Bullhorn User goes to a reconciliation queue. Role names from ClearCompany map to Bullhorn permission roles, with a role-mapping table provided during scoping.

ClearCompany onboarding task checklists and new-hire workflows are not transferable as automation logic to Bullhorn Onboarding (built on Able Teams). We export task definitions, completion status, and task assignees as records in a flat task table. The customer decides whether to rebuild the workflow logic in Bullhorn Onboarding or to use the task records as a one-time checklist. Conditional branching and completion triggers from ClearCompany do not migrate as logic; we document the workflow structure for the customer's Bullhorn admin to configure.

ClearCompany performance review records, goals, and calibration data have no native Bullhorn equivalent. We export the review data as records in a Bullhorn custom object or attach as Notes to the relevant Employee or Candidate record, depending on whether the customer uses Bullhorn for internal hiring, external recruiting, or both. Review templates and rating scales do not migrate; we deliver a template map for the customer to configure in Bullhorn's custom field builder or a connected performance tool.

ClearCompany LMS content (courses, learning paths, completion records, compliance data) does not have a Bullhorn equivalent because Bullhorn has no native LMS. We export completion records and compliance data as custom fields on the relevant Candidate or Employee record. SCORM packages are flagged during scoping for explicit customer decision: import as-is to a document repository (Bullhorn's Document Uploads or an external storage), or convert to a destination-native format if the customer adopts a separate LMS. Learning path logic and curriculum dependencies do not migrate.

If the ClearCompany ATS module includes an inbound Lead concept, it maps to Bullhorn Lead. Bullhorn Lead tracks prospect company, contact name, status (new, contacted, qualified, unqualified), source, and owner. We resolve the Lead status from ClearCompany's lead stage and map the owner to the Bullhorn User by email. Bullhorn Leads convert to ClientCorporation and ClientContact records when the prospect becomes an active client.

ClearCompany does not have a separate client CRM object; client-related data may exist as company and contact information within Job or Candidate records. We extract client-type records and merge them into Bullhorn ClientCorporation (the company entity) and ClientContact (the person at that company with name, title, phone, email). The ClientCorporation address, industry, and status map to Bullhorn fields. Multiple client contacts associated with the same company merge into ClientContact records linked to a single ClientCorporation.

If the ClearCompany instance tracks placements (offers accepted, candidates hired, start dates), these map to Bullhorn Placement. We map job title, client (ClientCorporation), candidate (Candidate), start date, end date, bill rate, pay rate, status, and owner. Placement status (active, completed, terminated, extended) maps to Bullhorn Placement status. The Placement-to-JobOrder and Placement-to-Candidate linkage is preserved through Bullhorn's native foreign-key relationships. We use Placement records as the anchor for commission tracking if the customer licenses Bullhorn's commission module.

ClearCompany engagement history on Candidates (phone calls, emails, interview notes, tasks) maps to Bullhorn Activity records attached to the Candidate. Calls become Task records with TaskSubtype=Call and call duration preserved. Emails become Activity records with email content. Meetings become Event records with date, duration, and attendees. Notes migrate as Bullhorn Note records linked to the Candidate via the Note's targetID and targetType. Bullhorn does not support bulk Activity import through CSV; we use Bullhorn's REST API with batch chunking and parent-record resolution to maintain engagement timelines without silent drops.

ClearCompany custom fields vary by module and tenant configuration. We discover all custom field definitions during scoping, including field type, picklist values, required/optional status, and entity attachment. Bullhorn custom fields use the API name convention customFieldX or a custom field name prefixed with the entity (e.g., candidateCustom01). We pre-create Bullhorn custom fields before data import, convert data types (e.g., ClearCompany text picklist to Bullhorn picklist or multi-select), and flag any picklist constraint violations before the production load.

Documents attached to ClearCompany Candidates, Employees, and Jobs migrate as Bullhorn Document Upload records linked to the target entity. We export file content by reference and upload to Bullhorn's document storage. Files exceeding Bullhorn's size thresholds are flagged during scoping for alternative handling (external document link or separate file storage with URL reference in Bullhorn). The original file name, upload date, and attached-by user migrate where available.

ClearCompany integration configurations (ADP, LinkedIn, Indeed, assessment vendors) contain credentials that cannot be exported. We extract integration reference data (connected vendor names, sync frequency settings, mapped field pairs) and document them in a configuration handoff file. All integrations must be re-established manually in Bullhorn with fresh OAuth flows and re-mapped sync rules. Bullhorn's Exchange marketplace is the destination for re-connecting recruitment-specific integrations.

Bullhorn Automation (formerly Herefish) handles recurring outreach, candidate engagement cadences, and task automation within Bullhorn. ClearCompany does not have a comparable automation layer within its ATS module. We do not migrate Bullhorn Automation from any prior Bullhorn instance; we deliver a written inventory documenting any existing automations (trigger, conditions, actions, cadence) and recommend the rebuild approach using Bullhorn Automation's trigger-based builder. This is a separate rebuild scope for the customer's Bullhorn admin or a Bullhorn partner.