Guides
Migrating from Personio to KI BMS - productive in 90 minutes
Concrete steps: what to export, where it lands in the new tool, what you can let go. With two real migration examples.
Key takeaways
Set the cutover date
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.
Export the talent pool from Personio
Personio Settings > Recruiting > Talent Pool > CSV export. Save as pool.csv with default columns (name, email, role, status, date).
Import candidates into KI BMS
Candidates > Import CSV. The column-mapping UI shows where Personio's fields belong. 5 minutes for 1,000 candidates.
Create the jobs
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.
Create email templates
Three are enough to start: receipt, first-call invite, rejection. Auto-send on stage change optional.
Deactivate Personio recruiting
Set the careers page to 'inactive' or change the application URL to KI BMS. Active applications stay visible in Personio until completion.
Document the reporting cutover
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.
Why teams migrate
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.
What you *don't* migrate
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.
Two real migrations, with numbers
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.
FAQ
Frequently asked
Try KI BMS
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
From Excel sheet to KI BMS - productive in 30 minutes
Six steps, a CSV mapping example, a 'don't do this' block.
Read