Migrate from Savvy HRMS to Bullhorn ATS & CRM

Savvy HRMS candidate profiles, application stages, interview scores, and offer details map to Bullhorn Candidate. Stage history from the Savvy HRMS Recruitment module converts to Bullhorn Candidate status and to the corresponding JobOrder submission pipeline. We preserve the original application date, source channel, and any scoring values in Bullhorn custom fields. If the candidate has been placed through Savvy HRMS as a contract worker, the placement record maps to Bullhorn Placement with start date, end date, and pay rate preserved.

Savvy HRMS employee records represent either current employees or contract workers. Employees with recruitment history in the Savvy HRMS Recruitment module map to Bullhorn Candidate. Pure administrative employees without recruitment context map to Bullhorn ClientContact if they represent an organization contact, or are flagged as out-of-scope if they represent an internal HR record with no Bullhorn equivalent. We confirm this boundary during scoping based on the customer's Bullhorn usage model.

Savvy HRMS job history records attached to an employee or candidate split into multiple Bullhorn Candidate Employment records. Each history row maps to company name, job title, start date, end date, and description. We concatenate employment periods and map the most recent employer to the Candidate's primary employment record.

Core employee fields (name, email, phone, date of birth, address, emergency contact) map to Bullhorn Candidate standard fields. Employee ID from Savvy HRMS becomes a custom field on Candidate. Date of hire from Savvy HRMS maps to the Candidate's dateAdded or a custom hire_date__c field depending on Bullhorn edition configuration.

Savvy HRMS contract worker records (contract dates, billing rates, assignment details) map to Bullhorn Candidate with a contract type designation, and to a Bullhorn Custom Object if the customer requires detailed contract terms tracking (start date, end date, hourly/daily rate, vendor name, assignment status). Bullhorn Support provisions the Custom Object before migration using the Custom Object Setup Spreadsheet.

Savvy HRMS employee documents including resumes, ID copies, offer letters, and contracts export as binary files and attach to the corresponding Bullhorn Candidate record. Resume content also feeds Bullhorn's resume parsing on insert so that candidate fields (skills, education, work history) are auto-populated from the parsed content. We preserve the original file name and mime type as ContentDocument metadata.

Savvy HRMS leave types, accrual rules, and employee balance amounts at the migration cut-off date do not have a native Bullhorn equivalent because Bullhorn is a recruiting ATS, not a leave management system. We map leave balances to a Bullhorn Custom Object provisioned per the customer's Bullhorn edition if the customer wants to maintain leave history in Bullhorn for compliance or auditing. Otherwise, we export leave data as a CSV handoff document with employee ID, leave type, balance, and accrual date.

Savvy HRMS payroll records (earnings, deductions, net pay per pay period) have no direct Bullhorn equivalent. Bullhorn is not a payroll system. We export payslip summary data as a structured CSV with employee ID, pay period, earnings, deductions, and net pay, and attach it as a Note on the Candidate or store it as an external reference. Full payroll rebuild requires a separate payroll system implementation outside the Bullhorn migration scope.

Savvy HRMS review cycles, ratings, and competency scores map to a Bullhorn Custom Object (appraisal_history__c) with fields for review date, rating, reviewer, and competency scores. Bullhorn Support provisions this custom object before migration. We preserve the review period and score values at the cut-off date; active review cycles in progress are documented separately for the customer's Bullhorn admin to recreate.

Savvy HRMS course enrollments, completion statuses, and quiz scores map to a Bullhorn Custom Object (training_history__c) with fields for course name, enrollment date, completion date, status, and score. Certification expiry dates are flagged as requiring re-triggering in Bullhorn or a learning management system. Bullhorn Support provisions this custom object before migration.

Savvy HRMS attendance data (clock-in/clock-out timestamps, overtime, grace period adjustments) does not have a Bullhorn equivalent because Bullhorn is a recruiting and placement platform. We export attendance records as a CSV handoff grouped by employee ID and pay period. Customers needing attendance tracking in Bullhorn should consider Bullhorn Time & Expense or a third-party time-tracking integration.

Savvy HRMS organizations frequently add custom properties to standard objects. We enumerate all active custom fields during scoping, map each to a Bullhorn custom field on the Candidate entity, and confirm field types (text, drop-down, date, number) match Bullhorn's supported custom field types. Bullhorn custom fields use the field label as the display name and an auto-generated API name with __c suffix.