// troubleshooting guide · leapsome
Leapsome Not Syncing Employees From BambooHR or Personio
- Status
- Workaround available
- platforms:
- Web
- updated:
- November 17, 2026
- reports:
- 2
- Method
- how we research
RUNBOOK · leapsome/hris-sync-employees-missing5 FIXES
// quick answer
Leapsome only creates accounts for HRIS employees who are Active and have a work email, aren't excluded by a custom-attribute rule, and don't share an email with an existing user. A 'Successful' sync just means the list was fetched; check User Provisioning Insights for skipped people.
Most likely fix: Check status and email in the HRIS
How to fix it
// try these in order, the most common fix is first
FIX 1Check status and email in the HRIS
- 01Set the employee status to Active
- 02Fill in the work email
- 03In Personio, make Email and Status readable in the API credentials
Did this fix it?FIX 2Read User Provisioning Insights
- 01Open User Provisioning Insights in Leapsome
- 02Look at the latest run for skipped employees (missing email, no external ID, duplicates)
- 03Fix the record in the HRIS and wait for the next sync
Did this fix it?FIX 3Review exclusion rules
- 01Open the BambooHR/Personio custom attribute settings
- 02Check the user exclusion criteria
- 03Make sure the value matches the HRIS value exactly and the attribute is mapped
Did this fix it?FIX 4Find duplicate emails
- 01Go to Company > Employees > Export
- 02Search the export for the missing person's email
- 03Change or remove the conflicting profile
Did this fix it?FIX 5Re-enter credentials
- 01For BambooHR enter only the subdomain (e.g. 'mycompany')
- 02For Personio paste the Client ID and Secret carefully without extra spaces
- 03Re-authenticate; the resync can take a few hours depending on team size
Did this fix it?
Symptoms
New hires don't appear in Leapsome, some employees are missing after the sync, or changes in the HRIS don't show up.
Why it happens
- C-01Employee status isn't 'Active' or the work email is empty in the HRIS
- C-02Personio API credentials don't have Email and Status set as readable
- C-03A custom-attribute exclusion rule filters the person out
- C-04The email is already used by another Leapsome user in the workspace
- C-05Extra characters pasted into the Personio Client ID or Secret
- C-06Full BambooHR URL entered instead of the subdomain
- C-07Sync runs within 24 hours, so recent changes aren't there yet
// this guide also covers
- leapsome bamboohr sync
- leapsome personio integration not working
- leapsome employees not syncing
- leapsome hris sync
Still not working?
If Leapsome keeps failing, you're not alone. See every Leapsome problem users report or the alternatives people switch to.
Done fighting Leapsome? Our small team builds your own Leapsome alternative, or any software you need: web, mobile, games, desktop. Price agreed together.
Talk to usThe same problem in other apps
Lattice 1:1 Not Syncing With Outlook or Google Calendar (Lattice)
Culture Amp HRIS Sync Missing Employees (Culture Amp)
15Five HRIS Connector Sync Errors (15Five)
Other Leapsome errors
- Leapsome Login Not Working
- Leapsome SSO Not Working (Okta, Azure AD, Google)
- Leapsome Slack Integration Not Working
- Leapsome Microsoft Teams Integration Not Working
- Leapsome Meetings Not Syncing With Google Calendar or Outlook
- Leapsome Notifications Not Received
- How to Stop Too Many Leapsome Notifications
- Can't See Leapsome Review Results