Guides
Move from Personio to Bizisy
On this page
Move your people, their jobs, teams, managers and time off from Personio to Bizisy, with an export file or a read-only API key. You see everything Bizisy would do before anything is written.
You need to be an owner, admin or HR member. Open Manage → People → Import → Coming from another tool? and pick the tool. Connecting an API key needs an owner or admin: the key opens the whole HR system.
What moves, and what doesn't#
| Moves | How |
|---|---|
| People with their contact details, and private details (birthday, personal email and phone) | From the file, or the API. Private details stay private in Bizisy. |
| Job (title, team, department, manager, location, legal entity, start date, contract, weekly hours) — each legal entity of the old tool goes to one of yours (the same name, or your only one; you choose the rest) | From the file: today's job. Through the API: the job history too, as dated job changes. |
| Teams, departments and locations | Matched by name; the missing ones are created (new locations get your company's country unless you choose another). |
| Managers | By email, by name or by the Personio ID, whichever the file has. |
| Time off | Past and future leave, from a second file (the Absences report) or the API; balances ("available" on the day of the move) from a second file only: Personio's API has no balances. Leave is recorded as booked by HR: no approvals, no emails. |
| Pay | Only if you choose it in the mapping step, only in the app, and only for people the move adds or who have no pay in Bizisy yet. |
| Documents | Through the API connection only: the files Personio provides, up to your storage limits. The check shows how much space they take and what it costs beyond what your plan includes. Files Bizisy can't take are listed with their title and person, to fetch by hand. |
| Custom fields | A column goes to one of your fields, or to New field (a private text field named after the column, created on import: only the person and HR see it until you change that in Settings → Custom fields). |
Not moved: people who already left (a termination date in the past, or an inactive status). They are counted and listed, never written: Bizisy starts with your current team. People starting later arrive as pre-hires, with no checklist and no invite. Nobody is emailed by a move, except the usual security notice when the payroll details of someone already in Bizisy change.
Export from Personio#
- In Personio, open Organization → People list (how the people list works).
- Choose the columns to move (the export has the columns of the list): name, email, position, supervisor, department, team, office, hire date, employment type, weekly working hours, and any you want to keep.
- Click the export icon and download Excel or CSV. English and German labels are both recognised (attributes).
- For time off, export the Absences report too (employee, absence type, start date, end date, days, half day, status) and add it as the second file.
Or connect with an API key#
- In Personio, open Marketplace → Connected integrations → Create custom integration (getting started with the Personio API).
- Allow it to read the attributes you want moved (and absences, documents and compensation if you move them).
- Copy the client ID and client secret into Bizisy. Bizisy reads people, employments (the job history), teams, legal entities, absences, documents and this month's compensation (one pay row: Personio's API gives pay a month at a time); it never writes to Personio.
What the wizard does#
- Choose the tool. Bizisy knows each tool's column names, in the languages it exports in (for a spreadsheet: common names in seven languages).
- Upload or connect. Upload the people file (CSV or .xlsx, up to 20 MB and 10,000 rows) and, if you have it, the absences file. Or paste the API credentials.
- Mapping. Every column gets a field with a confidence: exact (the tool's own name), likely (a common name) or not mapped (shown with sample values and a picker). Choose what each column feeds, or Don't import. Columns left out are listed in the report.
- Dry run. Bizisy checks every row and writes nothing: "142 people (138 new, 4 updated), 12 teams, 3 locations, 1,204 days of leave, 3 problems". Each problem names its row, its column and how to fix it.
- Fix or skip. Correct a value in place or skip the row, map each leave type to one of yours (or leave it out), then check again.
- Import. It runs in the background, managers first, with progress per step. You can leave the page, cancel after the current batch, or carry on later.
- Summary. What was created and updated, with the next steps: invite people to sign in, check time off and start onboarding for people starting later.
Running the same move again updates what it moved before instead of making duplicates.
Undo#
For 24 hours after an import, Undo on the summary removes what it created (people, their job rows, pay, leave, balance adjustments and documents, and the teams, locations and fields nobody else uses) as long as nothing changed since. Someone edited, given a login or invited after the import is kept and listed with the reason. Changes to people who were already in Bizisy are not reverted.
Privacy#
- Files you upload are deleted as soon as they are read. An API key you connect is stored encrypted, used only to read (Bizisy never writes to your old tool), and removed when the move ends or 24 hours after you connected it, whichever comes first. You can also delete it in the old tool once you're done.
- A move, with its rows and their checks, is kept 30 days and then deleted. A row is emptied once it is imported (the person's record holds the data).
- Activity records each move with counts only, never names or values.
- The privacy policy says the same under "Moving from another HR tool".
With your AI#
An AI app connected to Bizisy (or an API key) can move people too: it pastes the people export as CSV text, at most 250 people, checks it, shows you the dry-run report and imports when you agree. It moves people, teams, locations and custom fields that aren't private; pay, payroll identifiers, sex, private details, time off and documents stay in the app. Ask it to read skill://migration/move-from-another-tool first (Skills). The actions are migration.start, migration.check, migration.items, migration.fix_items and migration.import; undoing a move happens in the app. See What machines can see.
Something missing or wrong on this page? Write to hello@bizisy.com.