Skip to content
Get a quote

Personio to BambooHR migration

We migrate Employees, Absences, Documents, Recruiting Positions, and Compensation history from Personio into BambooHR with absence category translation, effective-dated salary entries preserved, and the Personio custom-application-field gap flagged before any data moves.

Short answer

FlitStack AI migrates employees, departments, time offs, employee files and job openings from Personio to BambooHR, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

By

Source Personio
DestinationBambooHR
EmployeeDepartmentTime OffEmployee FileJob Opening
Mapped field by field · sample run · one-click rollback

What moves from Personio to BambooHR?

The Personio to BambooHR migration is primarily a records migration with three structural adjustments: absence category mapping between the two systems, compensation history preservation as effective-dated entries, and a manual extraction step for custom application form fields that Personio does not expose through its API.

Read the full summary

BambooHR organizes data around the Employee as the central record, mirroring Personio's model, but differs in absence entitlement display (BambooHR shows balances per type rather than a calendar view) and in recruiting structure (BambooHR Job Openings contain a single embedded candidate list rather than separate Position and Application objects). We sequence the migration with Employee as the first import object because all other records depend on its employee ID, resolve Departments before Contacts, and map Absence types individually before entitlements load. We do not migrate Personio Workflows, Approval Chains, or onboarding document templates as code; we deliver a written inventory of every active workflow and approval chain for the customer's HR admin to rebuild in BambooHR's workflow builder.

1:1

Employee → Employee

Personio Employee records map directly to BambooHR Employee.

How it maps

The employee's UUID from Personio is stored in a custom field bhr_legacy_id__c for reconciliation. BambooHR requires the Employee record to exist before any related objects (Absence, Documents, Compensation) can be imported, so we import Employees first and use the returned BambooHR employee ID as the foreign key for all dependent objects. We handle Personio's date-format inconsistencies (DD/MM and DD.MM by locale) by normalising all dates to ISO 8601 during extraction and validating numeric fields against expected ranges before load.

1:1

Department → Department

Organisational hierarchy of departments exports from Personio as a flat or nested list depending on the customer's configuration.

How it maps

We map departments to BambooHR Departments before Employee import so that the department_id resolves at the time of Employee insert. BambooHR supports a flat department list; nested sub-departments in Personio map to the parent department in BambooHR with a note that hierarchical org chart visualisation is handled in BambooHR separately.

configuration

Absence → Time Off

Personio Absence records (vacation, sick leave, and other absence types) map to BambooHR Time Off entries.

How it maps

Each absence category in Personio must be mapped individually to a BambooHR Time Off type because the system-level type names differ between platforms. Entitlement balances export from Personio as effective-dated records and are created as accrual rules in BambooHR. We flag any absence categories that have no direct BambooHR equivalent (for example, special German leave types) and present a mapping table to the customer for confirmation before import.

1:1

Document → Employee File

Employee documents (contracts, certificates, ID scans) stored in Personio are retrieved via the API and mapped to BambooHR Employee Files.

How it maps

Document naming conventions in Personio vary by company and by folder structure, so we flatten the hierarchy into a single file list per employee and map the Personio document category to a BambooHR file category label. Binary file content transfers directly. We flag any files that exceed BambooHR's size limits or use unsupported formats.

1:1

Recruiting Position → Job Opening

Personio Recruiting Positions (job postings with department, location, status, and hiring manager metadata) map to BambooHR Job Openings.

How it maps

We map Personio's position status (open, paused, filled, cancelled) to BambooHR's Job Opening status equivalents. The hiring manager field resolves via the Personio manager UUID to the corresponding BambooHR employee record.

1:1

Application → Candidate

Personio Applications (candidates linked to recruiting positions) map to BambooHR Candidates.

How it maps

The candidate's email address serves as the dedupe key during import. Standard application fields (name, email, phone, status, source) migrate directly. However, custom_attributes configured on Personio application forms are not accessible via any documented API endpoint, so we request the customer to enumerate these fields and their data during scoping, then create equivalent custom fields in BambooHR before applying the values. Without this step, custom candidate data is not transferred.

What moves12 objects
PersonioBambooHR
  • EmployeeEmployee1:1
  • DepartmentDepartment1:1
  • AbsenceTime Offtransformed
  • DocumentEmployee File1:1
  • Recruiting PositionJob Opening1:1
  • ApplicationCandidate1:1

