Migrate from hireEZ to BambooHR

hireEZ Candidate records map to BambooHR Applicant records within the BambooHR ATS. When a candidate has been hired, the Applicant record transitions to an Employee record through BambooHR's native onboarding workflow. We use candidate email as the canonical dedupe key across both object types. We validate email addresses against standard deliverability patterns during import and flag records flagged as high-bounce-risk in hireEZ (derived from the known 30% bounce rate in enriched contact data) for customer verification before they enter BambooHR's ATS pipeline.

hireEZ Projects store job requisition metadata including title, department, location, and pipeline stage assignments. These map directly to BambooHR Jobs. We preserve the project-to-candidate association as a BambooHR custom applicant field that references the source hireEZ Project ID for audit trail. Job status (open, paused, filled, closed) migrates to BambooHR Job Status.

hireEZ Talent Pools are named collections of candidates grouped by skill, role, or talent community. BambooHR does not have a native Talent Pool equivalent; we map pool membership to BambooHR's Applicant Tags feature and create a custom tag per source Talent Pool. Pool descriptions migrate as tag metadata notes. Candidates belonging to multiple pools receive multiple tags. This is a configuration-level mapping that preserves the pool structure without requiring BambooHR custom objects.

hireEZ Automated Campaigns store multi-channel outreach sequences (email, SMS, InMail) with candidate engagement history. We migrate campaign membership and the most recent engagement timestamp per candidate as a BambooHR custom applicant field. The sequence step definitions (step timing, message content, cadence rules) do not transfer because they are tied to hireEZ's internal messaging infrastructure. We deliver a written inventory of each campaign's structure for the customer's admin to rebuild as BambooHR email templates and stage-based nurture sequences.

hireEZ Activity logs capture engagement events including email opens, clicks, replies, InMail views, and scheduling events. We preserve the activity timeline per candidate as BambooHR Applicant Notes with a standardized prefix (e.g., '[hireEZ:Email Open]') and the original timestamp. The full activity type taxonomy migrates as separate note entries. Note that BambooHR does not have a native engagement analytics dashboard equivalent to hireEZ's sourcing analytics; we flag this as a reporting gap for HR analysis reconstruction.

hireEZ interview scheduling events and calendar syncs recorded as activity entries map to BambooHR Interview records within the ATS. We preserve scheduling metadata (date, time, interviewer name, location or meeting link) and link the interview record to the corresponding Applicant and Job. Interview disposition notes migrate as a BambooHR Interview Note.

hireEZ custom fields on candidate profiles vary by customer configuration. We discover all custom properties during scoping, map them to BambooHR's custom applicant field system (found under Settings > HR Fields > Applicants), and flag any hireEZ properties with no matching BambooHR field type for customer decision. BambooHR supports text, date, number, dropdown, checkbox, and URL custom field types on Applicant records. Fields requiring type conversion (e.g., a multi-select list in hireEZ with no BambooHR multi-select equivalent) are escalated during scoping.

Enterprise Auto Sync on hireEZ keeps candidate records synchronized with the customer's ATS in real time. Records created or updated via ATS sync may have conflicting IDs or duplicate email addresses across both systems. We deduplicate on candidate email, resolving conflicting stage assignments by preferring the most recent timestamp. The customer must identify which ATS was the sync source during discovery so we can avoid double-counting records that already exist in both systems.

hireEZ analytics dashboards and reports are platform-native and do not export in transferable format. The underlying funnel data (candidate source, pipeline stage, hire outcome) migrates as applicant notes and custom field values, enabling reconstruction of basic hiring funnel reports in BambooHR's reporting module. Custom dashboards with sourcing analytics, market benchmarking, and competitor hiring activity from hireEZ do not have an equivalent in BambooHR and are documented as scope gaps for the customer's reporting team.

hireEZ outreach sequence definitions and step logic are tied to hireEZ's internal messaging infrastructure and do not export. We do not migrate sequence definitions. We deliver a written inventory of each sequence's trigger, steps, timing, and message content for the customer's admin to rebuild using BambooHR's email template system and stage-based workflows if applicable. For teams requiring full sales engagement cadence capability, we document the gap and recommend evaluating BambooHR's integration ecosystem for a compatible cadence tool.