Migrate from greytHR to Crelate

greytHR Employee records contain demographic data (name, date of birth, gender, mobile, email, address) and employment data (department, designation, grade, joining date, employment status) that maps to Crelate Person records. We extract contact fields, emergency contact details, education and skill fields from greytHR, and load them as Crelate Person records. Active employees in greytHR map to Crelate Persons with a status tag (current-employee or re-hire-candidate). Former employees map to Persons tagged as alumni for re-hire pipelines. The greytHR statutory fields (UAN, PF, ESI, PAN, Aadhaar) do not migrate because Crelate has no equivalent statutory compliance module; we document these as a separate statutory handoff package.

greytHR department, designation, and grade fields store the employee's current organizational position. We extract these values and map them to Crelate custom Person fields (department__c, designation__c, grade__c) or as tags on the Person record. The customer chooses field versus tag strategy during scoping based on how they plan to filter and report on candidate origin in Crelate.

greytHR stores skills, certifications, educational qualifications, and prior experience on the Employee record. We extract these as comma-separated or multi-value fields and load them into Crelate Person skills fields and tags. Skill normalization may be required if greytHR uses free-text skill entries rather than a controlled vocabulary; we flag inconsistent skill formats during scoping.

greytHR emergency contact fields (name, relationship, mobile number) store as structured fields on the Employee record. We extract these and load them into Crelate custom Person fields (emergency_contact_name__c, emergency_contact_phone__c, emergency_contact_relationship__c). These fields are relevant if the customer plans to use Crelate for contractor or re-hire onboarding handoff.

greytHR payroll runs (gross pay, deductions, net pay, pay period, pay date) do not migrate to Crelate. Crelate has no payroll module and no field equivalent for compensation data. We export a payroll summary CSV from greytHR as a manual reference document for the customer's finance team. Statutory deductions (PF, ESI, TDS) are flagged as high-priority manual handoff items because government filings may reference mid-year payroll records.

greytHR leave balances, accrual history, carry-forward rules, and encashment records do not migrate to Crelate. Crelate has no leave management module. We export the current leave balance snapshot per employee as a CSV reference. Leave carry-forward rules defined in greytHR leave policies must be manually reconfigured if the destination platform includes leave management; we document the current policy settings during scoping.

greytHR swipe logs, shift schedules, overtime data, and regularization status do not migrate to Crelate. Crelate has no attendance tracking module. We flag that greytHR community posts document occasional swipe visibility issues in the admin view where raw swipe data exists but regularization status has not been updated; we export both raw swipe logs and regularization status and flag contradictions for the customer's attention before migration.

greytHR statutory fields (UAN, PF number, ESI number, PAN, Aadhaar, TDS section) do not migrate to Crelate. These fields are mandated for Indian government filings (EPFO, ESIC, TDS returns) and have no equivalent in Crelate's recruiting data model. We flag every statutory field as a mandatory cutover checklist item: the customer must download official PF/ESI challan history and TDS filing records from greytHR before cutover, as these records are required for mid-year government filing continuity. This is a high-severity handoff item.

greytHR expense claims, reimbursement amounts, and approval status do not migrate to Crelate. Crelate has no expense management module. If the customer uses Crelate for contractor placements and needs expense reimbursement tracking, they must configure a separate expense management workflow in Crelate or retain another tool. We export claim records as a CSV for the customer's finance team.

greytHR stores department, designation, grade, and location changes with effective dates as a position history timeline. We extract the current position snapshot and map it to Crelate Person fields. If the customer wants historical position changes preserved, we load them as a custom text field or as work history entries on the Person record; Crelate's primary model does not support full position history timelines, so we compress to current position plus most recent prior role.

greytHR performance review cycles, ratings, goals, and feedback text do not migrate to Crelate. Crelate is a recruiting ATS and does not include performance management or review cycle tracking. We export completed review records as a CSV reference for the customer's HR team. In-progress review cycles at migration time are flagged as a cutover risk: the customer's greytHR admin must finalize or document any open review cycles before we freeze writes on the source system.

greytHR stores employee documents (offer letters, ID proofs, contracts, joining letters, previous employer documents) in its document module. We export document metadata (filename, type, upload date, employee linkage) and binary files where API access is granted. These files attach to the corresponding Crelate Person record as ContentDocumentLink attachments. The customer must verify that document access permissions in greytHR allow bulk export before migration. Some document types (PF forms, ESI cards, TDS certificates) should be retained separately as statutory handoff items.