+ 6 more in the mapping below

How Personio and BambooHR differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionPersonioBambooHR
Primary market focusUK, Ireland, Germany, and wider EU with native GDPR and local employment law complianceUS-headquartered SMB market with limited native EU compliance tooling
Absence displayCalendar view with entitlement balances per employeeTime Off balances per type with accrual rules on the employee record
Recruiting structureSeparate Position (job posting) and Application (candidate) objectsJob Opening with embedded candidate list in a single object
Performance managementBasic reviews and goal tracking, limited 360-degree cyclesStronger performance management with configurable review cycles and competency frameworks
PayrollNative in Germany with DATEV integration; payroll prep for UK and EU via validated exportsUS-native payroll add-on; EU payroll via third-party integrations (Nmbrs, AFAS)
Report builderLimited — cannot copy reports between views or apply advanced filtersRule-based reporting, limited flexibility for advanced users
Custom application fieldsStored on recruiting forms but not accessible via documented APIStandard candidate fields accessible via BambooHR API

What to watch for in a Personio to BambooHR migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Personio API rate limit of 300 req/min on employee export

Personio's GET Employees endpoint enforces a rate limit of 300 requests per minute introduced in May 2024, with a burst capacity of 15 requests per second.

How we handle it

Exceeding this returns a 429 error and can stall the migration if not handled. We implement paginated requests with exponential backoff and a request queue that throttles to 280 req/min to maintain headroom. For migrations with fewer than a few hundred employees this is not a bottleneck, but larger headcounts require careful pagination planning to stay within the limit without extending migration timelines significantly.

high

Custom application form fields not accessible via Personio API

Personio's recruiting application forms support custom_attributes configured by the customer, but these are not retrievable via any documented API endpoint.

How we handle it

During scoping we explicitly ask customers to provide the list of custom application fields and their data. Without this step, custom candidate data from recruiting forms is silently absent from the BambooHR migration. We create equivalent custom candidate fields in BambooHR before applying the manually provided data, and note this gap in the migration report.

medium

Date and number format inconsistencies in Personio by locale

Personio stores dates and numbers inconsistently depending on the account's locale setting — the same field may appear as 24/12/2019 or 24.12.2019, and overwriting a salary field can append an extra zero.

How we handle it

We normalise all extracted dates to ISO 8601 and validate numeric fields against expected ranges before loading to BambooHR. This preprocessing step adds a validation pass to the extraction phase but prevents corrupted date entries and salary anomalies from landing in BambooHR.

medium

BambooHR date format must match account settings

BambooHR allows configurable date input formats per account.

How we handle it

If the BambooHR account's date format setting (found in Settings, Account, General Settings, Date Input Format) does not match the format of the incoming Personio data, date fields may be misinterpreted on import. We configure the attributeMappings.date parameter to match the destination account's setting and verify this setting during the scoping phase before any data moves.

low

Personio domain migration leaves API at .de subdomain

Personio completed its web migration from personio.de to personio.com in March 2025, but the Public API remains at developer.personio.de.

How we handle it

We whitelist developer.personio.de in all connection configurations and inform customers that IT allowlists must include both the .com web domain and the .de API domain. Failing to whitelist the .de API endpoint causes the migration connection to fail silently without an error message pointing to the domain.

