Migrate from hireEZ to Crelate

hireEZ candidate profiles map to Crelate Contact records. The candidate's email address is the canonical dedupe key during import. We extract name, phone, location, social profile URLs (LinkedIn, GitHub, etc.), education, and work history from hireEZ's exported profile fields and map them to Crelate's corresponding Contact fields. hireEZ's contact accuracy issues (70-80% reported) require a validation pass during import: we flag records with malformed email patterns or missing required fields for customer review before campaign re-launch.

hireEZ Projects (job requisitions) store the hiring context including job title, department, location, employment type, and pipeline stage assignments. We map these directly to Crelate's Job object. Project-to-candidate associations are preserved by linking the imported Contact to the target Job via Crelate's candidate-to-job relationship. If hireEZ projects use custom stage names, we configure Crelate pipeline stages to match during the migration window.

hireEZ talent pools are named collections of candidates grouped by skill, role, or talent community. Crelate does not have a native talent pool object with the same membership model. We preserve pool membership by creating a Crelate Saved Search for each talent pool using the same filter criteria (skills, location, seniority, etc.), and we add a tag matching the pool name to every member Contact record. The customer reviews and adjusts Saved Search criteria post-migration since the hireEZ enrichment data that powers pool membership may differ from Crelate's native search fields.

hireEZ automated campaigns store outreach sequence definitions across email, SMS, and LinkedIn InMail channels. Crelate supports bulk email distribution and activity logging but has no native multi-step sequence builder with built-in delays, step branching, or cadence logic. We do not migrate sequence step states or cadence definitions. We migrate campaign membership and candidate engagement history (opens, clicks, replies) as Activity notes on the Contact record. We deliver a written inventory of all active sequences, step counts, channel assignments, and target pool sizes for the customer's admin to rebuild in Crelate's workflow context or a third-party sales engagement tool.

hireEZ email engagement history (opens, clicks, replies, sends) migrates to Crelate Note records linked to the parent Contact. We preserve the email subject, send timestamp, open timestamp, click timestamp, and reply content as structured note fields. Email engagement data is scoped to what hireEZ exports in its UI-based or ATS-synced data; the raw email body may not be available in all export configurations.

hireEZ call engagement records (duration, disposition, recording URL if stored) map to Crelate Activity entries on the Contact record. We preserve call duration and timestamp; disposition notes migrate as Activity detail text. Call recordings stored in hireEZ are not directly migratable and are flagged as a separate data asset requiring manual transfer if retention is required.

hireEZ meeting engagements (scheduled events, calendar syncs) map to Crelate Activity entries on the Contact record. We preserve the meeting timestamp, title, location, and any recruiter-added notes. Meeting event links or conferencing data migrate as Activity detail text.

hireEZ notes attached to candidate profiles migrate directly to Crelate Note records linked to the Contact. We preserve the note body, author (mapped to the Owner/User), and creation timestamp. Note attachments (documents, images) are flagged for manual transfer if the hireEZ export includes them; we do not extract embedded attachment binary data through UI-based export.

hireEZ job requisitions store the full requisition metadata including department, location, salary range, employment type, priority, and requisition owner. We map these fields to Crelate Job object fields directly. Salary range fields migrate as text or numeric depending on Crelate field type configuration in the destination environment.

hireEZ custom fields on candidate profiles vary by customer configuration. We discover all custom properties during scoping (a required pre-migration step given hireEZ's lack of API documentation), map each to a Crelate custom field of the equivalent type (text, picklist, numeric, date, checkbox), and flag any hireEZ custom fields with no matching Crelate field type as requiring admin configuration before import. Custom field values migrate as data in the mapped Crelate field.

If hireEZ Auto Sync is active with a connected ATS (Greenhouse, Lever, Bullhorn, etc.), candidate records may exist in both hireEZ and the connected ATS. We deduplicate on candidate email, preferring the most recently updated record from either system. The Auto Sync configuration itself is not migratable; Crelate's own ATS integration or native sourcing tools replace it in the destination environment. We flag any records with conflicting stage assignments or duplicate candidates for customer review before import.

hireEZ's EZ Agent automates screening, sourcing, and scheduling workflows using agentic AI. These agentic workflow definitions are tied to hireEZ's internal AI infrastructure and do not export. We do not migrate agentic workflows as code. We deliver a written inventory of active EZ Agent workflows, their trigger conditions, action sequences, and target outcomes for the customer's team to evaluate against Crelate's Co-Pilot AI capabilities, which handle screening assistance and process recommendations rather than fully autonomous agentic execution.