This article describes how to set up and manage the integration between Leapsome and Deel when Leapsome is your primary source of truth for employee data.
With this integration, you can manage your employee lifecycle, including new hires, profile updates, and terminations, directly in Leapsome and have those changes automatically reflected in your Deel account. This eliminates duplicate data entry and ensures your global payroll and employer-of-record platform is always in sync with your people enablement platform.
Table of contents
What the integration does
Before you get started
Setting up the integration
Attribute mapping details
Error handling
Revoking the integration
Frequently Asked Questions
What the integration does
This is a one-way integration: data flows only from Leapsome to Deel. It will not sync users or data from Deel back into Leapsome.
When Leapsome is configured as the source of truth for Deel, the integration will:
- Provision new hires: Create an employee record in Deel when a new user is added to Leapsome.
- Sync profile updates: Push changes made in Leapsome (e.g., preferred name, location, phone number) to the corresponding record in Deel.
- Sync terminations: Update the end date in Deel when an employee is terminated in Leapsome.
- Automate data flow: Synchronize data automatically and allow manual retries for failed syncs.
Before you get started
To ensure a smooth setup, please confirm the following:
- Admin access: You must have 'Super-Admin' permissions in Leapsome to set up or manage this integration.
- Unique identifiers: Ensure that existing employees have matching email addresses in both systems to avoid creating duplicate records.
- Field mapping: Review which attributes you want to sync before running the first synchronization.
Setting up the integration
1. Enable and authenticate the integration in Leapsome
Navigate to Settings > Integrations and imports > HRIS Integrations > Outbound Provisioning
- Locate the Deel card and click on it to open the integration modal
- Click 'Connect Deel account'
- In Deel, use an account that is allowed to install or authorize third-party apps for your organization, so the OAuth consent can complete successfully.
- Leapsome connects to Deel using OAuth:
- In the modal, choose ‘Connect’
- You will be redirected to Deel to sign in and approve the connection and the requested access.
- After you complete consent, you are returned to Leapsome. The status should show as connected when the link is successful.
Note: This integration is one-way. It only allows the sync of users from Leapsome to Deel. It will not sync users from Deel to Leapsome. If you need to pull data from Deel into Leapsome, please refer to this article.
2. Map your attributes
In the integration settings, you can define which Leapsome fields map to Deel fields.
- Locked fields: Some fields (such as first name, last name, and work email) are mandatory and locked; they cannot be remapped
- Optional fields: All other fields can optionally be synced and mapped to the correct Deel attributes
- Custom attributes: If you have custom fields in Leapsome that need to reach Deel, you can map them here
3. Save and trigger a sync
Once mapping is complete, click 'Update' to save your configuration. The integration will then begin syncing automatically. You can also click 'Sync now' at any time to force an immediate update.
Automatically create employees in Deel
Use the toggle (e.g. Automatically create employees in Deel to choose behavior:
- On: When a Leapsome user does not yet match anyone in Deel, Leapsome can create a corresponding person in Deel, subject to required data (see below).
- Off: Leapsome only updates people who already match in Deel (by stored Deel link, employee ID, or work email). Users with no match are skipped until a match exists or you turn creation on.
New hire requirements (when creation is on)
To create someone in Deel, Leapsome typically needs at least legal first name, legal last name, work (corporate) email, and hiring date, and the integration must have a valid Deel organization context (team and legal entity) when your Deel setup requires it.
Attribute mapping details
Not all fields behave the same way. Some fields can only be set during new hire creation and cannot be updated afterward. In the same modal, review attribute mapping.
- Locked rows: Legal first name, legal last name, and work email are fixed mappings from Leapsome first name, last name, and corporate email; they cannot be remapped.
- Additional rows: Add optional mappings (e.g. job title, location, phone). Each mapping can usually be turned on or off for sync. Optional fields respect Deel’s rules (some values only apply on create, on update, or not at all—use your in-product sync behavior labels or table).
- Custom data: Leapsome custom attributes can be mapped to custom fields defined in Deel (custom field list is loaded from Deel after you are connected).
Please note: Department/team syncing requires that the corresponding departments already exist in Deel's Organization Settings. If the department name in Leapsome doesn’t exactly match an entry in Deel, that field will be skipped for the user; the rest of their data still syncs.
Error handling
If a sync fails for one or more employees, the errors will be surfaced directly in the Deel integration settings modal, alongside the name of the affected user. You can retry a failed sync manually from the same view by clicking 'Sync now' next to the relevant error.
Revoking the integration
If you'd like to disable the integration, click the 'Revoke authorization' button in the Deel modal. Clicking 'Revoke authorization' will disconnect the integration, remove all stored Deel credentials and configuration, and stop the automated data sync immediately.
Frequently Asked Questions
1. How often does the sync run?
The integration syncs employee data automatically in the background. You can also trigger an immediate update at any time by clicking 'Sync now' in the Deel integration settings.
2. What happens if I update an employee's profile in Leapsome?
Any changes to mapped attributes will be pushed to Deel automatically during the next sync. You may also trigger the push manually by clicking 'Sync now'. Because Leapsome is the source of truth, manual changes made to those same fields inside Deel may be overwritten during the next sync.
3. Does this integration handle payroll calculations?
No. This integration manages identity and profile data. Payroll calculations, compensation reviews, and benefit elections must still be managed within the Deel platform.
4. What happens when an employee is terminated in Leapsome?
When an employee's termination or end date is set in Leapsome, that information will be synced to Deel automatically. The employee's record in Deel will be updated accordingly.
5. Can I exclude certain users from the sync?
The sync currently processes all active (active, invited, pre-boarding, created) Leapsome users and creates or updates their information in Deel.
6. Where are errors for the sync surfaced?
If there are any errors or warnings raised during an employee sync, they will be listed in the Deel settings modal and will indicate which user the error is associated with. You can retry the sync for affected users directly from this view.
7. What is the difference between this integration and the existing Deel connection via Merge?
The inbound Deel integration (via Merge) pulls data from Deel into Leapsome. The outbound integration is outbound only and pushes data from Leapsome to Deel, making Leapsome the source of truth.