Migrate from Workable to Bullhorn ATS & CRM

Workable Candidates map directly to Bullhorn Candidate records. We extract the full profile including name, email, phone, address, social URLs, communication history, and evaluation comments. Workable's tags and talent pool memberships map to Bullhorn Candidate tags. The Candidate record in Bullhorn is the parent for all submissions, so candidate migration must complete before JobSubmission records are loaded.

Workable Jobs map to Bullhorn JobOrder. Job title, description, department, employment type, and status migrate directly. Workable's job status (active, paused, closed) maps to Bullhorn's JobOrder status field. We flag whether the destination Bullhorn instance requires job reopen or job type reconfiguration per the customer's licensing tier.

Workable pipeline stages are per-job and carry candidate counts and movement history. We map stage names and sequences to Bullhorn JobSubmission status values. ClonePartner's ATS migration checklist advises building a static mapping table (not dynamic) that the ETL pipeline references, forcing a sign-off on exact stage translations before any data moves. Stage probabilities from Workable migrate to JobSubmission custom fields if the Bullhorn instance has them enabled.

Workable interviews (scheduling data, interviewer assignments, meeting type, date/time) map to Bullhorn Event records linked to the JobSubmission. Interviewer assignments become EventRelation records pointing to Bullhorn User records resolved by email match. Meeting type and location migrate to Bullhorn Event description and custom fields.

Workable structured scorecards (rating templates, individual scores, written feedback) migrate to Bullhorn Candidate Note records with a standardized format using a scorecard__c prefix in the note title for identification. Rating scales differ between platforms; we normalize numeric ratings to the destination scale and preserve the original Workable score as a text field for audit. Scorecard templates are not a portable format in Bullhorn and are documented separately for rebuild.

This is the highest-risk mapping in the pair. Workable Offer records (compensation, start date, status: sent, accepted, declined, retracted) map to Bullhorn Placement records only if the candidate has a confirmed hire. Workable Offer status is preserved as a custom Placement field; candidates with non-confirmed offer status become Bullhorn JobSubmissions without a Placement. Bullhorn Placement also carries pay/billing structure (bill rate, pay rate, overtime rate) that has no direct Workable equivalent; we leave these fields for the customer admin to populate post-migration or configure in Bullhorn Time & Expense.

Workable recruiters, hiring managers, and collaborators per job map to Bullhorn User records resolved by email. Role assignments (recruiter, hiring manager, coordinator) map to Bullhorn JobOrder owner, JobSubmission recruiter, or CandidateOwner relationships depending on the relationship type. Any Workable hiring team member without a matching Bullhorn User is flagged in the reconciliation queue for the customer admin to provision before record import.

Workable HRIS employee records (name, department, job title, employment status) map to Bullhorn User records for employees who will also act as recruiters or internal staff. Bullhorn's User table does not have a direct HRIS equivalent; employee-only records that do not need Bullhorn access are documented in a separate employee inventory for the customer admin to manage outside Bullhorn or in Bullhorn Onboarding (formerly Able).

Workable time-off balances and requests (Standard plan and above) are an HRIS feature with no Bullhorn ATS equivalent. Bullhorn Onboarding handles onboarding workflow but not PTO accrual or balance tracking. We export time-off data as a CSV inventory during discovery and recommend the customer configure a separate HR or payroll system for this data post-migration. This is not a Bullhorn-supported object.

Workable Talent Pools (customer-created candidate groupings) map to Bullhorn Candidate tags and, where applicable, Bullhorn Candidate Segments if the Bullhorn instance has the Segments feature enabled. Pool names migrate as tag values. The customer chooses during scoping whether to map pools to tags, segments, or both depending on how Bullhorn's segmentation is used for candidate sourcing.

Workable custom candidate and job fields migrate to Bullhorn custom fields on the equivalent entity. Bullhorn supports custom fields on all entities (Candidate, JobOrder, ClientCorporation, ClientContact, Placement, Lead) with per-entity limits. We audit all Workable custom field names, types, and values during scoping and map them to Bullhorn field types (text, number, date, dropdown, multi-select, checkbox). Bullhorn field mapping settings (required, hidden, sort order) are configured in Admin > Field Mappings before migration.

Resume files must be extracted separately from Workable candidate profile data. The CSV candidate-details export does not include resume files; we script bulk extraction using Workable's /candidates/{id}/resume endpoint. Bullhorn supports file attachments on Candidate records via the REST API or Bullhorn file upload. We re-associate extracted resume files by candidate email match during Bullhorn import. File naming conventions are preserved where Workable provides them.