Migrate from HR Manager Pro to Bullhorn ATS & CRM

HR Manager Pro candidate records (name, email, phone, resume, status, source, notes) map directly to Bullhorn Candidate. The HR Manager Pro status field (applied, interview, offer, hired, rejected) maps to Bullhorn Candidate.status with a custom status value set we configure before migration. Resume files are downloaded from the WordPress media library and uploaded to Bullhorn via the Candidate Document API endpoint, linked as ContentDocument with a DocumentType of Resume. Candidate source attribution migrates to a custom Candidate field candidateSource__c if the customer's Bullhorn edition limits the standard source picklist.

HR Manager Pro Company records (company name, address, industry, website, primary contact) map to Bullhorn ClientCorporation. The primary contact person from HR Manager Pro maps to a Bullhorn Contact record linked to the ClientCorporation via the clientCorporationId lookup. If HR Manager Pro stores multiple contacts per company, each becomes a separate Bullhorn Contact under the same ClientCorporation. Company deduplication uses name and website as the key.

HR Manager Pro job postings map to Bullhorn Job records. The HR Manager Pro job title maps to Job.title, description maps to Job.description (with HTML formatting preserved where present in the source). Employment type, location, and salary range from HR Manager Pro map to Bullhorn custom fields (jobType__c, address__c, salaryMin__c, salaryMax__c) because Bullhorn's standard Job object uses JobAddress for location and does not include a native salary range field.

HR Manager Pro applications (candidate applied to a specific job) map to Bullhorn JobSubmission. We resolve the CandidateId and JobId references at migration time using the email match on Candidate and the job title match on Job. Application status (pending, reviewed, shortlisted, interview_scheduled, offer_extended, placed, rejected) maps to a custom JobSubmission status field or the standard submissionStatus__c if the Bullhorn edition exposes it. A submitted candidate without a matching Job record is held in a pending queue for manual Job creation before the submission inserts.

HR Manager Pro Employee records split into two Bullhorn targets. Internal staff who will use Bullhorn as system users (recruiters, sales staff, administrators) map to Bullhorn User records with email as the match key and a custom field originalEmployeeId__c for audit. Employee records representing the customer's own workforce (not candidates or client contacts) map to Bullhorn Contact records in a separate contact segment. Bullhorn Users require active Bullhorn seat licensing; we flag this during scoping and the customer provisions the required seats before User migration proceeds.

HR Manager Pro department taxonomy has no native Bullhorn equivalent. Bullhorn does not include a Company Department concept in standard objects. We offer two migration paths during scoping: (1) map departments to a Bullhorn custom object CorporateDepartment__c with a lookup from Contact or User, limited by the customer's custom object quota (2 on Bullhorn ATS, 10 on Enterprise); or (2) map departments as tags on Contact/User records using the Tag entity. The customer selects the approach before field map finalization.

HR Manager Pro leave entitlement and accrual balances migrate as static values only. Bullhorn has no absence management module, so there is no destination object to carry accrual rules, carryover limits, or vesting schedules. We write current leave balances as custom fields on the Contact or User record (e.g., annualLeaveRemaining__c, sickLeaveBalance__c) and advise the customer's admin to configure leave entitlements in a dedicated absence management system post-migration.

Employee documents (contracts, certifications, government IDs) stored in the WordPress media library require a parallel download step. The HR Manager Pro CSV contains the file path or WordPress attachment ID; we download each file, map it to the target Bullhorn record (Candidate or Contact) by matching on the parent employee/candidate name, and upload via Bullhorn's ContentDocument REST API with a custom DocumentType classification. This step adds 15-30 minutes per 100 documents depending on file size and WordPress server response time.

HR Manager Pro allows admin-defined custom fields on employee profiles that are discovered only during pre-migration scan. We map each discovered custom field to a Bullhorn custom field on the relevant entity (Candidate for applicant-facing fields, Contact for workforce fields). Bullhorn's custom field limits apply: Bullhorn ATS is capped at 2 custom objects with 55 fields each; Front Office Growth/Enterprise allows 10 custom objects with 55 fields each. If the customer's HR Manager Pro schema exceeds the Bullhorn edition's quota, we route overflow fields to a supplemental CSV for manual admin entry and flag the constraint during scoping.

If HR Manager Pro tracks placements (hired candidates tied to a job), these map to Bullhorn Placement records. The Placement object links CandidateId, JobOrderId (derived from the mapped Job), ClientCorporationId, and custom billing fields (payRate__c, billRate__c, overtimeRate__c). Placement date, termination date, and status migrate as Placement.dateBegin, dateEnd, and a status picklist configured during schema setup.

HR Manager Pro notes attached to candidate or employee records map to Bullhorn Note records linked via ContentDocumentLink to the parent Candidate, Contact, or ClientCorporation. Note body migrates as plain text. The original note author and timestamp migrate to Note.createdById and Note.createdDate for audit trail integrity.

HR Manager Pro call and meeting logs attached to candidate records map to Bullhorn Task with TaskSubtype = Call (for calls) or Event (for meetings). Call duration, disposition, and outcome migrate to custom Task fields (callDuration__c, callDisposition__c). Meeting location, start time, and end time migrate to Bullhorn Event fields. Attendee associations in HR Manager Pro map to EventRelation records pointing to the relevant Candidate or Contact.