Migrate from hireEZ to Recruit CRM & ATS

hireEZ candidate profiles (contact details, work history, skills, education, and enrichment data) map directly to Recruit CRM candidate records. We use candidate email as the canonical dedupe key. We validate email addresses against standard deliverability patterns before import: addresses failing format checks (missing @, invalid domain, no MX record) are flagged in a pre-import reconciliation report for customer review before candidate records are committed to Recruit CRM. Credit-based enrichment flags (stale data from records last enriched mid-billing-cycle) are preserved in a custom field for the customer's review.

hireEZ Projects store requisition metadata including job title, department, location, salary range, priority, and pipeline stage assignments. We map these directly to Recruit CRM Job records. Project-to-candidate associations are preserved as candidate-job assignments in Recruit CRM's pipeline view, maintaining the hiring context that candidates were sourced under.

Job Requisition records from hireEZ map to Recruit CRM Jobs with the same metadata (title, department, location, salary range, priority). We map hireEZ stage assignments to Recruit CRM pipeline stages, which are configurable per job. The customer configures pipeline stages in Recruit CRM during setup; we document the source stage assignments for stage mapping.

hireEZ talent pools are named collections of candidates grouped by skill, role, or talent community. We export pool membership as candidate-to-pool relationships and map these to Recruit CRM Lists. A candidate can belong to multiple Recruit CRM Lists, matching the many-to-many relationship in hireEZ. Pool names and candidate membership counts are preserved in List descriptions for reference.

hireEZ Automated Campaigns store outreach sequences across email, SMS, and LinkedIn InMail. We migrate campaign membership (which candidates were added to which campaigns) and candidate engagement history (opens, clicks, replies, InMail views, scheduling events) as candidate activities in Recruit CRM. Campaign step logic, sequence step definitions, step timing, and outreach cadence states do not export because they are tied to hireEZ's internal messaging infrastructure. We deliver a written campaign inventory with each sequence's steps, timing, and recommended Recruit CRM automation rebuild approach.

Activity logs from hireEZ capture email opens, clicks, replies, InMail views, and scheduling events tied to candidates and projects. We preserve the full activity timeline per candidate in Recruit CRM's activity log with original timestamps. Timestamp formats may vary by ATS integration source; we normalize to ISO 8601 before import.

Interview scheduling events and calendar sync records from hireEZ are preserved as interview entries linked to the corresponding candidate and job in Recruit CRM. Scheduling metadata (interviewer, date, time, meeting link or location) migrates directly. Note: a Reddit thread for Recruit CRM users identifies that deleted meetings do not sync back to Google Calendar, a platform-level limitation we document for the customer's awareness but do not resolve in migration scope.

Custom fields on hireEZ candidate profiles vary by customer configuration. We discover all custom properties during scoping, map them to equivalent Recruit CRM custom fields (Text, Number, Date, Dropdown, or Multi-select based on data type), and flag any properties with no matching target field in Recruit CRM for customer resolution before migration.

Enterprise customers using hireEZ Auto Sync with a connected ATS (Greenhouse, Lever, Bullhorn, iCIMS, Workday) may have candidate records created or updated through bidirectional sync. These records may have conflicting IDs or duplicate email addresses across hireEZ and the ATS. We deduplicate on candidate email, resolve the most recent update timestamp as authoritative, and flag records with ambiguous merge candidates for customer review before import.

hireEZ native analytics dashboards and reports do not export in transferable format. We migrate the underlying funnel data (source, stage, hire dates, pipeline timestamps) as candidate and job record fields, enabling Recruit CRM's native reporting to reconstruct the funnel. Dashboard-level visualizations must be rebuilt by the customer's team in Recruit CRM's reporting module.