Migrate from Greenhouse to Crelate

Greenhouse Candidate records map to Crelate Person records. We preserve all standard fields (name, email, phone, social URLs, tags) and map Greenhouse's custom field values by type: single_select to Crelate's picklist, multi_select to multi-select, currency to currency, date to date. Phone number formats are normalized during transform to match Crelate's expected format. Any Greenhouse-specific free-text notes migrate as activity entries on the Person record.

Greenhouse Application records link a Candidate to a Job. We preserve application date, rejection or hire status, current pipeline stage, and stage history timestamps as an activity log. Rejection reasons and anonymized notes migrate as Activity records attached to the Application. Application UUID from Greenhouse is preserved as a reference field for audit trails.

Greenhouse Job records map to Crelate Job (Job Order) records. We preserve job title, department, office location, open/closed status, opening date, and full job description as structured fields. Job posting URLs are migrated as reference links on the Job record rather than re-created in Crelate's job board distribution tool. Pipeline stage names and order are mapped separately as part of the Pipeline Stages configuration.

Greenhouse Offers attached to Applications map to Crelate Offer records. We preserve start date, salary, equity, and any custom offer fields. Offer status (pending, accepted, declined, retracted) migrates as a status field on the Offer. The Application linkage is preserved by resolving the Application UUID to the Crelate Application record during import.

Greenhouse Scorecards store structured evaluator feedback tied to Interview Plans. We map scorecard questions and selected ratings to Crelate as Activity records with a custom structured format (question text as label, rating as value) because Crelate does not have a native scorecard object equivalent to Greenhouse's Interview Kit structure. Free-text evaluator comments migrate as Activity notes. The customer's admin rebuilds Greenhouse's scorecard templates as Crelate's form or checklist templates post-migration.

Greenhouse Users (Site Admin, Recruiter, Hiring Manager) map to Crelate Users. We resolve by email match and map role assignments from Greenhouse to Crelate's permission model. Owner assignment on records (Candidates, Applications, Jobs, Offers) is remapped to Crelate User IDs during import. Any Greenhouse User without a matching Crelate User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

Greenhouse custom fields across all value types (short_text, long_text, yes_no, single_select, multi_select, currency, number, date, url, user_reference) are pre-created in Crelate with equivalent types before data import. We handle Greenhouse's field value transforms: multi_select arrays become comma-separated strings or Crelate's multi-select format; user_reference fields are resolved via the User mapping. Greenhouse's custom field on applications vs on candidates distinction is preserved by linking to the correct parent object in Crelate.

Greenhouse's flat office/department structure (Core) maps directly to Crelate's org units. Greenhouse's hierarchical tiered structure (Plus/Pro) requires flattening or preserving as a parent-child relationship in Crelate depending on the customer's preferred org model. We validate the customer's Greenhouse tier at scoping time and discuss whether to flatten or preserve the hierarchy. Crelate's org structure is configurable without tier gating, so all customers have access to the same structural options.

Tags on Greenhouse Candidates and Applications migrate as Tags on Crelate Person records. Greenhouse allows unlimited tags; we preserve them as label arrays and map them to Crelate's tagging system. Tagsets (grouped tag collections) in Greenhouse are mapped to Crelate's tag categories if used, or flattened to a single tag list if the customer prefers simplicity.

Greenhouse Plus and Pro CRM events (calls, emails, notes, meetings) map to Crelate Activity records. For Core customers, all activity types are collapsed into Crelate's unified activity timeline since Greenhouse Core only supports a single CRM event type. We preserve timestamps, disposition notes (for calls), and body text (for notes and emails) as structured Activity fields. Activity parent links are resolved to the Person or Job record in Crelate.

Greenhouse Pipeline Stages define the hiring workflow and map to Crelate's Pipeline and Stage configuration. We preserve stage names, order, and any stage-specific questions as Stage metadata in Crelate. Custom stage names and stage-dependent scorecards are mapped field-by-field. The pipeline name from Greenhouse maps to a Crelate Pipeline with the same name, and stage probability percentages are preserved as informational fields on each Stage.

Greenhouse tracks candidate source (referral, job board, direct apply) as a field on the Application. We preserve source attribution and migrate it to Crelate's Source field on the Person or Application. Sourcing campaign UTM data stored in Greenhouse custom fields migrates to Crelate custom fields on the Person record for marketing attribution continuity.

Resumes, cover letters, and portfolio files attached to Greenhouse Candidates or Applications migrate as binary attachments in Crelate. We handle file type detection, preserve the original filename, and link files back to the correct Person or Application record. Crelate's file storage limits are validated against the total attachment volume during scoping.

Greenhouse Job Posts (published listings on job boards and careers pages) are not re-created in Crelate. We preserve the Job Post reference URL and job board name as metadata fields on the Crelate Job record. The customer's admin republishes active job postings in Crelate's job board distribution tool post-migration. Job description content migrates in full as structured fields on the Job record.