Migrate your Greenhouse data

Candidates are the primary person record in Greenhouse. We map all standard fields (name, email, phone, social URLs, tags) and preserve custom field values. Phone numbers and free-text fields may contain formatting inconsistencies we normalize during ingestion.

Applications link a Candidate to a Job. We preserve the application date, rejection or hire status, current stage, and all stage history timestamps. Rejection reasons and anonymized notes are migrated as metadata on the Application record.

Jobs are the requisition-level record. We preserve job title, department, office location, open/closed status, opening date, and job description. Job posting URLs are migrated as reference links rather than re-creating the postings on job boards.

Offers store the compensation package attached to an Application. We preserve start date, salary, equity, and custom offer fields. Offer status (pending, accepted, declined, retracted) is migrated as a stage value.

Scorecards are tied to Interview Plans and store structured evaluator feedback. Greenhouse stores them as nested objects under Applications. We map the scorecard questions and selected ratings; free-text commentary is migrated but may need manual review for formatting artifacts.

Users represent the internal team. We map their names, emails, and role assignments (Site Admin, Recruiter, Hiring Manager). Owner assignment on records must be remapped to user IDs in the destination system as those IDs are destination-specific.

Greenhouse supports custom fields across value types including short_text, long_text, yes_no, single_select, multi_select, currency, number, date, url, and user reference. We preserve all custom field values but flag multi-select arrays for value-mapping against the destination schema.

Offices and departments can be flat (Core) or hierarchical (Plus/Pro tiered structure). We preserve the flat structure universally; tiered hierarchies require Plus or Pro and we validate the customer's tier before migrating sub-department relationships.

Tags on Candidates and Applications are migrated as label arrays. Greenhouse allows unlimited tags; we preserve them as-is and map them to the destination's tagging or labeling system.

Plus and Pro tiers support unlimited CRM events (calls, emails, notes). Core limits CRM events. We migrate available event history and note the tier limitation in the scoping report. Events are mapped to the destination's activity or engagement log.

Job Posts represent the published listing on job boards and careers pages. We do not re-create postings in the destination. We preserve the Job Post reference URL and job board name as metadata on the Job record.

Pipeline stages define the hiring workflow. We preserve the stage names, order, and stage-specific questions. Custom stage names and stage-dependent scorecards are mapped field-by-field to the destination pipeline configuration.

Resumes, cover letters, and portfolio files attached to Candidates or Applications are migrated as binary blobs. We handle file type detection and link files back to the correct record in the destination. Very large files may require chunked transfer.

Greenhouse tracks candidate source (referral, job board, direct apply). We preserve source attribution as a field on the Application. Sourcing campaign UTM data stored in custom fields is migrated alongside other custom fields.