Migrate from Worknice to Bullhorn ATS & CRM

Worknice People records (employees, contractors, managers, account owners) map to Bullhorn Candidate records. We extract the person's name, email, phone, role, position, start date, and pay details from the CSV export and map them to Bullhorn Candidate standard fields. The Worknice role (Employee, Contractor, Manager) becomes a custom Candidate field or Custom Object entry since Bullhorn separates Candidate type from the placement relationship.

Worknice Position records define job titles and hierarchies and serve as the structural backbone of the org chart. Bullhorn's JobOrder is a recruiting requisition rather than an employment position, so we map Worknice Position names and reporting relationships to Bullhorn JobOrder titles and a Custom Object capturing the org hierarchy. If the customer needs to preserve the internal position structure in Bullhorn, we use a Custom Object (Position__c) with a self-referencing Manager lookup.

Worknice leave entitlements and accrual balances are tied to People and position start dates with accrual rules stored per leave type. Bullhorn has no native leave management object. We create a LeaveBalance__c Custom Object (up to 10 allowed on Bullhorn Enterprise) with fields for LeaveType, Balance, AccrualMethod, and LastAccrualDate. We export the current balance as a static starting balance rather than the accrual rule itself, and document the accrual method in the migration notes so the customer's Bullhorn admin can configure equivalent rules if Bullhorn's absence management module is enabled.

Worknice supports 360 reviews, customizable review forms, and review status tracking. Bullhorn has no native review form builder. We map reviewer relationships, form question responses, and completion status to a Custom Object (PerformanceReview__c) linked to the Candidate. Custom form fields require field-by-field mapping during scoping because Worknice custom forms and Bullhorn Custom Object field names diverge. Review documents and completed forms migrate as Bullhorn Document records attached to the Candidate.

Worknice company-level OKRs and employee goals with alignment hierarchies export as goal titles, descriptions, progress percentages, and parent-child relationships. Bullhorn has no native goal or OKR object. We map goals to a Custom Object (Goal__c) with fields for Title, Description, Progress, ParentGoalId (self-lookup), and OwnerId pointing to the Bullhorn User. If the customer has fewer than 10 active Custom Objects and prefers a lighter approach, goals migrate as Note records attached to the Candidate with a 'OKR' type prefix in the title.

Worknice Bundles group templates (documents, onboarding tasks, review forms) assigned to positions or people during onboarding. Bullhorn has no Bundle equivalent. We export bundle names and template associations as structured metadata and attach them to the relevant Worknice Position record. In Bullhorn, we store bundle names as a multi-line text field on the Position__c Custom Object and flag during the design call that bundle automation must be rebuilt as Bullhorn workflows by the customer's admin post-migration.

Worknice stores compliance documents, contracts, and onboarding paperwork per person. We export documents as binary blobs from Worknice's file export and recreate the attachment relationship in Bullhorn as Document records linked to the Candidate via ContentDocumentLink. File naming conventions may differ; we preserve the original Worknice filename in a custom field (OriginalFileName__c) for audit traceability.

Time tracking is available on Worknice Essential plan. We export time entry records per person including hours, dates, and time category where this data exists. Bullhorn does not have a native time tracking object. If the customer needs to preserve historical time data, we create a TimeEntry__c Custom Object. If time tracking will be handled by a separate tool post-migration, we export the data as a CSV reference file rather than migrating into Bullhorn's schema.

Worknice assigns roles at the person level (Employee, Manager, Account owner, Contractor). Bullhorn separates Candidate type from user roles. We preserve role assignments as a custom text or picklist field on the Bullhorn Candidate record (WorkniceRole__c). The customer's Bullhorn admin determines how these roles map to Bullhorn's internal team structure.

Worknice Connections maps individual People records to external systems (ATS, payroll, timesheet integrations) via its integration broker. These person-level integration IDs are specific to Worknice and have no counterpart in Bullhorn. We exclude these records from the migration set and flag that the customer must re-establish integration connections in Bullhorn through Bullhorn Marketplace or Bullhorn's REST API after go-live.

Worknice supports continuous feedback collection and engagement surveys. We export survey responses and feedback records per person where they exist. Bullhorn has no native survey or feedback object. Survey responses migrate to a Custom Object (SurveyResponse__c) linked to the Candidate. Survey design and question structures require reconstruction in Bullhorn's form builder or a third-party survey integration; we document the original Worknice survey schema as part of the migration notes.

Worknice Owner and Manager references on People records map to Bullhorn User records. We resolve by email match against Bullhorn's User table. Any Worknice Owner without a matching Bullhorn User goes to a reconciliation queue for the customer's Bullhorn admin to provision before record import resumes.