Migrate from Workstream to Bullhorn ATS & CRM

Workstream Employee records map to Bullhorn Candidate records. The three Workstream lifecycle tabs (Active, Onboarding, Offboarded) each produce Candidate records with their original status preserved in a custom field workstream_lifecycle_status__c. Standard mappings include firstName, lastName, phone, email, address fields, dateOfHire to dateAdded, and job title or position name to primarySkills or a custom field workstream_position__c. We resolve the candidate deduplication key by email address during import.

Workstream Position records map to Bullhorn JobOrder. Each Position's location assignment maps to a Bullhorn JobAddress or to a custom field workstream_location__c on the JobOrder. Position title, pay rate/range, schedule type, and job description map to corresponding JobOrder fields or custom fields (title, salary, hours, description). We preserve the Position's department assignment as a custom field workstream_department__c on the JobOrder.

Workstream Position Templates are reusable job definitions that feed multiple Position instances. We flatten Position Templates into their instantiated Position records during export, tagging each with the template origin as a custom field workstream_template_id__c on the resulting JobOrder in Bullhorn. This preserves the standardization benefit without requiring Bullhorn to replicate the template-parent structure.

Workstream Applications (candidate submissions tied to a specific Position) map to Bullhorn JobSubmission. The mapping includes applicant contact info, answers to screening questions migrated as custom fields on the JobSubmission, communication history migrated as Note or Task records linked to the JobSubmission, and status in the hiring pipeline mapped to Bullhorn's submissionStatus field. The candidate-to-job association is preserved by resolving both the Candidate and JobOrder references at migration time.

Workstream's primary organizational unit is the Location (physical store or office). We preserve Location names and addresses as Bullhorn Branch records if the destination Bullhorn edition includes Branch functionality, or as custom fields workstream_location_name__c and workstream_location_address__c on the Candidate and JobOrder for standard Bullhorn ATS editions. Each Location's assigned manager maps to a Bullhorn User reference.

Workstream custom fields on team members (text, date, number, dropdown) map to Bullhorn custom fields on Candidate. We detect field-level presence during Workstream profiling because Workstream custom fields can be scoped to specific roles, locations, or departments, meaning a field may exist on one employee record but not another. We map only fields that are populated for each individual record, avoiding null-fill issues. Bullhorn ATS edition limits mapping to 2 custom objects with 55 fields each; if custom field count exceeds this, we recommend Front Office Growth or Enterprise edition during scoping.

Workstream custom fields on Positions map to Bullhorn custom fields on JobOrder. These commonly include internal job codes, franchise-specific requirements, or uniform allowances. We extract all active Position-level custom fields and map them to Bullhorn JobOrder custom fields of equivalent type (text, date, number, picklist). The workstream_position_custom__c prefix distinguishes them from employee-level custom fields in the destination.

Workstream custom fields scoped to Locations (e.g., regional manager, district code, store format) map to Bullhorn custom fields on the Branch or on a ClientCorporation record representing the franchise or corporate entity. We resolve the parent Location for each Workstream employee and Position during scoping and attach the Location-level custom field values to the corresponding Bullhorn records.

Workstream uses configurable pipeline stages for the hiring process (Applied, Screening, Interview, Offer, Hired). We extract the full pipeline definition and map stage names and order to Bullhorn JobOrder status values or to a custom field workstream_pipeline_stage__c. If Workstream uses custom pipeline configurations per location or role, we document each pipeline variant during scoping and apply the correct stage mapping per JobOrder at migration time.

Workstream stores pay rates, pay schedules, and payroll sync status as employee properties rather than running payroll itself. These migrate as Bullhorn custom fields on the Candidate (payRate, payRateType, payrollSyncStatus) or on the Placement record if the customer licenses Bullhorn Time & Expense. We flag any Workstream-integrated payroll provider (ADP, Paychex, Paylocity) during scoping and document the integration for reconfiguration against Bullhorn's supported payroll integrations post-migration.

Workstream's offboarded employee records require explicit scoping because the standard export may omit the Offboarded tab. We query all three tabs (Active, Onboarding, Offboarded) explicitly during discovery, include offboarded history in the migration package unless the customer opts out, and preserve terminationDate and terminationReason fields as custom fields on the Bullhorn Candidate record. This preserves compliance records that may be required for rehire eligibility checks or audit purposes.

Workstream role definitions scoped to locations determine pay and schedule authority. We map which roles exist and how employees are assigned to them, preserving the location-role combination as a custom field workstream_role_assignment__c on the Bullhorn Candidate. Role definitions themselves (the list of available roles) migrate as a custom picklist or as records in a custom object depending on Bullhorn edition.