Migrate from HigherMe to Recruit CRM & ATS

HigherMe job postings map to Recruit CRM Job records. We extract job title, description, location address, screening questions with weighted scoring, and fit-score weighting configuration. HigherMe's fit-score algorithm per job becomes a documented configuration note for Recruit CRM custom field setup. The HigherMe location identifier maps to a Recruit CRM custom location_text field because Recruit CRM does not have a native multi-tenant hierarchy. For multi-location migrations, we chunk by location_id to produce one Recruit CRM Job per HigherMe job-location combination.

HigherMe Candidate records (aggregated across all applications and locations for the same individual) map to Recruit CRM Candidate. We preserve name, email, phone, work authorization status, geographic distance from job location, and WOTC eligibility flag as custom fields. Candidate uniqueness is enforced by email dedupe. If the same individual appears under multiple HigherMe store locations, we merge into a single Recruit CRM Candidate record to avoid duplicate profiles.

HigherMe Application records map to Recruit CRM Candidate-Job associations. The association carries application status, source channel (job board referral or direct), application timestamp, and screening question answers. Recruit CRM's associated_fields API stores per-application custom field values against the candidate-job pair. Fit-score numeric value (0-100) migrates as a custom associated field since Recruit CRM does not have a native fit-score concept.

HigherMe custom screening questions per job (single-choice, multi-choice, free-text) map to Recruit CRM custom fields on the Candidate-Job association. We extract question text, answer type, and weight configuration from HigherMe's job schema. Recruit CRM's associated_fields endpoint (POST /v1/candidates/associated-field/{candidate}/{job}) accepts field_id and value pairs per candidate-job pair. We pre-create the custom field schema in Recruit CRM before migration and map field_id references during the transform phase.

HigherMe fit-score (0-100) per application is stored as a numeric value on the Application record. Recruit CRM has no native fit-score object. We create a custom numeric field in Recruit CRM and populate it via the associated_fields API for each candidate-job pair. This preserves the relative ranking for migration audit and allows Recruit CRM users to recreate scoring logic using their own formula or a third-party scoring tool.

HigherMe stores 30-second video cover letters as hosted media URLs. Recruit CRM supports native video interview recording but may not auto-import HigherMe's hosted video URLs. We preserve the HigherMe video URL as a custom text field on the Recruit CRM Candidate record with a label like 'HigherMe Video Cover Letter URL'. Customers verify whether Recruit CRM's native video player can ingest the hosted URL; if not, candidates re-record in Recruit CRM's video interview module post-migration.

HigherMe multi-location franchise configurations require tenant-aware chunking during migration. Each store has its own job postings, applicant pool, and manager assignments. We extract location identifier, store name, address, and manager email, then map to a Recruit CRM custom location field on Job records. For chains with 50+ locations, we coordinate a location inventory list from the customer during scoping to ensure complete coverage and avoid missed stores.

HigherMe interview scheduling, date/time, interviewer assignment, and interview type (phone, video, in-person) map to Recruit CRM Interview records linked to the Candidate-Job pair. Interviewer email resolves to a Recruit CRM User if an active account exists; otherwise the interview record stores the name as a text field. Interview type maps to Recruit CRM's interview type dropdown.

HigherMe free-text manager notes attached to applications map to Recruit CRM Note records or Activity entries on the Candidate profile. We preserve author name, timestamp, and full note body. Multi-author notes migrate as separate Note entries with the original author attribution. If the customer uses Recruit CRM's Activity feed, notes land as activity entries with type=NOTE.

HigherMe WOTC eligibility questionnaire responses and associated tax credit data attach to the Candidate record. We preserve the questionnaire answers and eligibility flag as custom fields in Recruit CRM. Note that WOTC eligibility is US-specific tax credit logic; Recruit CRM has no native WOTC object, so the data migrates as documentation for the customer's HR or finance team to review. Non-US/Canadian candidates flagged by geographic distance anomalies or work authorization inconsistencies migrate with a migration flag for admin review.

Background check results flow through HigherMe's integrated third-party provider (First Advantage) and are not stored as readable records in the HigherMe ATS API. We do not migrate background check data. Candidates with completed checks in HigherMe require a new check initiation in Recruit CRM or a direct re-request from the same third-party provider. We document this gap in the migration scope and recommend coordinating re-check timing with First Advantage or the customer's preferred background check vendor before cutover to avoid processing delays for active placements.

Post-hire onboarding documents, I-9 forms, and new-hire paperwork live in HigherMe HR Software, which is a separate product tier from the ATS. We do not migrate onboarding document blobs as they fall outside the ATS data model and API scope. If the customer needs onboarding continuity, they should plan a parallel HR migration to their preferred HRMS or accept manual re-documentation for new hires processed during the transition window.