Migrate from HR Director to Bullhorn ATS & CRM

HR Director Employee records map to Bullhorn Candidate records. The employee's personal name fields map to Candidate firstName and lastName; email maps to Candidate email; phone maps to Candidate phone; address maps to Candidate address. The employee's employment status (active, leaver) maps to Bullhorn Candidate status with a custom field original_employment_status__c preserving the original HR Director value. Employee records that represent internal staff (not external candidates) are flagged with a custom field candidate_type__c set to 'internal_transfer' so the Bullhorn admin can filter them separately from external candidates placed with clients.

The HR Director employer entity (the company itself as the internal employer) maps to a Bullhorn Client Corporation record representing the staffing agency's own corporate entity. This is necessary if the agency places its own employees as contractors or if Bullhorn is used to track internal headcount alongside external candidate placements. The employer's registered address and company name populate the Client Corporation name and billing address fields.

HR Director's internal departments and organisational hierarchy do not have a direct Bullhorn equivalent. Bullhorn uses Client Corporations for external client companies and does not model internal org structure. We map the HR Director employer to a single Client Corporation (the staffing agency's own firm) and map internal departments to a custom Bullhorn custom object InternalDepartment__c with a lookup to the Client Corporation. If the customer uses Bullhorn Connexys or Bullhorn One, department structure may map to Business Sector or Division fields on Client Corporation.

HR Director absence records (type, start date, end date, status) cannot map to native Bullhorn objects because Bullhorn has no standard absence management feature. We store absence history as a long-text custom field absence_history__c on the Candidate record in JSON-structured format: {'type': 'Sick', 'start': '2024-03-01', 'end': '2024-03-03', 'status': 'Approved'}. The customer decides during scoping whether to store this on every migrated Candidate or only on Candidates with significant absence history. Bullhorn Automation can be configured to surface this field in a Candidate's record layout.

HR Director compensation-effective-date records (salary, bonus, pay frequency, effective date) cannot map to Bullhorn standard fields because Bullhorn does not have an employee payroll engine. We store compensation history as a structured custom field compensation_history__c on the Candidate record in JSON format: {'salary': 45000, 'currency': 'GBP', 'effective_date': '2023-04-01', 'pay_frequency': 'Annual'}. If the agency uses Bullhorn Time & Expense for contractor timesheets, the placement's bill rate and pay rate are configured on the Placement record post-migration, not migrated from HR Director compensation records.

HR Director documents (employment contracts, ID copies, right-to-work checks) migrate as Bullhorn ContentDocument records attached via ContentDocumentLink to the Candidate. The document type (contract, ID, DBS check) is stored in a custom picklist field document_type__c on the ContentDocument. The original filename is preserved. If HR Director stores documents in a proprietary or encrypted format, we extract text content where possible and store it as a Note attachment on the Candidate as a fallback.

HR Director emergency contacts (name, relationship, phone) store as a structured custom field emergency_contact__c on the Candidate record in JSON: {'name': 'Jane Smith', 'relationship': 'Spouse', 'phone': '+44-7700-900123'}. Bullhorn does not have a native emergency contact object. The customer may alternatively choose to store emergency contacts in the Candidate's primary address or notes field if GDPR considerations require them to be accessible to Bullhorn users.

HR Director employment status values (active, suspended, on leave, leaver, retired) map to Bullhorn Candidate status values (Active, Inactive, Placed) with a custom field original_status__c preserving the source HR Director status for audit. Placements in Bullhorn represent the active employment or assignment of a Candidate with a Client; internal staff who remain on the agency's payroll are entered as Candidate records with a placement record reflecting their internal assignment.

HR Director leave entitlement balances (annual leave remaining, sick leave entitlement) cannot map to Bullhorn standard fields. We store current-year entitlement as a custom field leave_entitlement__c on the Candidate record. If the agency requires leave tracking for placed contractors (for example, umbrella company contractors entitled to statutory leave), this is reconfigured in Bullhorn Time & Expense or in a post-migration leave management integration rather than stored as migrated data.

HR Director job roles and positions (title, job family, grade) map to Bullhorn Job Order records if the migration includes a client-specific job structure, or to custom fields on the Candidate record (candidate_title__c, candidate_job_family__c) if the agency is migrating internal headcount without client job orders. Bullhorn Job Orders are the staffing-specific equivalent of job requisitions and carry client, location, requirements, and bill-rate information.

HR Director reporting-line data (manager-employee relationships) stores as custom fields manager_name__c and manager_email__c on the Candidate record. If the manager is also a migrated Candidate or an active Bullhorn User, we resolve the lookup at migration time and store the manager's Candidate ID or User ID. Bullhorn's User object is not directly equivalent to HR Director's manager hierarchy; Bullhorn Users represent recruiters, not line managers.

HR Director employee start date migrates to Bullhorn Candidate dateCreated as the employment start date, and to a custom field original_start_date__c preserving the exact source value. Bullhorn's native dateCreated represents the record creation timestamp in Bullhorn, not the employment commencement date; we use the custom field to preserve the HR Director start date for compliance records and tenure calculations.