Guides
Concrete steps: what to export, where it lands in the new tool, what you can let go. With two real migration examples.

Key takeaways
Pick a day on which all new applications go to the new tool. Ideal: month-start so reporting is clean. No hybrid phase - the biggest trap.
Personio Settings > Recruiting > Talent Pool > CSV export. Save as pool.csv with default columns (name, email, role, status, date).
Candidates > Import CSV. The column-mapping UI shows where Personio's fields belong. 5 minutes for 1,000 candidates.
Copy job descriptions by hand from Personio. For 6-15 open roles that's 15 minutes. We recommend using Markdown, switching on KI screening, and setting a short KI prompt while you're there.
Three are enough to start: receipt, first-call invite, rejection. Auto-send on stage change optional.
Set the careers page to 'inactive' or change the application URL to KI BMS. Active applications stay visible in Personio until completion.
At the next quarterly review it's clear: Q1 = Personio, Q2 = KI BMS. Comparing the first two quarters gives you an honest before/after view.
Three reasons, recurring. One - Personio recruiting feels generalist; the team wants specialist ATS depth (KI pre-sort, real kanban, multi-voice scorecards). Two - per-seat recruiting load isn't economical: 50 seats but only 3 people recruit. Three - procurement forces module reduction or grasps at sourcing tools, which prompts a review. A detailed feature comparison of both tools is at KI BMS vs Personio.
Active applications with running interviews. Let those finish in Personio - mid-process migration costs more than the win. Set a cutover date: 'from June 1st all new applications land in KI BMS, everything before stays in Personio'. Clean line, no data mix.
Also not migrated: employee files of hires, payroll data, absence management. Personio keeps doing those, well. Once KI BMS is live, our guide publishing your first job in 8 minutes walks you through setting up the first listing.
Example A - Berlin B2B SaaS, 38 staff, 6 open roles. Migration April 2026, 2.5 hours for the HR lead. Personio recruiting module deactivated April 30, KI BMS live May 1. Result: 3 hours per role per week back, KI screening on all 6 roles.
Example B - Hamburg manufacturer, 220 staff, 14 open roles, 8 recruiting seats. Migration across two weekends, ~12 hours for 2 people. 2,400 candidates migrated. Result: ~50% recruiting-module cost saved, KI screening adopted, Personio stays for 4 other modules.
You export applicant data not via the big company export but via the separate recruiting report 'Export application data'. The window used to be capped at 3 months and is now raised to a maximum of 12 months - so you export up to a year of applications per run as Excel/CSV. The columns (name, email, role, status, date) get mapped in a column-mapping UI on import into KI BMS.
Two traps nobody mentions up front: first, applicant documents (CVs, cover letters, references) can only be downloaded individually, not as a bulk ZIP - for large pipelines, back up the attachments of the genuinely relevant candidates, not every dead lead. Second, the big company export (all employee data + documents) runs only as Account or Contract Owner, at most every 6 days, generation can take over a day, and the download link is valid for only about a week. Plan for it instead of discovering it on cutover day.
The tool switch takes 90 minutes; the contract is the longer job. Personio typically runs on a 12-month minimum term, auto-renews for another 12 months, and has a 3-month notice period to the end of the term. Miss the deadline and you're locked in for another year - the most expensive migration trap there is.
So order matters: first find your own cancellation date in the Personio contract, then plan backwards. You can take KI BMS live immediately and let Personio run out in parallel until contract end - deactivate the recruiting module at once, keep payroll and files until the regular cancellation. Cancel in writing (Personio recommends registered mail) so the date is provable. The pricing model, by the way, is per active employee per month, with the recruiting module often a paid add-on - exactly the line item you save after the switch.
FAQ
Free plan, no credit card. We host in Germany. You can export and delete everything self-serve.
Read next
KI BMS vs Personio: the right recruiting tool for modern HR teams
Suite vs specialist: when an integrated HR tool wins - and when a dedicated ATS sets you free.
Read
Publishing your first job with KI BMS - online in 8 minutes
Step-by-step from empty account to public role with application form and KI pre-sorting. No magic, no setup day.
Read
Applicant tracking software: what it actually does and when it pays off
Definition, feature scope, selection criteria, and the point at which the effort pays off.
Read