Migrate from Homerun to Recruit CRM & ATS

Homerun Candidates map directly to Recruit CRM Candidates. We preserve the full application timeline, current pipeline stage, source channel, and any rating or scorecard results. The candidate's email address serves as the dedupe key during import to prevent duplicate records. Custom properties on the Candidate object migrate as typed fields with explicit value mapping for picklist, date, and numeric types.

Homerun Job Openings map to Recruit CRM Jobs. Each job's title, description, department, location, and employment type migrate as structured fields. Pipeline stage configuration from Homerun maps to Recruit CRM's pipeline stage names and ordering, with a configuration step that aligns the stage probabilities with the customer's desired sales process. Active versus archived status is preserved; archived jobs are imported as closed with their closure date.

Homerun pipeline stages (name, order, probability) map to Recruit CRM pipeline stages on the corresponding Job record. We configure Recruit CRM pipeline stages during the schema design phase so that the stage labels match the customer's hiring language. Stage-count mismatches are flagged: if Homerun has more stages than the Recruit CRM pipeline allows, we map the closest equivalent and document the gap for the admin.

Homerun Employee records require a split decision: employees who are also active candidates in the pipeline migrate to Recruit CRM as Candidate records with an employee flag, while pure employee records without candidate activity migrate as Contacts in the CRM module. This split is computed at migration time based on whether the employee has a corresponding active or historical application in Homerun. Start date, role, department, and employment status map to equivalent Contact fields in Recruit CRM.

Homerun Time Off balances and request records migrate as current-state records with effective dates and remaining balances. Historical accrual patterns are not replayed; instead, we import the current balance snapshot and the destination Recruit CRM accrual engine handles future accrual calculation. Approval status and request type (vacation, sick, personal) map to Recruit CRM's time-off request fields. Note: if Recruit CRM's plan tier does not include a time-off management module, we flag this as a gap during scoping and migrate time-off as notes attached to the Contact record.

Homerun scorecard ratings and evaluator comments migrate to Recruit CRM's evaluation structure. Score values are normalized to the destination's rating scale: if Homerun uses a 1-5 numeric scale and Recruit CRM uses a pass/fail or star rating, we preserve the original numeric score in a custom field and map the semantic equivalent (e.g., 4-5 maps to 'Strong Hire'). Evaluator name and submission date migrate as structured fields.

Homerun offer letters including compensation details, start date, conditional terms, and signing status migrate to Recruit CRM Offers. Salary and bonus figures migrate as numeric fields with currency preserved; conditional clauses are imported as text notes on the Offer record. If the candidate has already been hired in Recruit CRM before the offer migrates, we link the Offer record to the existing Candidate or Contact via the relationship API.

Homerun team members and user accounts migrate to Recruit CRM Users. Role assignments (Hiring Manager, Recruiter, Admin) map to Recruit CRM role equivalents. We resolve users by email match; any Homerun user without a matching Recruit CRM account is held in a reconciliation queue for the customer to provision before migration begins. Active and inactive status is preserved.

Employee and candidate documents stored in Homerun (contracts, resumes, identification) are exported as file metadata with content references. We import file URLs as Recruit CRM attachments linked to the corresponding Candidate, Contact, or Job record. Large files are handled through chunked retrieval against the Homerun document API. Note: if a document's source URL requires authentication that expires, we flag it during scoping and advise the customer to download critical files before migration begins.

Custom fields on any object (Candidate, Job, Employee, Offer) are enumerated during scoping and mapped to Recruit CRM custom fields of equivalent type. Picklist custom fields require explicit value mapping if the source and destination picklist values differ. Date, numeric, and boolean custom fields map directly. We create the destination custom field schema before importing any records so that all data lands in typed fields rather than generic text.