Migrate from Eddy to Bullhorn ATS & CRM

Eddy Employee records map to Bullhorn Candidate (for active candidates in the recruiting pipeline) or ClientContact (for existing client relationships). The split is determined during scoping: candidates with a Bullhorn JobOrder association go to Candidate; contacts representing hiring managers or client contacts go to ClientContact. Eddy employment status (active, on_leave, terminated) maps to a Bullhorn custom field; termination date maps to a custom date field since Bullhorn Candidate lacks a native termination date field. Job title, department, and location from Eddy map to Bullhorn custom fields on both Candidate and ClientContact.

Eddy department records (names, cost center codes, reporting hierarchy) map to Bullhorn ClientCorporation records with a department custom field, or to a Bullhorn custom object for org-chart reporting. We flag whether the customer needs ClientCorporation as the legal entity or as the business unit and configure the mapping accordingly. Locations and addresses from Eddy map to Bullhorn ClientCorporation Address fields.

Eddy PTO balances (accrued, used, available, carry-forward) do not have a Bullhorn native equivalent. We create a Bullhorn custom object with fields for pto_type, accrued_balance, used_balance, available_balance, and carry_forward_days, linked to the Employee-equivalent Candidate record. We preserve balance snapshots as of the migration date. Bullhorn ATS tier limits custom objects to 2; ATS Growth has 0. We confirm the customer's Bullhorn edition during scoping and recommend Front Office Growth or Enterprise if custom objects are required.

Eddy employee documents (offer letters, contracts, signed agreements) migrate as Bullhorn ContentDocument records. We extract file names, file types, upload dates, and blob references. Bullhorn's document storage attaches files to Candidate or ClientContact via ContentDocumentLink. PDF and standard document formats are fully supported. Rich-text document content is preserved. We flag that Eddy's document export may require CSV-assisted extraction if the API export path is incomplete for certain file types.

Eddy onboarding step checklists and task assignment counts map to Bullhorn custom fields (step_1_status, step_2_status, etc.) or a Bullhorn custom object capturing completed onboarding steps and dates. Bullhorn does not replicate Eddy's guided onboarding workflow builder. We document each active onboarding workflow, its step count, the assigned approver, and the completion status for each employee so the customer's Bullhorn admin can rebuild the workflow in Bullhorn's onboarding module or document it as a standard operating procedure.

Eddy training completion records (course name, completion date, expiry date, certification status) map to Bullhorn custom fields on the Candidate record or a training custom object. Bullhorn does not have a native LMS or training certification tracking module. We extract training history and completion dates from Eddy and preserve them in Bullhorn custom fields. Customers with extensive training compliance requirements may need to maintain a separate LMS; we document the training record count during scoping to inform that decision.

The Eddy employee directory view is derived from employee records. We migrate the underlying employee data that populates the directory into Bullhorn ClientContact records with custom fields for directory-specific attributes (photo URL, phone extension, reporting manager, office location). We preserve organizational hierarchy information via Bullhorn ClientContact custom fields for manager_id reference. Bullhorn's org chart is a community or portal feature; we note this during the handoff.

Eddy's HR and payroll modules are not fully integrated per reviewer feedback, and payroll data export requires manual steps or CSV export. We extract available pay-related records (pay rate, pay frequency, last pay date) as Bullhorn custom fields on the Candidate record for staffing operations that use Bullhorn's payroll module (Bullhorn Pay). We flag that full pay run history requires manual export from Eddy before migration scoping finalizes, as automated extraction may be incomplete.

Eddy location records (addresses, location names, regional codes) map to Bullhorn ClientCorporation Address records. Multiple Eddy locations per company map to multiple ClientCorporation Address records with address type differentiation (primary, branch, remote). We preserve the location-to-employee association via custom fields on the Employee-equivalent Candidate record.

Eddy stores industry-specific HR data as custom fields. We map these to Bullhorn custom fields on the appropriate entity (Candidate, ClientContact, ClientCorporation). Bullhorn limits custom fields per entity depending on edition. Bullhorn ATS supports a limited number of custom fields; Front Office Growth and Enterprise allow custom objects with up to 55 fields each. We audit the Eddy custom property count during scoping and confirm whether the customer's Bullhorn edition has sufficient capacity before migration.

Eddy employment status (active, on_leave, terminated) maps to Bullhorn Candidate status (Active, Day Labor, On Hold, Placed, etc.) plus a custom field edy_employment_status__c capturing the original Eddy value for audit. Terminated employee records migrate as Day Labor or Inactive Candidate records with the termination date preserved in a custom field. Active employee records migrate as Active Candidate records.

Eddy hire_date maps to Bullhorn date fields on the Candidate record. We compute tenure in months and store it in a custom field for reporting. Anniversary dates and probation end dates from Eddy migrate as custom date fields. These are used in Bullhorn reporting for tenure-based filtering.