Skip to content

Guides

Move from Sesame HR to Bizisy

On this page

Move your people, their jobs, departments, managers and holidays from Sesame HR to Bizisy with Sesame's export files. 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.

What moves, and what doesn't#

MovesHow
People with their contact details, and private details (birthday, personal email and phone)From the file. 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. Job history moves only through an API connection (Personio, Factorial, BambooHR or HiBob).
Teams, departments and locationsMatched by name; the missing ones are created (new locations get your company's country unless you choose another).
ManagersBy email, by name or by the Sesame ID, whichever the file has.
Time offBalances ("available" on the day of the move) and past and future leave, from a second file. Leave is recorded as booked by HR: no approvals, no emails.
PayOnly 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.
DocumentsNot from Sesame: documents move only through an API connection, which Sesame isn't offered for yet. Download the ones you need from Sesame and add them to each person in Bizisy.
Custom fieldsA 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 Sesame HR#

  1. In Sesame, open Empleados and click Exportar empleados (top right) (exportar empleados).
  2. Choose the fields to move: nombre, apellidos, email, código, DNI/NIE, puesto, departamento, centro, responsable, fecha de alta, tipo de contrato, horas semanales, and any you want to keep. Spanish labels are recognised as they are.
  3. Download Excel or CSV. The report Informes → Información completa del empleado in Excel or CSV works too (informes).
  4. For holidays, export your vacaciones (empleado, tipo, fecha de inicio, fecha de fin, días, estado) and add it as the second file.

Moving from Sesame works with files only: Bizisy doesn't connect to Sesame's API yet.

What the wizard does#

  1. Choose the tool. Bizisy knows each tool's column names, in the languages it exports in (for a spreadsheet: common names in seven languages).
  2. Upload or connect. Upload the people file (.xlsx or CSV, up to 20 MB and 10,000 rows) and, if you have it, the vacaciones file.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  • 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.

Developer docs