Migrate your Personio data

The core HR object in Personio. Standard fields include name, contact details, employment dates, department, position, manager, and status. We export all employee fields via the GET Employees API endpoint, handling rate limits of 300 req/min by implementing backoff and pagination.

Tracks vacation, sick leave, and other absence types per employee. Absence categories and entitlement balances are exportable. We map absence types between source and destination schemas, flagging any custom absence types that require manual configuration at the destination.

Employee documents (contracts, certificates, ID scans) are stored in Personio and retrievable via the API. Document naming conventions and folder structures vary by company, so we map them to a flat target schema and flag any GDPR-classified documents that require special handling.

Job postings with associated metadata (department, location, status, hiring manager). Custom attributes on application forms are not accessible via a documented API endpoint according to community reports — we flag custom_attributes as a manual capture item and ask customers to confirm field mappings.

Candidate applications linked to recruiting positions. The API exposes standard application fields but custom_attributes on the application form require separate enumeration. We merge standard fields automatically and escalate custom field mapping to the scoping call.

Salary, bonus, and compensation data per employee. Personio stores effective-dated compensation entries. We preserve the effective_date on each record and map compensation components to destination field names, flagging any currency or proration anomalies.

Review cycles with configurable forms, ratings, and status tracking. Review templates and custom form questions vary by company. We export review status and scores but note that form question text does not automatically transfer to a new system — we flag this as a content-migration item.

Company-level goals and individual employee objectives are stored in Personio. We export goal titles, descriptions, progress percentages, and linkages to employees. Goal alignment hierarchies (company → department → individual) are preserved as structured data where the target system supports it.

Clock-in/out records and working-hours data per employee. Attendance entries export via the API. We map working-hours types and overtime rules between systems, flagging any rule-based calculations that do not transfer as raw data.

Custom fields added by the customer on any object. Personio supports custom attributes on Employees, Positions, and Applications. We detect all custom attributes via the API schema introspection and include them in the migration map as explicit field-level mappings.

Organisational hierarchy of departments and sub-departments. Exported as a flat or nested list depending on destination support. Standard in Personio and mapped directly.

Effective-dated salary change records per employee. Each change is a distinct entry with a date and amount. We export the full history and insert all dated entries at the destination, preserving the audit trail of raises and adjustments.

Employee benefit enrolments (health insurance, pension, etc.) stored against the employee record. We map benefit types and coverage levels, flagging any benefit plans that require carrier-specific configuration at the destination.

Personio automates approval chains for absence requests, onboarding steps, and document signing. These workflow definitions are not fully exposed via the API in a migration-ready format. We do not transfer workflow configurations automatically — we document the workflows as part of the requirements spec and recommend manual reconfiguration at the destination.