Migrate from EMP Trust HR to Bullhorn ATS & CRM

EMP Trust HR Employee records map to Bullhorn Candidate as the primary record. Bullhorn Person is not a standalone object but rather a contact sub-type within Candidate. The EMP Trust HR employee profile fields (name, address, phone, email, hire date, employment type, location) map directly to Bullhorn Candidate fields. Custom employee properties from EMP Trust HR are mapped to Bullhorn Custom Object fields on the Candidate record. We provision Bullhorn Custom Objects during schema design if the count of custom properties exceeds standard Candidate fields. Bullhorn editions: ATS Growth has no Custom Object support; Bullhorn ATS supports 2; Front Office Growth/Enterprise supports 10. Edition constraints are validated during scoping.

EMP Trust HR onboarding portal instances with portal state (started, in-progress, completed), associated task sets, and completion timestamps are migrated as structured records. The portal state migrates to Bullhorn Candidate custom fields tracking onboarding status. Bullhorn Onboarding (formerly Able, accessible at app.ableteams.com) is the native Bullhorn onboarding module for managing post-hire workflows and documents; we document the recommended onboarding package configuration using Bullhorn Onboarding field mappings and deliver the setup guide to the customer's admin. The onboarding portal branding assets (logos, welcome messages, video embeds) do not migrate; these require reconfiguration in Bullhorn Onboarding settings.

EMP Trust HR completed forms (legal forms, NDAs, non-competes, offer letters, policy acknowledgements, tax withholding, direct deposit, beneficiary forms) migrate as Bullhorn Document records attached to the Candidate. We extract the form definition name, completion status, completion timestamp, and e-signature metadata. Form logic and conditional branching are not preserved in the export; we document each form requiring rebuild in Bullhorn Onboarding or via Bullhorn Field Mappings. Completed form PDFs migrate as ContentDocument records linked via ContentDocumentLink to the Candidate.

I-9 Section 1 (employee self-completion) and Section 2 (employer or third-party notary verification) records from EMP Trust HR are among the highest-risk data artefacts in this migration. EMP Trust HR stores e-signature audit trail metadata within the Forms module using proprietary schemas. We reconstruct a standard e-signature envelope (signer ID, timestamp, IP address, certificate hash) for each form and write it as a Bullhorn Custom Object record I-9__c linked to the Candidate. We flag any I-9 record where Section 2 has not been completed by a third-party notary so the customer can plan for re-initiation of the remote verification workflow post-migration.

E-Verify case status codes (Verified, Tentative Nonconfirmation, DHS/DOJ Query) from EMP Trust HR migrate to Bullhorn Custom Object E-Verify__c with E-Verify case number, USCIS verification date, and case result fields. We preserve the DHS E-Verify case number as a reference field. Bullhorn does not have a native E-Verify module; compliance continuity requires the customer to either maintain the E-Verify integration within EMP Trust HR post-migration (if they continue a partial license) or configure Bullhorn Onboarding's I-9 and E-Verify compliance workflows if supported by their Bullhorn edition and add-ons.

Onboarding tasks assigned to new hires, managers, HR staff, and IT in EMP Trust HR migrate to Bullhorn Task records linked to the Candidate. Task status (not started, in progress, completed), due dates, assignees, and completion timestamps transfer. Bullhorn Tasks are standard activity records; they do not have native hierarchical task grouping equivalent to EMP Trust HR's onboarding package task sets, so we document the original task hierarchy for the admin to restructure in Bullhorn if needed.

Training courses assigned via EMP Trust HR's new hire learning portal with completion flags, scores, and assignment timestamps migrate to Bullhorn Candidate custom fields (training course name, completion date, score). Bullhorn does not have a native LMS; if the customer requires a full training management module post-migration, a third-party LMS integration is recommended. We preserve the training record history as structured custom field data rather than as an active training assignment.

Background check orders and results sourced through EMP Trust HR's pre-built integrations (CastleBranch, AccurateBackground, BirdDogHR) migrate as Bullhorn Custom Object BackgroundCheck__c records with order date, status, result summary, and vendor name. Raw vendor PDF reports migrate as ContentDocument records linked to the Candidate. EMP Trust HR does not expose raw background check PDF reports as structured fields; we extract the result summary and document the vendor reference number so the customer can request full reports directly from the background check provider if needed.

Benefits selections captured during onboarding in EMP Trust HR (plan choices, dependent information, beneficiary designations) migrate as Bullhorn Custom Object BenefitsEnrollment__c records attached to the Candidate. These are historical enrollment snapshots, not live feeds, because EMP Trust HR does not maintain a live connection to benefits carrier APIs for ongoing changes. Active ongoing benefits changes in progress at migration time must be captured separately from the HRIS export and manually reconciled. Bullhorn does not have a native benefits administration module; the customer should plan to maintain benefits data in their payroll provider or a dedicated benefits admin platform.

Employer-defined custom forms, HR policies, and handbook acknowledgements from EMP Trust HR migrate as Bullhorn Document records linked to the Candidate with form definition name, completion status, and e-signature metadata. Conditional branching logic within custom forms is not preserved in the export; we document each custom form requiring rebuild in Bullhorn Onboarding and identify the Bullhorn form field equivalents for the customer's Bullhorn admin.

Candidates transitioned from Greenhouse or Lever to EMP Trust HR via the ATS integration retain only the fields mapped by the EMP Trust HR integration configuration. We extract all mapped fields from EMP Trust HR and write them to Bullhorn Candidate. Any original ATS candidate fields not included in the EMP Trust HR integration field map are flagged during scoping; the customer should retrieve these from the original ATS export before the integration fires. We document the EMP Trust HR integration field map during scoping to identify gaps.

EMP Trust HR pre-built integration connectors (ADP, Workday, Oracle, SAP, UKG, Greenhouse, Lever) and related sync configurations, credential mappings, and webhook endpoint settings are not migrated. Integration endpoints, credentials, and sync schedules must be re-established from scratch in Bullhorn's integration marketplace (Bullhorn Data Hub, Bullhorn Automation, or third-party iPaaS). We deliver a written inventory of each active integration requiring rebuild with recommended Bullhorn integration paths and partner contacts.