Migrate from hireful to Recruit CRM & ATS

hireful candidate records (contact details, work history, CV attachment reference, communication history) map 1:1 to Recruit CRM candidate profiles. The hireful candidate ID is preserved in a custom field hireful_candidate_id__c for cross-system audit. CV and document files are extracted from hireful's download interface and re-uploaded to Recruit CRM against the corresponding candidate record; the original file name and upload timestamp are preserved in Recruit CRM's attachment metadata.

hireful Vacancy records (title, description, status, pipeline stage) map to Recruit CRM Jobs. The vacancy pipeline stage from hireful's custom property is mapped to Recruit CRM's pipeline stage on the Job record. Vacancy approval module settings (available on hireful Pro and above) do not migrate; we document the original approval workflow as a configuration note for Recruit CRM rebuild.

Each hireful candidate-to-vacancy pairing is an Application record. We map Applications 1:1 to Recruit CRM Job Applications and preserve application status (Applied, Shortlisted, Rejected, Offer Extended, Hired) as a standard field in Recruit CRM. Application timestamps (created date, last modified date) migrate to preserve the original sequence in the candidate pipeline.

Custom application forms with bespoke fields are available on hireful Pro and above. We export form field definitions and candidate responses separately, then reconstruct each form as a set of custom fields on the Recruit CRM Candidate record. Custom fields that exceed Recruit CRM's character limits (long-text fields mapped to character-limited text fields) are flagged during scoping for manual review or truncation handling. On hireful Go and Grow plans where only pre-set form fields are available, we map to Recruit CRM's standard candidate fields directly.

hireful hiring manager portal seat assignments are extracted from the platform and mapped to Recruit CRM User records with the appropriate role (Admin, Recruiter, Hiring Manager). Unlimited hiring manager seats on hireful map to Recruit CRM's unlimited user model, and we reconcile the total count during scoping. Any portal-specific notes or preferences attached to hiring manager accounts do not carry over and are flagged in the migration report.

Interview scheduling is available on hireful Grow and Pro tiers. Where interviews are recorded as structured events with candidate, vacancy, date, and interviewer assigned, we map them to Recruit CRM Interview records or Activity/Event equivalents. Self-service interview scheduling configurations do not migrate; the scheduling link and calendar integration are noted as a rebuild item in the handoff document.

Recruiter scoring and evaluation notes stored against hireful Application records are exported as structured score data and mapped to Recruit CRM's rating or evaluation custom fields on the Candidate or Job Application record. Free-text evaluation notes migrate as text fields. Numerical score values are mapped to Recruit CRM's numeric rating scale and flagged if the destination scale differs from the source.

Job board integrations configured in hireful (TotalJobs, Reed, CV Library, Indeed) are recorded as metadata in the migration log indicating which boards each vacancy was posted to. Actual job board postings do not migrate; the postings must be re-created manually in Recruit CRM's job board distribution settings or via VONQ integration post-migration. We provide a posting checklist for each board as part of the handoff document.

hireful GDPR automated deletion flags and retention period timestamps are stored as system properties and do not appear in the standard CSV export. We extract these values from the hireful admin interface during scoping and carry them as a custom metadata field on each affected Candidate record in Recruit CRM. The destination admin configures a GDPR reminder workflow in Recruit CRM using this preserved timestamp to honour the original retention schedule.

Recruiter licence counts and unlimited hiring manager seats are mapped to Recruit CRM User accounts. The total active user count from hireful is reconciled against Recruit CRM's user licensing during scoping. Pro-rated licence adjustments for mid-contract hireful exits are not calculated by FlitStack AI; the customer coordinates those with both vendors.