Migrate from Mercu to Bullhorn ATS & CRM

Mercu staff member records map to Bullhorn Candidate records. The staff member's full name maps to Candidate firstName and lastName. Employment status (active, terminated, on leave) maps to Candidate status with custom fields for employment category. We resolve the mapping at the field level during discovery and flag any staff records with missing names or duplicate national ID numbers for manual review before bulk import.

Mercu departments (faculties, schools, administrative units) map to Bullhorn ClientCorporation records if the university models itself as a client employer, or to a Candidate custom field if departments represent internal cost centers. The choice is made during scoping based on whether the migration will also include job orders tied to departments. We create Bullhorn field mappings in Admin > Field Mappings to route the department name into the correct destination.

Employment contract data (contract type, start date, end date, salary band, role title) maps to a Bullhorn Custom Object attached to the Candidate entity. Bullhorn ATS edition allows 2 custom objects per entity with 55 fields each; Front Office Growth and Enterprise allow 10. We request the custom object through Bullhorn Support using the Custom Object Setup Spreadsheet and map contract fields to the custom object schema before import begins.

Annual leave, sick leave, and study leave balances map to a second Bullhorn Custom Object attached to the Candidate. Leave type, accrued amount, used amount, and remaining balance are stored as custom fields on the custom object. Bullhorn ATS edition users who need both contract and leave data must decide which is higher priority for migration or upgrade to a higher Bullhorn tier that allows more custom objects.

Mercu's organizational hierarchy (reporting managers, faculty chairs, department heads) maps to Bullhorn User reporting relationships. Each Mercu staff member with direct reports maps to a Bullhorn User with subordinates assigned. We resolve the User mapping by matching Mercu employee ID or email against Bullhorn User records provisioned before migration.

Payroll data in Mercu (salary components, bank details, tax identifiers) splits across Bullhorn Placement records and a third Custom Object if the Bullhorn edition allows. Placement fields capture pay rate, bill rate, and placement status. Detailed payroll components (deductions, allowances, tax codes) require a custom object if the destination tier supports it.

Mercu internal job postings for faculty and staff roles map to Bullhorn JobOrder records. JobOrder title, description, department, employment type, and salary range migrate. Bullhorn JobOrder requires at minimum a title, client corporation reference, and job status. We configure the JobOrder Record Type to reflect internal university posting versus external recruitment.

Mercu job applications for internal postings map to Bullhorn Candidate records linked to JobOrder via a JobSubmission. The applicant's Mercu staff member profile (if internal) or external candidate profile (if external) becomes a Candidate record. Application status maps to JobSubmission status.

Academic qualifications (degree, institution, year, field of study) from Mercu map to Bullhorn Candidate custom fields. Bullhorn's Candidate entity supports custom fields for education history. We extend the Candidate schema with a customObject if the standard 20 custom fields per entity are insufficient for multi-degree academic staff.

Performance review records map to a Bullhorn Custom Object attached to Candidate. Review period, rating, reviewer, and comments migrate as custom fields. This object is only available on Bullhorn editions that support more than 2 custom objects per entity.

Training attendance and completion records map to a Bullhorn Custom Object on Candidate. Training course name, completion date, provider, and certification expiry migrate. Bullhorn editions supporting multiple custom objects can accommodate this in a separate custom object or consolidated into an HR profile custom object depending on field count.

Mercu staff portal user accounts map to Bullhorn User records. We match by email address. Active Mercu users become active Bullhorn Users; inactive Mercu users become inactive Bullhorn Users. Bullhorn User provisioning (role, department assignment, Bullhorn seat type) is the customer's admin responsibility; we validate the mapping and flag any Mercu users without a matching email for reconciliation.