Migrate from Homerun to Crelate

Homerun Job Openings map to Crelate Job Order records. Each job's title, description, department, and pipeline stage configuration migrates. Homerun pipeline stages (name, ordering, associated actions) map to Crelate pipeline stages by sequence position; we flag any stage that exceeds Crelate's default stage limit per pipeline configuration. Department from Homerun maps to a custom picklist or tag field in Crelate.

Homerun Candidate records map to Crelate Contact records. Application history, pipeline stage assignments, and the full candidate timeline migrate. We preserve the original candidate ID from Homerun as a custom field hr_candidate_id__c for reconciliation. Any candidate record with multiple applications maps to separate activity entries on the single Contact record in Crelate.

Homerun Employee records (introduced with the 2025 HR module) map to Crelate Contact records tagged with an employment context flag. We map name, email, role, department, start date, and employment status. Custom HR properties on Employee records (benefits tier, location, manager) migrate as custom fields on the Contact record. If the Homerun account predates the 2025 HR module activation, we scope the migration based on active modules at migration time, not retrospectively.

Homerun Time Off balances and requests migrate as current-state records with effective dates. We export the balance amount, accrual method, and request history. Crelate does not have a native Time Off object; we create a custom record type or attach the data to the Employee Contact record via custom fields (balance_hours__c, accrual_start_date__c, time_off_requests__c as a linked list). Historical accrual patterns are mapped based on Crelate's custom field type requirements.

Homerun Offer letters including compensation details, start dates, and conditional terms extract into Crelate's Job Order record with custom fields (offer_salary__c, offer_start_date__c, offer_conditions__c, offer_status__c). We handle formatting differences in salary amounts (EUR in Homerun, USD in Crelate for US-based teams) by applying a customer-provided conversion rate or flagging for manual review.

Homerun Evaluation scorecards and their ratings migrate as Crelate Activity Forms with field mappings to Contact. Score values may not map 1:1 to Crelate's rating schema; we normalize scores to Crelate-compatible integer or picklist values and preserve evaluator comments in a custom notes field on the activity record.

Homerun Team members and user accounts map to Crelate User records by email match. We preserve role assignments and ownership relationships during migration so access controls map to equivalent roles in Crelate. Any Homerun Owner without a matching Crelate User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Employee and candidate documents stored in Homerun HR migrate as file attachments in Crelate. We export file metadata and content URLs, handling large files through chunked retrieval where needed. Documents attach to the parent Contact (for employee documents) or to the Job Order (for job-related documents) via Crelate's document attachment model.

Homerun pipeline stage names, ordering, and associated actions vary between accounts. We apply sequential stage mapping aligned with Crelate's pipeline configuration, flagging any stages that exceed the target pipeline's stage limit. Stage probability percentages migrate as custom fields if required by the customer's reporting model.

Custom fields on any Homerun object are accessible via API with field IDs and data types. We enumerate all custom properties during scoping, build explicit type mappings to Crelate's custom field types (Text, Number, Money, Date, Picklist), and pre-create the destination schema before import. Picklist values map to Crelate picklist options by exact match; unmapped values are flagged for admin review before migration begins.

Homerun email engagements migrate to Crelate Activity records linked to the Contact. Email content, timestamp, and sender/recipient details preserve. If the engagement references a specific Job Opening, we link the activity to the corresponding Job Order record via Crelate's activity-job association model.

Homerun call engagements migrate to Crelate Activity records with call disposition, duration, and recording URL preserved in custom fields on the activity. Activity timeline ordering is preserved by setting the activity date to the original Homerun timestamp.