Migrate from Personio to Recruit CRM & ATS

Personio recruiting Positions (job postings with department, location, status, and hiring manager metadata) map directly to Recruit CRM Job records. The Personio position status (open, paused, closed) maps to Recruit CRM's job status field. We extract the full position metadata including custom fields via the GET Positions endpoint and map each field to the equivalent Recruit CRM job field. Position hierarchy or nested job families in Personio become flat tags or custom fields in Recruit CRM.

Personio Applications (candidates linked to Positions) map to Recruit CRM Candidate records. The application status (new, screening, interview, offer, hired, rejected) maps to Recruit CRM pipeline stage values. We preserve the full application timeline as stage-change entries in Recruit CRM's candidate history. Source attribution (where the candidate came from) migrates to the candidate's source field.

Personio's custom_attributes on job application forms are NOT accessible via any documented API endpoint — this is a confirmed platform limitation. We explicitly request the customer to provide a list of all custom application form fields and sample data during scoping. We then create matching custom fields in Recruit CRM and map the data manually. Without this step, custom candidate data is silently missed.

When a Personio Application reaches hired status, the candidate is linked to an Employee record in Personio. We extract the hired candidate's employee profile fields (name, contact details, start date, department, manager) and merge them into the Recruit CRM Candidate record as a complete candidate profile. The hire date from Personio maps to Recruit CRM's placement date.

Personio employee documents (CVs, cover letters, certificates, ID scans) stored against the Application or Employee record migrate as files attached to the Recruit CRM Candidate. We map document types (CV, cover letter, reference, certification) to Recruit CRM's file category taxonomy. File naming is normalised to a flat structure during migration since Personio folder hierarchies vary by company configuration.

Personio Departments extracted from the employee and position hierarchy are mapped as tag values on Recruit CRM Job and Candidate records. Since Recruit CRM does not have a standalone departments object (it uses tagging for organisational context), we merge all Personio departments into Recruit CRM's tag vocabulary and apply them to the relevant job and candidate records during migration.

Personio Absence records (vacation, sick leave, entitlement balances per employee) have no equivalent in Recruit CRM. Recruit CRM is a recruiting ATS and does not track employee absences. We flag absence data as out-of-scope during scoping and recommend the customer maintains absence records in Personio or migrates them separately to a dedicated absence management tool if they are leaving Personio entirely.

Personio compensation entries (salary, bonus, effective-dated pay changes) and benefits enrolments have no mapping in Recruit CRM. Recruit CRM has no payroll, compensation, or benefits module. If the customer is leaving Personio entirely, we recommend migrating payroll records to a dedicated payroll platform (such as Payroll by Personio spin-off, Figure, or a local payroll provider) as a separate project.

Personio Performance Review cycles, ratings, and review form responses do not map to Recruit CRM's candidate-centric schema. Recruit CRM does not have a performance management module. We flag performance review history as out-of-scope. The customer may choose to export review summaries manually or migrate them to a dedicated performance management platform as a separate project.

Personio company-level goals and individual employee objectives have no equivalent in Recruit CRM. Goals, progress percentages, and alignment hierarchies are out-of-scope for this migration. Recruit CRM is designed for candidate and client relationship management, not for OKR tracking against employee performance.

Personio approval chains for absence requests, onboarding steps, and document signing are not exposed via the API in a migration-ready format. We do not migrate workflow definitions as code. We deliver a written inventory of every active Personio workflow with its trigger, conditions, actions, and approval chain, plus a recommended Recruit CRM automation builder equivalent for the customer's admin to rebuild.

Personio clock-in/out records, working-hours data, and overtime rules have no equivalent in Recruit CRM. Time tracking data is out-of-scope. The customer should retain time tracking records in Personio or migrate them separately to a dedicated time-tracking platform if leaving Personio entirely.