Migrate your HigherMe data

HigherMe job postings include title, description, location, screening questions, fit-score weighting, and distribution status across integrated job boards. We extract the full job record and its associated application funnel configuration. Custom screening questions are preserved as structured key-value pairs.

Applications represent a candidate's response to a specific job posting. We extract applicant contact details, availability windows, screening question answers, fit-score output, application source channel, and timestamp. Status transitions (new, reviewed, interviewed, hired, rejected) are preserved as a timeline.

The candidate record aggregates all applications across jobs and locations for the same individual. We map candidate name, email, phone, work authorization status, and geographic distance from the job location. Video application blobs are referenced by URL and carried forward if the destination supports video embedding.

30-second video cover letters are stored as hosted media URLs rather than raw video files. We preserve the URL reference and metadata (duration, upload timestamp). Destination platforms without native video support receive the URL as a link field; platforms with native video objects may require re-upload or re-recording.

Custom screening questions per job include single-choice, multi-choice, and free-text types with weighted scoring. We map question text and weight configuration to equivalent custom fields in the destination ATS. Questions with conditional branching logic may require simplification during schema translation.

HigherMe supports multi-location franchise configurations where each store is a discrete hiring unit with its own job postings and applicant pool. We preserve location identifiers, address, and manager assignment. For multi-location customers, we chunk migration by location to avoid cross-tenant data contamination.

Fit scores are calculated per application based on availability match, distance from location, and screening question responses. The numeric score (0–100) is stored on the application record. We map it as a custom numeric field; destinations without native fit-score concepts receive it as a custom pipeline property.

WOTC eligibility questionnaire responses and associated tax credit data attach to the candidate record. We preserve the questionnaire answers and eligibility flag. Note that WOTC eligibility is US-specific and not applicable in Canadian or other international deployments.

Interview scheduling, date/time, interviewer assignment, and interview type (phone, video, in-person) are tracked as events linked to the application. We extract the full interview record including rescheduling history and candidate confirmation status.

Manager notes and structured feedback attached to applications are stored as free-text with author and timestamp. We map these as conversation or activity entries in the destination ATS. Multi-author feedback threads are flattened into a linear note history to preserve all content.

Background check results are handled by integrated third-party providers (First Advantage and similar) and are not stored as readable records within HigherMe. We do not migrate background check data — candidates must re-initiate the check through the new platform's integration.

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 recruiting scope and require separate access credentials.

HigherMe Payroll is a distinct product covering payroll processing, tax filing, and wage disbursement. Payroll history and tax documents are not accessible via the ATS API and are out of scope for recruiting-data migrations.