Migrate from hireful to Crelate

hireful Vacancies map directly to Crelate Jobs. We export vacancy title, description, status, and pipeline stage via hireful's CSV export and map them to Crelate's job_name, description, status, and pipeline stage fields. The vacancy pipeline stage ordering from hireful requires manual reconfiguration in Crelate's pipeline builder since stage sequence is stored as a custom property in hireful rather than a native ordering field. Job board posting metadata (which boards each vacancy was posted to) is recorded as a migration log entry rather than a Crelate field, since Crelate manages job board distribution through its own marketplace configuration.

hireful Candidate records map to Crelate People records. The hireful candidate profile fields (name, email, phone, work history, education, skills) map to corresponding Crelate person fields. CV and resume attachments migrate as Crelate document attachments linked to the person record. Communication history from hireful's candidate timeline is exported as a structured CSV and replayed as Crelate Activity records against the person after insert.

Each hireful Application record (candidate-to-vacancy pairing) maps 1:1 to a Crelate Job Application. The application status (Applied, Shortlisted, Rejected, Offer, Hired) migrates to Crelate's application_status field. The job reference on the application resolves to the migrated Crelate Job; the candidate reference resolves to the migrated Crelate Person. If a candidate has applied to multiple vacancies in hireful, each application becomes a separate Crelate Job Application record linked to the same Person.

Custom application forms from hireful Pro and above tiers are reconstructed in Crelate using Crelate's custom form builder. Each hireful custom form field maps to a Crelate question, and each question is linked to a specific Crelate field on the parent Job Application or Person record via Crelate's field mapping configuration. Since Crelate field mappings are unique per question per form, we document the mapping matrix during scoping and configure it in Crelate's staging environment before production migration. Pre-set form fields from hireful Go and Grow tiers map directly to equivalent Crelate standard fields.

Recruiter scoring stored against hireful Application records migrates to Crelate's rating or evaluation fields on the Job Application. Numerical scores transfer as-is. Free-text evaluation notes transfer to Crelate's notes field on the Job Application or as an Activity of type Note. If hireful's scoring used a named scale (stars, points, weighted criteria), we preserve the scale label in the field mapping documentation so Crelate's admin can calibrate the destination rating system consistently.

Interview events from hireful Grow and Pro tiers migrate to Crelate Activities of type Event. The interview date, time, duration, location, and interviewer assignment transfer to corresponding Crelate Activity fields. Crelate's EventRelation records link the interview to the relevant Person (candidate) and User (interviewer). Self-service scheduling links from hireful are not carried forward; the customer configures Crelate's scheduling integration (Calendly, Outlook, Google Calendar) post-migration if required.

hireful hiring manager seat assignments (unlimited on all hireful tiers) are mapped to Crelate User access records. We export the portal user list and their vacancy access scope from hireful's admin interface. In Crelate, we assign hiring managers as Users with the appropriate Job-level access permissions. The hiring manager portal interface itself does not migrate; Crelate's sharing model and hiring manager-facing views are configured post-migration using Crelate's standard access controls.

CVs and uploaded documents attached to hireful Candidate records are downloaded from hireful's interface and re-uploaded to Crelate as document attachments against the corresponding Person record. File naming conventions from hireful are preserved in the Crelate document record. We flag any CV files that exceed Crelate's attachment size limits for manual handling or alternative storage (Crelate supports linking to external document stores via URL).

hireful's automated candidate data deletion flags and retention timestamps are stored as system properties and do not appear in the standard CSV export. We extract these values from hireful's admin interface during scoping and carry them as a separate metadata file in the migration package. Crelate does not have a native GDPR deletion scheduling field, so the customer maintains the metadata file post-migration and runs deletion events manually in Crelate according to their retention policy. The metadata file format (CSV or JSON) is agreed with the customer during scoping.

hireful's native integrations with TotalJobs, Reed, CV Library, and Indeed are configured per vacancy in hireful. These integrations do not have direct Crelate equivalents since Crelate uses its own job board marketplace and API-based posting. We record which boards each hireful vacancy was posted to as a metadata entry in the migration log. The customer uses Crelate's job board distribution tools to rebuild postings post-migration, referencing the migration log for the original board list.

hireful's EDI and D&I tools including anonymised applications and diversity benchmarking are hireful-native features with no standard equivalent in Crelate. Anonymised application data (where candidate name and contact details are withheld) migrates as standard candidate records; the anonymisation flag does not carry forward. Diversity benchmarking reports are documented as a written inventory for the customer to evaluate Crelate's D&I add-ons or third-party tools post-migration.

Active hireful recruiter users are mapped to Crelate Users by email match. The hireful plan tier determines the recruiter licence count (1 on Go, 2 on Grow, unlimited on Pro and Hero). We export the active user list and their plan tier from hireful and use it to plan Crelate seat provisioning. Unlimited hiring manager seats from hireful map to Crelate User provisioning, where hiring manager-level access is assigned via Crelate's sharing and permission sets rather than a separate seat type.