Migrate from Greenhouse to Recruit CRM & ATS

Greenhouse Candidate records map to Recruit CRM Contact (candidate mode). We preserve name, email, phone, social URLs, tags, and all Greenhouse custom field values including single_select, multi_select, currency, date, and user-reference types. Phone number formatting is normalized during transform. Tags migrate as label arrays. Source attribution (referral, job board, direct apply) and any UTM data stored in custom fields migrate as Contact fields or custom fields in Recruit CRM.

Greenhouse Application records — which link a Candidate to a Job and store the application date, rejection or hire status, current stage, stage history timestamps, and rejection reasons — map to Recruit CRM's application-level sub-records on the Contact. We preserve the full stage history timeline and application-level scorecards as notes or custom fields. Active applications in flight at cutover require a manual export step from the customer's Greenhouse UI as documented in the gotchas section.

Greenhouse Job records (requisition-level: title, department, office location, open/closed status, opening date, job description) map directly to Recruit CRM Job records. Job posting URLs and job board distribution references migrate as metadata fields. We map Greenhouse office and department assignments to Recruit CRM's organization hierarchy and flag tiered office structures (Plus/Pro) for validation against the Recruit CRM schema before import.

Greenhouse Offers (compensation package attached to an Application: start date, salary, equity, custom offer fields, and status) migrate to Recruit CRM Offer records. Offer status values (pending, accepted, declined, retracted) map to Recruit CRM's offer status field. Custom offer fields translate directly to Recruit CRM custom fields by type.

Greenhouse Scorecards store structured evaluator feedback (rating fields, follow-up questions, interviewer notes) tied to interview plans and pipeline stages. Recruit CRM does not expose a native structured scorecard object. We serialize scorecard content — interview type, scorecard questions, selected ratings, and evaluator notes — into a formatted text block stored in a custom field on the Candidate record, or as a chronological note entry in the activity timeline. The customer receives a written map of every Greenhouse scorecard template for admin-level rebuild as a Recruit CRM form or custom field set if structured evaluation tracking is required.

Greenhouse Users (Site Admin, Recruiter, Hiring Manager) map by email match to Recruit CRM Users. We extract all distinct owner references from Candidate, Application, Job, and Offer records and reconcile against Recruit CRM's User table. Any Greenhouse user without a matching Recruit CRM account enters a provisioning queue; migration of records owned by unresolved users pauses until the customer provisions the corresponding Recruit CRM User.

Greenhouse custom fields across all supported value types — short_text, long_text, yes_no, single_select, multi_select, currency, number, date, url, user_reference — map directly to Recruit CRM custom fields of the equivalent type. We validate field type compatibility during scoping and flag any Greenhouse field type that requires transformation (e.g., user_reference values resolve to the corresponding Recruit CRM User ID before import). Multi-select values migrate as comma-separated strings or as Recruit CRM's multi-select format depending on destination field configuration.

Greenhouse flat offices and departments (Core tier) map to Recruit CRM's organizational structure directly. Tiered office and department hierarchies available on Greenhouse Plus and Pro are validated against Recruit CRM's hierarchy model; if the customer's Plus/Pro tier hierarchy is deep or complex, we flag it for admin-level reconstruction in Recruit CRM rather than automated mapping, because Recruit CRM's org hierarchy has different modeling conventions.

Greenhouse tags on Candidate and Application records migrate as label arrays in Recruit CRM. Greenhouse allows unlimited tags; Recruit CRM's tagging model supports equivalent labeling. We preserve tag names exactly and map them to the destination's tagging fields on the Contact record.

Plus and Pro tier CRM events (calls, emails, notes) from Greenhouse migrate to Recruit CRM activity log entries. Core tier customers are limited to a single CRM event type in Greenhouse; we document this constraint during scoping and collapse available events into the single Recruit CRM activity type. Activity timestamp ordering is preserved. For Greenhouse Core customers, we advise upgrading to Plus before migration if comprehensive activity history migration is a requirement.

Resume, cover letter, and portfolio files attached to Greenhouse Candidates or Applications migrate as binary blobs linked to the corresponding Recruit CRM Contact record. We handle file type detection during extraction and map file links to the Recruit CRM attachment model. Attachment filenames and file size metadata are preserved for reconciliation validation.