Migrate from hireEZ to Bullhorn ATS & CRM

hireEZ candidate profiles (contact details, work history, skills, education, engagement activity) map 1:1 to Bullhorn Candidate. We deduplicate on candidate email address as the canonical key and preserve hireEZ custom candidate properties as Bullhorn custom fields on the Candidate entity. Bullhorn's Candidate record supports up to 55 fields per custom object (customObject1s through customObject10s on Enterprise and Growth editions); we discover all hireEZ custom properties during scoping and pre-provision matching Bullhorn fields before import.

hireEZ Projects store requisition metadata (job title, department, location, salary range, priority, pipeline stage assignments) and map directly to Bullhorn JobOrder. We preserve project-to-candidate associations as JobSubmission records in Bullhorn, linking the Candidate to the JobOrder with the corresponding submission status. JobOrder status values (Open, Pending, Closed, Cancelled) map from hireEZ project stage.

hireEZ does not have a native Company object but Company data attached to candidates maps to Bullhorn ClientCorporation. Where a hireEZ candidate record references an employer or previous company, we create a ClientCorporation record in Bullhorn and link it via the Candidate's currentCompany or employmentHistory fields. ClientCorporationAddress, Industry, and URL migrate as typed fields.

hireEZ Talent Pools (named collections of candidates grouped by skill, role, or talent community) have no native Bullhorn equivalent. We map pools to Bullhorn Lists and preserve candidate-to-pool membership. Lists in Bullhorn support saved search criteria or manual membership. If the customer uses talent pools for active talent community segmentation, we recommend using Bullhorn Smart Lists (saved searches) to recreate that functionality post-migration; manual membership-based pools migrate as standard Lists.

hireEZ Automated Campaigns store outreach sequences across email, SMS, and InMail channels. We migrate campaign membership and candidate engagement history (opens, clicks, replies, InMail views) but do not transfer sequence step states, which are tied to hireEZ's internal messaging infrastructure and do not export. We document each hireEZ campaign with its candidate membership, engagement summary, and recommended Bullhorn Automation or Engagement replacement so the customer's admin can rebuild sequences post-migration.

hireEZ activity logs (email opens, clicks, replies, calls, meetings, scheduling events) map to Bullhorn Task, Event, and Note records. Email activities map to Bullhorn Task with activity type preserved in a custom field; call records map to Task with TaskSubtype=Call and CallDurationInSeconds; meeting records map to Bullhorn Event with start and end times; notes map to Note. We preserve the full activity timeline per candidate, linking each activity to the Candidate record. Timestamp formats are normalized to Bullhorn's expected ISO 8601 format during transform.

Custom fields on hireEZ candidate profiles vary by customer configuration. We discover all custom properties during scoping, classify them by data type (text, number, date, picklist, boolean), and map them to equivalent Bullhorn Candidate fields. Bullhorn allows custom fields directly on Candidate or through customObject1s through customObject10s depending on the customer's Bullhorn edition (10 on Front Office Growth and Enterprise, 2 on Bullhorn ATS). Fields with no matching Bullhorn target are flagged for customer review and mapped to a catch-all text field or Note attachment.

hireEZ interview scheduling events and calendar syncs are recorded as activity entries and migrate to Bullhorn Event records. We preserve scheduling metadata (interview type, interviewer name, location, start and end times) and link each Event to the corresponding Candidate and JobOrder via the Bullhorn EventRelation entity. If hireEZ stores interviewer notes or feedback, those migrate as separate Note records attached to the Event.

hireEZ outreach sequence definitions and step logic are tied to hireEZ's internal messaging infrastructure and do not export. We do not migrate sequences as code. We deliver a written inventory of every active hireEZ campaign with its cadence steps, timing, and messaging content, plus a recommendation for rebuilding each sequence in Bullhorn Automation (if licensed) or Bullhorn Engagement. The customer's admin or a Bullhorn implementation partner rebuilds sequences post-migration.

hireEZ analytics dashboards and reports are platform-native and do not export in transferable format. We migrate the underlying funnel data (candidate source, pipeline stage, hire outcome) as candidate activity records and note that dashboard-level analytics must be rebuilt in Bullhorn Reporting or a BI tool post-migration. We provide a data dictionary mapping every hireEZ funnel metric to the Bullhorn field or report type that provides equivalent visibility.

Enterprise Auto Sync creates bidirectional candidate records between hireEZ and the customer's connected ATS. When extracting from hireEZ, we deduplicate on candidate email address and flag records with conflicting IDs or duplicate emails for customer review. We do not attempt to resolve stage conflicts from the source ATS during hireEZ extraction; the customer's Bullhorn admin determines the canonical stage assignment for each conflicted record before import.

hireEZ Owners (recruiters assigned to projects and candidates) map to Bullhorn User records. We resolve owners by email match against the Bullhorn destination tenant's User table. Any hireEZ Owner without a matching Bullhorn User is held in a reconciliation queue for the customer's Bullhorn admin to provision before record import resumes. Inactive hireEZ owners map to inactive Bullhorn Users to preserve assignment history without creating ghost active users.