HiBob migration guide

If you're already connected to HiBob through Eletive's legacy integration, you'll need to migrate to the new OAuth connection — Bob's marketplace-based, one-click connection that replaces the old setup.

Migrating takes a few steps and a window where syncing is paused, but your existing Eletive users and their data won't be lost. This guide walks you through it in order.

Before you begin: back up your current configuration

Your current lifecycle, mapping, and filter settings will not carry over automatically to the new connection. Before disconnecting anything, go through your legacy Hibob integration in Eletive (Settings > Integrations > click on "Hibob (Legacy)) and note down:

• Lifecycle settings — what happens to starters and leavers (auto-pause, auto-remove, or manual review), and any configured delays.
• Attribute mapping — which Hibob fields map to which Eletive fields, beyond the defaults (first name, last name, email, employee ID).
• Filters — any rules limiting sync to specific departments, entities, or field values.

Take screenshots or write these down somewhere you can refer back to — you'll re-enter them in Step 5.

Also check Bob's side of the connection: review which People data the current legacy service user/API key has access to. You'll set this up again separately when you authorize the new OAuth app(see step 3), since Bob's OAuth consent flow determines access independently of the old setup.

Step 1: Disconnect the legacy connection

In Eletive, go to Settings > Integrations > click on "Hibob (Legacy).

1. Disable the intergration at the bottom of the page

2. Click on "Edit HRIS connection" in the top right corner.

3. In the pop-up click on the cog wheel and select the "Delete" option. 

These steps stops the daily sync and removed the existing connection with HiBo.
It does not delete your existing Eletive users or their data — they stay exactly as they are until the new connection is live.

Step 2: Update existing users' external IDs

This is the step that ensures the new connection recognizes your existing Eletive users instead of creating duplicates.

The legacy connector tagged users with an external ID prefixed hibob-. The new OAuth connector uses a different prefix, hibob-oauth-.

Before reconnecting, you need to update the external ID on every existing Eletive user that came from Hibob so the new connection matches them correctly.

1. Export your current Eletive user list, including the External ID column.
2. For every user whose External ID starts with hibob-, replace that prefix with hibob-oauth-, keeping the rest of the ID unchanged (for example, hibob-12345 → hibob-oauth-12345). You can use "Search and replace" functions for this type of task. 
   
   Only touch IDs with the hibob- prefix — leave any manually created users or users from other sources untouched.
3. Upload the updated file via User Mass Edit in Eletive.
4. Once complete, verify that the ExternalIDs has been updated successfully. 

Once this is done, the new connection will treat these as the same people rather than attemption to creating new records (which causes conflict errors).

Step 3: Reconnect via the OAuth connection

1. In Eletive, go Settings > Integrations click on Connect with HRIS
2. Select HiBob (OAuth)
3. Review the consent screen and configure which People  the integration should get access to.
   
   This defines which user that will be synced to Eletive, make it match your previous Service Users People data access/scope. 
   
   Then click Authorize. You'll be redirected back to Eletive to continue with the configuration. 

Step 4: Reconfigure your settings

Using the notes from "Before you begin," re-enter:

• Lifecycle settings — starter/leaver handling and timing.
• Attribute mapping — under Attribute Mapping, re-map as before.
• Filters — re-add any department/entity/field-based sync rules.

Step 5: Test before you rely on it

1. Click Test Integration, then Run test. This produces three lists: employees to be created, updated, and removed.
2. Check the Updated list in particular — since you've already re-tagged your existing users in Step 2, they should appear here if you configured everything correctly. Also check that the attributes include data from HiBob.  
3. Once the test results look right, you're ready to enable the new integration. 
   Once enabled, the connection will continue syncing automatically once every 24 hours, same as before.

Troubleshooting

Users are being created as duplicates instead of matching This almost always means an External ID wasn't updated to the hibob-oauth- prefix in Step 2, or was updated with a typo. 

My old lifecycle/mapping/filter settings didn't carry over Expected — see Step 4. These settings live on the connection itself and reset when you disconnect the legacy integration.

Support

Questions or issues during migration? Reach out to support@eletive.com, or contact your Eletive representative.