Migrate your PeopleStrong data

The core employee record in PeopleStrong contains standard fields: personal details, employment status, department, job title, manager assignment, and hire/termination dates. The schema is stable and well-documented across API and export interfaces. We migrate Employee records 1:1, preserving the reporting chain via ManagerID mapping.

Payroll records include salary components, deductions, pay periods, and payslip metadata. PeopleStrong stores payroll by payrun cycles; we map each payslip to the corresponding employee record. Historical payroll can span multiple years and requires date-range scoping to avoid pulling data outside the customer's retention window.

Attendance data includes clock-in/out timestamps, regularization requests, and shift assignments. The attendance object ties to a specific pay period and employee. We preserve regularization status and approval workflows as custom fields on the destination system since not all platforms model regularization explicitly.

Leave management includes accrued balances, request records, and approval status. PeopleStrong tracks leave by leave type (earned, casual, sick) per employee per policy year. We map leave types to destination leave categories and preserve accrued-but-unused balances as of the migration cut-off date.

Performance Management module contains review cycles, ratings, and goals. PeopleStrong supports configurable review templates, so the schema varies by organization. We map standard fields (reviewer, reviewee, rating, date) and flag custom rating scales for manual review during migration.

The recruitment module stores candidates, job applications, interview scores, and offer letters. Candidate records include resume data, stage history, and recruiter assignments. We extract the full candidate pipeline and map stage names to destination workflow stages.

Expense claims with line-item details, approval status, and settlement records are stored in PeopleStrong. We migrate claim headers and line items, preserving submission date and payment status. Settlement data may require additional mapping if the destination system does not model partial reimbursement states.

Organizational structure entities — departments, cost centers, and locations — are referenced by employee records. These migrate as reference tables before employee records. We preserve the full hierarchy including parent-child department relationships.

Job titles, grade structures, and band definitions are standard lookups used by employee and payroll records. These migrate cleanly as value maps before the employee object.

PeopleStrong supports organization-level custom fields on employee records. Custom field schema varies by tenant and is not consistently exposed via the public API. We perform a schema discovery step during scoping and map custom fields to destination equivalents or store them as JSON blobs for manual categorization post-migration.

Employee documents such as offer letters, contracts, and ID proofs are stored as attachments linked to employee records. Document migration requires file retrieval via separate API calls after the primary record export. We preserve file names and MIME types and note that large binary blobs can extend migration timelines.

PeopleStrong distinguishes between employee records and system user accounts with login credentials and role assignments. Not all employee records correspond to active system users. We separate these two concepts during migration scoping and map role names to destination permission groups.

Salary revisions, effective-dated compensation changes, and bonus payouts are stored as separate objects linked to the employee. PeopleStrong records compensation with start and end dates enabling historical reconstruction. We map effective-dated rows chronologically to preserve pay progression.