Skip to content

Guides

Move from BambooHR to Bizisy

On this page

Move your people, their jobs, departments, managers and time off from BambooHR to Bizisy, with a report export 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#

MovesHow
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 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 BambooHR ID, whichever the file has.
Time offBalances ("available" on the day of the move) and past and future leave, from a second file or the API. 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.
DocumentsThrough the API connection only: the files BambooHR 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 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 BambooHR#

  1. In BambooHR, open Reports, pick a standard report or build a custom one with the fields to move: employee #, first and last name, work email, job title, department, division, location, reporting to, hire date, employment status, and any you want to keep (export employee data). The Company Directory CSV works too (company directory).
  2. Click Export and choose CSV or Excel. Bizisy reads BambooHR's US dates (month first) and "Reporting to" written as "Last, First".
  3. For time off, export the Time Off Requests report and, for balances, a report with employee, email, time off type and available; add them as the second file.

Or connect with an API key#

  1. In BambooHR, click your photo (bottom left) → API Keys → Add New Key (create a new API key). The key has your own permissions, so create it as someone who sees everyone.
  2. Paste the key and your company domain (the part before .bamboohr.com) into Bizisy.
  3. Bizisy reads the directory, each employee's job, employment status and compensation tables, time-off requests and balances, and files; it never writes to BambooHR.

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 report (CSV or .xlsx, up to 20 MB and 10,000 rows) and, if you have them, the time-off files. Or paste the API key.
  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. 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.

Developer docs