Migrate from Happy Hire to Crelate

Happy Hire candidate profiles include contact details, resume files, status, and source attribution. We migrate candidate records 1:1 to Crelate Person records. Resume files are extracted as attachments and linked via Crelate's document storage. Source attribution maps to the Crelate Source field. Any empty required fields in Happy Hire are flagged during extraction so the customer can decide whether to backfill before import.

Happy Hire Applications link a Candidate to a Job with stage and timestamp data. We preserve the full application history including stage transitions and notes across both inbound and outbound migrations. Application status maps to Crelate's submission stage values. The application timestamp is preserved as a custom date field on the Job Submission record.

Happy Hire Job records carry title, description, location, department, and status. We migrate active and closed jobs with their posting metadata. Custom job fields from Happy Hire are mapped to Crelate custom fields on the Job object. Active postings that are currently receiving applications are kept open until the cutover window closes to prevent mid-flight candidate loss.

Happy Hire user accounts include name, email, and role. We migrate users with their assigned roles and reassign ownership of candidates and jobs to the correct user records at Crelate destination. Owner reconciliation is performed by email match. Any Happy Hire user without a matching Crelate user account goes to a provisioning queue for the customer's admin.

Post-hire Employee records stored separately from candidate profiles in Happy Hire are migrated to Crelate Person records with an Employee record type. Fields including start date, department, and employment status map to corresponding Crelate Person fields. Custom employee properties may require additional field mapping work depending on the complexity of the source schema.

Happy Hire onboarding workflows include checklists and task assignments tied to new hires. We export task names, assignees, and completion statuses. Subtask nesting may flatten during migration depending on the depth of the source hierarchy. We flag any flattened subtasks in the migration report so the customer can assess whether manual reconstruction is needed in Crelate.

Scorecard templates and completed evaluations contain structured ratings and free-text notes. We export the scorecard structure and all completed evaluations, preserving the relationship to the candidate. Crelate's activity forms and custom fields are used to replicate the scorecard layout. The customer reviews the mapped scorecard structure during sandbox validation before production migration.

Active postings to external job boards are tracked as metadata on the Happy Hire Job object. We record which boards a job was posted to and the posting URL where available. Board-level analytics (views, clicks, applications per board) do not migrate as these are external platform data not stored in Happy Hire. The job posting URLs are preserved as notes on the Job record in Crelate.

Happy Hire tracks candidate source (referral, job board, direct apply, agency) as a property on the Candidate object. We map source attribution to the Crelate Source picklist field on the Person record. If Happy Hire uses free-text source values not in Crelate's standard picklist, we either add them to the picklist or store them in a custom text field for the customer to normalize post-migration.

Happy Hire custom fields on the Candidate object are mapped to Crelate custom Person fields. We match field types (text, number, date, picklist, checkbox) between the two systems and flag any Crelate field type that requires conversion. Custom fields are provisioned in Crelate before migration begins so they are available during the import phase.

Happy Hire pipeline stage names (Applied, Screening, Interview, Offer, Hired) are mapped to Crelate submission stage values. Stage ordering is preserved. If the customer has custom stage names in Happy Hire, we create matching custom stage values in Crelate during the pre-migration configuration phase.

Candidate-related notes and tasks from Happy Hire migrate to Crelate Activity records linked to the Person. Notes become Crelate note-type activities; tasks become Crelate task-type activities with assignee, due date, and status preserved. Activity timestamps are preserved to maintain the historical timeline on the candidate record.