How the migration runs

  1. Discovery and scoping

    We audit the source Personio account across all active modules (HR Core, Recruiting, Performance, Payroll, Time Tracking), custom attributes on each object, active absence categories, recruiting pipeline stages, and document volume per employee.

    What this step covers

    We confirm the BambooHR destination account settings including date format, time-off types, and any existing custom fields. The discovery output is a written migration scope covering which objects are in scope, which require manual data provision (custom application fields), and which are excluded (workflows, approval chains). We also confirm the Personio API credentials and whitelist the developer.personio.de endpoint in the connection configuration.

  2. Custom field enumeration and schema creation

    We enumerate all custom attributes in Personio via API schema introspection.

    What this step covers

    For each custom attribute on Employees and Positions, we create a matching custom field in BambooHR. For custom application form fields on recruiting forms, we request the customer to provide the field list and sample data during this step because the Personio API does not expose them. We create a mapping table for absence categories, confirm each Personio type with its BambooHR equivalent, and set up accrual rules for entitlement balances. All schema changes are applied to BambooHR in a pre-migration validation pass.

  3. Department and employee dependency resolution

    We extract Departments from Personio first and create them in BambooHR before Employees so that department_id references resolve at import time.

    What this step covers

    Employees are extracted second with all standard and custom fields, date formats normalised to ISO 8601, and numeric fields validated. We resolve the BambooHR employee ID for each Personio employee record and hold this mapping in a lookup table used for all subsequent dependent object imports. A reconciliation report compares the Personio employee count to the BambooHR insert count before proceeding.

  4. Documents, absence, and compensation import

    Employee documents transfer from Personio to BambooHR Employee Files using the employee ID lookup.

    What this step covers

    Absence records load after employees with category-to-type mapping confirmed. Compensation history loads as effective-dated entries against each employee using the employee ID lookup, with historical entries stored in the custom pay history table and the most recent entry applied as the current compensation rate. Each phase emits a reconciliation report before the next phase begins.

  5. Recruiting pipeline import

    Personio Recruiting Positions export as Job Openings in BambooHR with status and hiring manager fields resolved.

    What this step covers

    Candidates export from Personio Applications and import to BambooHR Candidates using email as the dedupe key. Standard fields transfer directly; custom application field values from the manually provided enumeration are applied to the corresponding BambooHR custom fields. The job opening to candidate linkage is preserved by matching the BambooHR Job Opening ID against the candidate's application history.

  6. Performance, goals, and benefits import

    Performance Reviews transfer with review cycle, status, ratings, and reviewer assignments.

    What this step covers

    Written review text migrates as notes on the review record. Goals and OKRs transfer with titles, descriptions, progress, and employee linkages, with parent goal IDs preserved in a custom field. Benefits enrolments transfer as benefit type and coverage level entries. All records use the employee ID lookup from Step 3.

  7. Cutover, validation, and workflow handoff

    We freeze Personio writes during the cutover window, run a final delta migration of any records modified since the initial extraction, then set BambooHR as the system of record.

    What this step covers

    We deliver the Workflow and Approval Chain inventory document to the customer's HR admin for rebuild in BambooHR's workflow builder. We support a one-week post-migration validation window where we resolve any reconciliation discrepancies raised by the customer's team. We do not rebuild Personio workflows as BambooHR automations within the migration scope; that work is a separate engagement.

Personio BambooHR
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · BambooHRRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

3-5 weeksTypical, smaller accounts
6-10 weeksLarge or heavily customised accounts

A quote scales with employee count, document volume, recruiting position count, and whether compensation history and custom application fields are in scope. Personio's implementation fee (charged on their side) and BambooHR setup fee are outside the FlitStack AI migration cost. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Personio to BambooHR →

Why teams move from Personio to BambooHR

  • Users consistently cite Personio's report builder as a friction point: reports cannot be copied between views, advanced filters are unavailable, and the same report must be rebuilt manually for each use case. BambooHR's reporting, while not enterprise-grade, is rated 4.4 for functionality on Capterra versus Personio's 3.9, and supports export for external analysis. Companies that rely on HR analytics for headcount planning, absence trends, and recruiting pipeline reporting migrate to BambooHR to eliminate the repeated manual work.
  • Performance management and feedback tools in Personio are considered thin by reviewers compared to dedicated performance platforms. BambooHR offers configurable review cycles, competency frameworks, and 360-degree review templates that reviewers on G2 and Capterra rate more highly for teams with established performance cultures. Companies with annual review processes and development planning migrate to BambooHR when Personio's module no longer meets their performance management maturity.
  • Companies headquartered outside the EU or with a primarily US-based workforce find Personio's European compliance tooling unnecessary and its EU-centric features a net cost. BambooHR is designed for US-headquartered SMBs with straightforward single-entity setups, offering an intuitive consumer-style interface that Capterra reviewers rate 4.6 for ease of use versus Personio's 4.4. Teams with global or US-centric operations migrate away from Personio when EU compliance overhead outweighs its benefits.
  • Personio charges an additional implementation fee on top of its subscription, and implementation timelines can extend to 6-8 weeks depending on company size. BambooHR's ATS comes built-in without an add-on module cost, and Capterra reviews indicate a faster time-to-value for small teams that do not require complex EU payroll integration. Companies migrating from Personio to BambooHR frequently cite total cost reduction and faster onboarding as decision factors.
  • BambooHR integrates with over 150 applications including payroll providers, background check tools, and standalone ATS platforms, while Personio's integrations are more EU-centric (DATEV, Xero, Sage 50). Companies that rely on US-native tools like Gusto for payroll, Checkr for background checks, or Tellent/Recruitee/Greenhouse for recruiting migrate to BambooHR because the integration ecosystem is better suited to US-based HR stacks.

