Migrate from HigherMe to Crelate

HigherMe franchise tenants manage discrete store locations, each with its own job postings and applicant pools. Crelate does not have a native store or tenant hierarchy — store identifiers migrate as a custom field on the Job record (e.g., store_location__c) and as a Tag on each candidate record. We chunk the migration by location identifier during scoping to prevent cross-store applicant contamination. For chains with 50+ locations, this requires a location inventory from the customer before migration begins.

HigherMe job postings (title, description, location, screening questions, distribution status) map directly to Crelate Job records. The job's location address migrates to Crelate's location field, and the fit-score weighting configuration migrates to a custom field since Crelate does not compute algorithmic weights natively. Job distribution status (e.g., Indeed, Snagajob) is preserved as a tag or note — Crelate does not syndicate to job boards natively but supports integrations with Indeed, Dice, and CareerBuilder.

HigherMe Candidate records (name, email, phone, work authorization status, geographic distance from job) map to Crelate Contact. The work_authorization_status flag migrates to a custom Contact field, and geographic distance data migrates to a numeric custom field. Candidates with multiple applications across jobs aggregate into a single Contact with activity history linked via Job submissions.

HigherMe Applications (candidate response to a specific job) map to Crelate application records linked to the Job and Contact. Screening question responses migrate as form submission answers attached to the application. The fit-score numeric value (0-100) migrates to a custom numeric field on the application record. Application source channel (e.g., Indeed, Snagajob, text-to-apply) migrates to a custom field or tag.

HigherMe custom screening questions per job (single-choice, multi-choice, free-text with weighted scoring) map to Crelate Application Forms and custom fields on the Contact or Job record. Question text and weight configuration migrate as form question definitions in Crelate, and the weighted scoring outputs map to custom numeric fields since Crelate does not calculate weighted screening scores. We flag any questions with free-text responses that may exceed Crelate's text field length limits.

HigherMe fit scores (0-100) calculated per application from availability match, distance from location, and screening question responses do not have a Crelate native equivalent. We preserve the numeric score in a custom field (e.g., fit_score__c) on the application record and migrate the availability and distance inputs as separate custom fields for the customer's recruiting team to interpret against Crelate's rating forms. Fit-score thresholds used for auto-reject or auto-advance in HigherMe require manual configuration in Crelate's workflow or form logic post-migration.

HigherMe stores 30-second video cover letters as hosted media URLs rather than downloadable video files. We preserve the URL reference as a link field on the candidate or application record in Crelate. Crelate's support for embedded video varies by configuration — we verify video embedding capability during scoping and flag whether candidates may need to re-record for full native playback. URL references are migrated regardless of playback support so that the hosted content remains accessible.

HigherMe WOTC eligibility questionnaire responses and tax credit data attach to the candidate record. We preserve questionnaire answers and eligibility flags as custom fields on the Crelate Contact. Note that WOTC eligibility is US-specific and applies only to candidates in eligible hiring categories — international candidates or Canadian store locations have no WOTC eligibility and are flagged accordingly during migration. Crelate does not have native WOTC tracking; the custom field configuration is designed during scoping and validated in the sandbox migration.

HigherMe interview scheduling, date/time, interviewer assignment, and interview type (phone, video, in-person) migrate to Crelate Activity records. Interview type maps to Crelate's activity type field, interviewer assignment resolves by email against the Crelate User table, and date/time preserves the original timestamp. Interview events are linked to the application record in Crelate. Multiple interview rounds per candidate are supported as sequential activity entries.

HigherMe manager notes and structured feedback attached to applications migrate to Crelate Activity records of type Note. Author and timestamp preserve from the original record. Multi-author notes migrate as individual activity entries linked to the same application record. Free-text formatting migrates as rich text where Crelate's field type supports it.

Background check results flow through HigherMe's integrated third-party providers (First Advantage) and are not stored as readable records within the ATS. Candidates with completed checks will need to initiate a new check in Crelate or through their preferred background check vendor. We document this boundary in the migration scope and recommend coordinating the re-check timing to avoid processing delays for active hires in the pipeline.

Post-hire onboarding documents, I-9 forms, and new-hire paperwork live in HigherMe HR Software, a separate product tier from the ATS. These documents are not accessible via the recruiting API and are out of scope for the ATS migration. If the customer uses HigherMe HR Software and needs onboarding continuity, a parallel HR document migration or manual re-documentation plan is required separately.