Migrate from Bullhorn ATS & CRM to Crelate

Bullhorn Candidates map to Crelate Contacts. The Bullhorn Candidate is the primary ATS record storing parsed resume data, work history, skills, certifications, and status. We map standard fields (name, email, phone, address, skills) directly. Bullhorn's Candidate custom fields and CandidateList associations (submissions to jobs) migrate as Crelate custom fields and activity tags respectively. Resume file attachments require separate retrieval via Bullhorn's file reference API because CSV exports do not include attachments.

Bullhorn JobOrders map to Crelate Jobs. JobOrder contains requirements, status, location, salary information, and links to Clients. We map standard job fields directly. Bullhorn's job pipeline stages (e.g., New, Interview, Offer, Extended) require a stage mapping table because Bullhorn's recruiting-specific stage names differ from Crelate's standard ATS pipeline terminology. We document the customer's stage names and build a custom mapping before import, preserving stage history as a Crelate activity tag if exact labels cannot be matched.

Bullhorn Clients (ClientCorporation) map to Crelate Client Organizations. This is Bullhorn's CRM company record representing the staffing agency's customer. Standard fields—company name, industry, address, website—map directly. The primary contact within each Client record migrates separately as a Crelate Contact linked to the Client Organization.

Bullhorn Contacts represent both client-side business contacts and candidate references. They share a schema but serve different roles. We separate Bullhorn Contacts by their entity type during migration to avoid confusion with Candidate records. Client-side contacts link to the Client Organization; candidate references link to the Candidate record. Email, phone, title, and company association migrate as standard fields.

Bullhorn Opportunities are CRM-level pipeline deals tied to Clients, representing sales pipeline stages distinct from the ATS submission flow. They map to Crelate Opportunities or pipeline deals. Bullhorn's recruiting-specific pipeline stages (Interview, Offer, Extended) differ from standard CRM terminology. We build a custom stage mapping table during scoping, documenting the customer's exact stage names and probability percentages. Stage history is preserved as a custom field at Crelate if exact labels cannot be matched.

Bullhorn Placements map to Crelate Placements. The Placement record links Candidate, JobOrder, and Client, with billing information including pay and charge rates. Contract placements carry overtime rules, start/end dates, and split-billing details. We preserve all placement billing fields including pay rate, charge rate, overtime multiplier, and billing frequency. Historical placements carry placement commission data that migrates as Crelate custom fields.

CandidateList represents a candidate's submission to a specific job, storing status within the recruitment pipeline (e.g., Submitted, Phone Screen, Interview, Offer, Placed). Bullhorn assigns each CandidateList a status within the Bullhorn job pipeline. We migrate submission status as Crelate activity tags on the candidate Contact record, linked to the destination Job. This preserves the candidate's journey through each job submission without requiring a dedicated submissions object.

Bullhorn custom objects (up to 10 per entity on Front Office editions, each with 55 fields) have no direct Crelate equivalent. Crelate supports a hard cap of 20 custom fields per entity with no child-table or custom object support. We audit every Bullhorn custom object during scoping. Single-instance custom object data (one record per candidate or job) flattens into Crelate custom fields. Multi-instance custom objects (e.g., multiple certifications per candidate, multiple interview rounds per job) are transformed into Crelate tags, notes (with structured text), or activity records depending on the customer's prioritization during scoping.

Bullhorn Tasks store to-dos with type, due date, status, and owner assignment across entities. They map cleanly to Crelate Task records. Bullhorn's ATS Growth edition caps API subscriptions at 50, which may limit bulk task retrieval; we handle this with pagination and batched retrieval. Standard task fields (subject, due date, status, priority, owner) migrate directly.

Bullhorn Users are system accounts representing recruiters, sales staff, and administrators with assigned roles and permissions. User records include name, email, role, and department. We extract all Users and map them to Crelate Users by email. Recruiters without a matching Crelate User go to a reconciliation queue for the customer's admin to provision before record import resumes.

Bullhorn stores resume files, parsed documents, and communications as separate attachment entities accessible via the file reference API endpoints (/entityFiles/{entityType}/{entityId} and /file/{entityType}/{entityId}/{fileId}). Bullhorn's standard CSV export does not include attachments. We retrieve every attachment via Bullhorn's file reference API, map the file to the corresponding migrated Candidate or Contact record, and upload to Crelate. This step is explicitly planned because it requires API calls beyond the standard export and cannot be completed via CSV alone.

Bullhorn Lead records (distinct from Candidate) represent unqualified prospects in the CRM pipeline. They map to Crelate Leads if the customer maintains a separate lead queue. If the customer's Bullhorn workflow routes all prospects through the Candidate object, Leads may be empty and can be skipped. We confirm the customer's lead workflow during scoping.