Migrate from Recooty to Bullhorn ATS & CRM

Recooty Jobs migrate to Bullhorn Job records as the primary job container. Each Recooty job title, description, location, department, employment type, and publishing status maps directly to the equivalent Bullhorn Job fields (title, description, address, employmentType). Bullhorn Job records are created first because Candidate applications reference the Job ID as a required foreign key. We preserve the Recooty job status (Draft, Published, Closed) as a Bullhorn custom field if the destination edition requires it, since Bullhorn handles status via the isDeleted flag and separate JobOrder status states.

Recooty Candidate records map to Bullhorn Candidate as the primary applicant record. The mapping includes full name fields, email, phone, resume file (PDF, DOC, TXT), application date, and any pipeline stage assignments. Recooty candidates tied to multiple job applications (one candidate, multiple applications) map to separate Bullhorn JobSubmission records, each linked to the same Candidate ID. This preserves the multi-application history that Recooty tracks natively.

Recooty's per-job visual pipeline stages (Applied, Screening, Interview, Offer, Hired) map to Bullhorn Opportunity record types with a corresponding Bullhorn Sales Process defining the stage whitelist. Each Recooty pipeline becomes a Bullhorn Record Type on the Opportunity object. If Recooty has custom pipeline stages per job, we create multiple Bullhorn Record Types and Sales Processes during schema setup, mapping the original Recooty stage names to Bullhorn OpportunityStatus values. Stage transition dates from Recooty are preserved in Bullhorn custom date fields.

Recooty Interview records (date, time, type, interviewer, candidate ID) map to Bullhorn Task records with TaskSubtype set to Interview or Bullhorn Event records depending on whether the interview is a scheduled meeting or a task-based to-do. Recooty Business and Enterprise calendar sync integrations do not transfer; we migrate the interview metadata as structured data and the customer's admin re-establishes calendar integrations in Bullhorn. Self-scheduling links are documented separately as a rebuild item.

Recooty custom fields (Business and Enterprise only) map to Bullhorn custom fields on the Candidate and Job entities. Bullhorn supports text, number, date, dropdown, multi-select, checkbox, and currency field types which cover the Recooty custom field set. We pre-create Bullhorn custom fields via the Bullhorn Field Mappings interface (Admin > Field Mappings) during schema setup, using the Recooty field labels as display names and preserving the original Recooty API field names in the Bullhorn field description for admin reference. Custom field limits per Bullhorn entity are checked before migration to avoid over-provisioning.

Recooty branded career pages generated on Growth and above do not migrate as builder state. Bullhorn Career Portal serves as the replacement. We extract the job content from Recooty Job records (which includes the formatted job description and application questions) and provide a migration worksheet listing every active job posting with its content, application questions, and any custom branding notes. The customer's Bullhorn admin uses the Bullhorn Career Portal builder to re-publish. Job posting history on Recooty's connected job boards is documented as a separate board-level re-publishing checklist.

Recooty stores candidate consent records, data retention policy IDs, and audit trail entries as structured account data. Bullhorn does not have a dedicated GDPR consent object; consent status is tracked via field-level flags (hasOptedOutOfEmail, dateAdded) and custom fields. We extract GDPR metadata from Recooty, map candidate IDs to Bullhorn Candidate records, and set Bullhorn email opt-out flags and a custom consent_date__c field carrying the original Recooty consent timestamp. Any candidates whose consent status may have lapsed during the migration window are flagged in a separate report for admin review.

Recooty does not have a dedicated client management module, but teams sometimes store client company names in custom fields or in candidate notes. Bullhorn's ClientCorporation (Company) and Contact objects allow structured client relationship tracking separate from candidate records. If Recooty contains company or client data in structured form, we map it to Bullhorn ClientCorporation and Contact records during migration. If the data exists only in unstructured notes, we flag it for manual entry or a separate data enrichment step.

Recooty Owner records map to Bullhorn User records by email match. Bullhorn User provisioning is a prerequisite for any migration because Opportunity records and Candidate assignments require OwnerId. We reconcile all distinct Recooty Owner emails against Bullhorn User records and flag any missing Users for the customer's Bullhorn admin to provision before record import proceeds.

Recooty's job board publishing connections (LinkedIn, Glassdoor, Indeed, and 100+ boards) are OAuth or API tokens scoped to the Recooty platform and are not portable. We preserve the job content (title, description, requirements) and application questions in the Bullhorn Job records. Board-level publishing history is documented in a separate post-migration checklist, and the customer's admin re-establishes publishing connections through Bullhorn's job board integrations or by publishing directly through each board's native interface.

Recooty workflow automations (stage-change triggers, email notifications, assignment rules) do not migrate to Bullhorn Automation (formerly Herefish) because they are different automation engines with different trigger models, action types, and configuration schemas. We deliver a written inventory of every active Recooty automation with its trigger conditions, actions, and a recommended Bullhorn Automation equivalent. The customer's Bullhorn admin or a Bullhorn partner rebuilds them post-migration.

Recooty pipeline metrics, hire velocity, and candidate ratings do not transfer as Bullhorn reports. Bullhorn Starter includes standard reporting; Bullhorn Core and Pro add advanced analytics dashboards. We extract key Recooty metrics (pipeline stage counts, time-in-stage averages, application volumes by job) as a CSV reference sheet and provide a mapping table showing which Bullhorn standard reports replace each Recooty analytics view. Custom Recooty reports are documented as a rebuild scope for the customer's reporting team.