Migrate from Grove HR to Crelate

Grove HR Candidate records map to Crelate Contact. Grove stores full name, email, phone, address, source attribution, and CV attachment per candidate. We extract all contact fields and migrate them to Crelate Contact, with the CV file attached via Crelate's document attachment model. The Grove candidate_id is preserved in a custom field grove_candidate_id__c for audit and cross-reference.

Grove HR Application records (a candidate's submission to a job) map to Crelate Opportunity. Each Application carries a status, submission date, and link to the parent Candidate and Job. We map Application to Opportunity with the Opportunity type set to 'Application' or a custom record type for the recruiting pipeline, and we preserve the Application ID in a custom field grove_application_id__c. The Opportunity links to the Contact record resolved from the parent Candidate.

Grove HR Job records (the open position being recruited for) map to Crelate Opportunity with Opportunity type = 'Job' and a dedicated record type for recruiting openings. The Job's title, department, location, and job description migrate as Opportunity fields. If the Job is associated with a Company in Grove HR, that maps to a Crelate Company record. Crelate's job portal publication and job board posting settings are noted for rebuild by the customer's admin post-migration.

Grove HR pipeline stages are defined per-organisation and vary between customers. Common stages include Applied, Screening, Interview, Offer, Hired, Rejected. We extract the full stage matrix during scoping and map each Grove stage to an equivalent Crelate Opportunity stage name. Stage probability percentages migrate from Grove to Crelate. If the customer uses multiple pipelines in Grove, each maps to a Crelate Opportunity record type.

Grove HR stores notes and comments against Candidate and Application records with author, timestamp, and text content. Notes migrate to Crelate Contact Notes linked via ContentDocumentLink to the Contact. Rich-text formatting in Grove notes is preserved where possible; HTML-stripped plain text is used as a fallback. Notes attached to Applications migrate to the corresponding Opportunity linked to the Contact.

Grove HR stores CV and resume files as binary attachments on Candidate records. We export these as files and attach them to the corresponding Crelate Contact record via Crelate's document attachment model. Customers should confirm Crelate's storage limits and attachment policy before committing to a full document migration. We do not parse CV content or extract structured data from resumes during migration.

Grove HR stores company-level data including departments and locations. In the recruiting context, companies referenced by Job openings map to Crelate Company records. Company name, website, industry, and location fields migrate directly. Custom company properties defined in Grove HR migrate as Crelate Company custom fields.

Grove HR supports custom fields on Candidate, Application, and Job objects. We detect all custom field definitions during scoping, extract their values alongside standard fields, and pre-create matching custom fields in Crelate on the equivalent object (Contact, Opportunity, Company) before migration. Crelate's custom field logical names must be specified during creation; we coordinate this with the customer during the development phase.

Grove HR Employee records (the HRIS core object storing name, role, start date, employment status, documents, and training history) have no equivalent in Crelate's ATS data model. Crelate does not manage employment records, onboarding checklists, leave balances, performance reviews, or training modules. We extract a named list of employee records requiring manual entry in Crelate's Contact records if the customer intends to use Crelate for internal hiring where candidate and employee records overlap. This is a partial data decision made during scoping.

Grove HR leave management (entitlements, balances, approval workflows) does not map to any Crelate object. Crelate has no time-off, absence, or leave management module. We flag this gap explicitly and recommend the customer evaluates a dedicated leave management tool if leave tracking is required post-migration. Leave data extracted from Grove HR is delivered as a supplementary CSV for the customer's HR admin to reference.

Grove HR onboarding and offboarding checklists are template-driven task structures assigned to employees. Crelate has no onboarding workflow or checklist module. We export assigned checklist items and their completion states as a standalone task list CSV. The customer's admin rebuilds onboarding processes in their chosen onboarding tool or in Crelate's Activity and Task features post-migration.

Grove HR performance reviews and goal records have no equivalent in Crelate's ATS. Crelate does not manage performance cycles, reviewer assignments, rating scales, or goal tracking. These records are out of scope for migration and are flagged in the handoff document. The customer should select a dedicated performance management tool if this data needs to be preserved.