Migrate your greytHR data

The primary object in greytHR. Contains all demographic, employment, and statutory fields (UAN, PAN, Aadhaar, PF, ESI, nominee details). We export the full employee record including effective-dated position changes. Custom employee fields are supported via our field-mapping layer.

Leave entitlement, accrual, and usage history are stored per employee with a leave policy assignment. We preserve leave balances at migration-cutoff, carry-forward rules, and encashment records. Leave approval workflows are not migrated — these are rebuilt at the destination.

greytHR stores swipe logs, shift schedules, and overtime data. We export raw attendance records with timestamps and the regularization status of each entry. Note that some reviewers report swipe visibility failures in greytHR itself — we flag records with missing swipes during the audit phase.

Payslip data (gross, deductions, net pay) is exportable, but greytHR does not expose salary computation rules via API. We map payslip rows to destination salary structures, but the underlying formula logic must be re-created at the destination. Arrears, adjustments, and one-time payments require manual review.

Employee documents (offer letters, ID proofs, contracts, joining letters) are stored in greytHR's document module. We export document metadata and binary files where API access is granted. Some document types may require re-upload via destination's native upload tool.

UAN, PF numbers, ESI numbers, PAN, and TDS sections are stored as structured fields on the Employee record. We preserve these exactly as-is. For exit migrations, we recommend downloading official PF/ESI challans from greytHR separately before cutover to avoid any filing gap.

Expense claims, approval status, and reimbursement amounts are stored per employee. We export claim records with status (approved, rejected, pending). Custom expense categories require field-level mapping to destination expense types.

Department, designation, grade, and location changes are tracked with effective dates. We export the position history timeline. Where destination systems store only the current position, we map the most recent record and flag historical changes.

greytHR Users are system actors (HR admins, managers, employees) with role-based access. Employee-to-user linkage is preserved. Role definitions (permissions, approval authority) do not export cleanly — we map them to equivalent roles or ACLs at the destination where possible.

greytHR maintains a tamper-evident audit trail covering payroll, leave, and employee data changes. We export audit log records for compliance record-keeping at the destination. Volume is typically manageable for standard migrations.

greytHR PMS stores review cycles, ratings, goals, and feedback text. We export completed review records and ratings. In-progress review cycles are migrated as-is with a status flag; finalization must complete in the destination system.

greytHR allows custom fields on employee records and uses a List of Values (LOV) system for picklist fields. We export both the custom field values and the LOV definitions, then map them to destination picklists. Mismatched LOV values trigger a review step before finalization.