Migrate from Personio to Crelate

Personio Recruiting Positions map to Crelate Job records. The Personio position title, department, location, status, and hiring manager transfer to Crelate's job_name, department, location, status, and AssignedTo fields. We extract position metadata via the Personio API and POST to Crelate's Jobs endpoint (POST /api3/jobs). Job status mapping follows the customer's agreed mapping table: Personio's Active/Draft/Closed maps to Crelate's Open/Paused/Closed. Note that Crelate Jobs are distinct from Crelate Job Orders in its legacy model; we target the current Jobs API.

Personio Applications linked to Recruiting Positions map to Crelate Candidate records. Standard fields including name, email, phone, application date, status, and source migrate. Candidate records in Crelate are linked to the destination Job via the submission history. We use the Crelate Candidate endpoint (POST /api3/candidates) with email as the dedupe key. Custom application form attributes are a known gap — see the gotchas section.

Personio application stages (Applied, Screening, Interview, Offer, Hired, Rejected) map to Crelate's candidate status workflow on the Job. We build a status mapping table during scoping that aligns Personio's stage names to Crelate's configurable pipeline stages per Job. Status transitions and rejection reasons transfer to Crelate's activity log.

Personio Employees map to Crelate Contact records if the migration scope includes internal employee data or if former employees are being imported as candidate prospects. Employee name, email, department, job title, manager, and employment dates transfer. We extract via GET Employees (rate-limited at 300 req/min) and POST to Crelate's Contacts endpoint. If the customer is only migrating recruiting data, the Employee-to-Contact mapping is optional and scoped during discovery.

Personio Departments transfer as Crelate tags on Job and Candidate records, or as a custom Department picklist field on Contact if the customer requires org-structure reporting in Crelate. We preserve the department hierarchy as a flat tag list during migration, with the customer's admin confirming the preferred tagging strategy during scoping.

Personio employee documents (contracts, certificates, ID scans) stored against the Employee record can be attached to the corresponding Crelate Contact record as document links. Document naming conventions vary by company in Personio, so we map file names to a consistent Crelate document type structure (Contract, Certificate, ID, Other). Documents are downloaded from Personio via the document retrieval API and uploaded to Crelate's document storage linked to the Contact record.

Personio Absence records (vacation, sick leave, time-off balances) do not map to Crelate's ATS/CRM data model. Crelate does not have an absence or time-off management module. If the customer needs to retain absence history for compliance or reporting, we export absence records as a CSV inventory delivered alongside the migration. The customer's HR team retains absence data in Personio's read-only state or exports to a separate HR system.

Personio Payroll records (salary, bonus, compensation entries, effective-dated changes) do not migrate to Crelate. Crelate is a recruiting ATS/CRM and does not have a payroll module. We export payroll data as a typed CSV with effective_date preserved and deliver it to the customer's finance or HR team for import into their payroll system of record.

Personio Performance Reviews and Goals (OKRs) do not migrate to Crelate. Crelate does not support a performance management data model. We export review status, ratings, and goal progress as a CSV inventory for the customer's HR team. The customer's admin rebuilds performance review templates in their chosen performance management tool (Personio, Lattice, BambooHR, or another HRIS) post-migration.

Personio custom employee attributes (attributes not in the standard Personio employee schema) map to Crelate custom fields on Contact. We discover all custom attributes via Personio's API schema introspection and create matching Crelate custom fields under Settings > Core Records > Contacts before migration. Field types are mapped: text attributes to Crelate Text fields, date attributes to Crelate Date fields, numeric attributes to Crelate Number (Decimal) fields.

Personio custom_attributes on job application forms are a known API gap — the Personio API does not expose these fields. We ask the customer during scoping to provide the full list of custom application form fields and a data export (screen scrape, manual export, or the customer's own record). We map these to Crelate custom fields on the Candidate record or as Activity Form questions with field mappings to the Contact. The customer must enumerate the field names and data manually; we cannot extract them via API.

Personio recruiting pipeline analytics and reports are not migrated because the data is known to contain discrepancies. Crelate's native reporting (Advanced Reports and Analytics on the Business plan) replaces these from the date of go-live. We advise the customer to treat Personio's recruiting analytics as historical reference rather than authoritative data and to verify figures against actual application records before migration scoping begins.