Questions, answered

Personio to BambooHR migration questions

How long does a Personio to BambooHR migration take?

Most migrations land between three and five weeks for accounts under 500 employees with core HR data (Employees, Absences, Documents, Departments) and no active recruiting pipeline. Migrations above 500 employees, with active recruiting positions, full compensation history, multiple legal entities, or custom application form fields requiring manual extraction move to six to ten weeks. The timeline also depends on customer sign-off speed on the absence type mapping table and custom field enumeration.

Do Personio Workflows and Approval Chains migrate to BambooHR?

No. Personio absence approval chains, onboarding step workflows, and document signing approval sequences are not exposed via the API in a migration-ready format and we do not transfer them as code. We deliver a written inventory of every active Personio workflow and approval chain with its trigger, conditions, assigned approvers, and a recommended BambooHR equivalent. The customer's HR admin rebuilds these in BambooHR's workflow builder post-migration. E-signature templates used in Personio's onboarding and document workflows are similarly listed as items requiring manual recreation in BambooHR.

Can we migrate our recruiting data from Personio to BambooHR?

Yes, recruiting data migrates with one caveat. Standard Personio Recruiting Positions map to BambooHR Job Openings and standard Applications map to BambooHR Candidates with email as the dedupe key. However, custom_attributes configured on Personio application forms cannot be retrieved via the API, so we request the customer to enumerate these fields and their values during scoping. We create matching custom candidate fields in BambooHR and apply the manually provided data. Without this enumeration step, custom candidate data is not transferred and is noted as a gap in the migration report.

Is BambooHR a suitable destination for companies with EU employees?

BambooHR is designed for US-headquartered SMBs and its native compliance tooling covers US employment law. EU employee data (contracts, absence entitlements, country-specific fields) migrates as standard employee records, but EU-specific compliance features such as GDPR data retention rules, local absence entitlements, and country-specific employment contract templates are not native to BambooHR and require manual configuration post-migration. Companies with significant EU headcount or multi-country operations should evaluate whether BambooHR's third-party EU payroll integrations and manual compliance setup meet their needs before migrating from Personio.

Do we lose historical absence and compensation data in the migration?

No. We migrate the full absence history (all past absence entries per employee) and the full compensation history (all effective-dated salary change entries) from Personio. Absence records load with their original dates and types mapped to BambooHR time-off types. Compensation history entries are stored in a custom pay history table in BambooHR with each effective date preserved, and the most recent entry is set as the current compensation rate on the employee record.

Why are Personio and BambooHR on different timelines for implementation?

Personio charges an additional implementation fee and reports an average 4-6 week setup from contract signing, with a dedicated implementation specialist. BambooHR implements in approximately two months according to G2 reviews, but does not charge a separate implementation fee on top of its subscription. FlitStack AI operates independently of both platforms' implementation timelines; our migration runs in parallel with or after the customer's BambooHR setup, and we do not charge for the time spent during the vendor's own onboarding period.

How does FlitStack AI handle Personio's API rate limits during migration?

We implement paginated extraction from the Personio API with a request throttle set to 280 req/min, maintaining a 20 req/min headroom below the 300 req/min limit. For employee counts above 500, we chunk the extraction into batches with exponential backoff on any 429 responses. This approach ensures no records are lost or duplicated and does not significantly extend migration timelines for typical SMB volumes. We test the throttle settings in the scoping phase and adjust batch sizes based on the observed response latency.

Get a quote

Moving from Personio to BambooHR?

Tell us roughly how many records and objects you have. We scope the mapping and the BambooHR setup with you, then send a quote.

Get a quote