Employee ID Mapping (Worker ID): In Deel, the unique identifier used for syncing is the Worker ID. This will map automatically to the Employee ID field in Culture Amp. If you are transitioning from a manual CSV import, verify that your current Culture Amp Employee IDs match the Deel Worker IDs.

Essential Permission Scopes: When generating your API token in Deel, you must select all available scopes, specifically including "contracts." Missing this scope is the most common cause of "403 Forbidden" errors and will prevent Culture Amp from reading your employee data.

Unsupported Demographics (Gender & Level): Due to specific API restrictions within Deel, the Gender and Seniority/Level fields cannot be synced automatically at this time. If you require these demographics for your reporting, they must be managed via a manual file upload.

Hierarchy Sync: Culture Amp builds your reporting structure using the Direct Manager field in Deel. For the hierarchy to sync correctly, the manager must be an active user in Deel with a valid work email address that matches their Culture Amp profile.

Active Status Logic: The integration is designed to pull users marked as "Active" in Deel. Employees without a valid "Active" status or those missing a Start Date may not appear in the sync results.

Syncing Teams: Deel "Teams" are treated as a separate organizational group. Because these don't map automatically, you must manually align them to a Culture Amp demographic (like "Department") during Step 2: Field Mapping.

Organization Token

You must be a Deel admin to complete the linking flow

Your Deel account must have API access enabled. Contact your Deel account manager to confirm if you are unsure of this

Now that the initial authentication is complete, on your Integrations page, click Map fields.

Select the data model for your target field (e.g., Employee).

Set the details for the field you are targeting in Culture Amp (the demographic name, e.g., Location).

Select the matching Deel field that contains the data.

You can Save mappings or click the + Field mapping icon to add more.

Alternatively, if you’re not ready to map fields yet, you can click Skip for now and return to mapping later.

Click on Map fields to begin the workflow.

You will see a field mapping for Exclude from Culture Amp in the workflow.

Search for the corresponding field from your HRIS under the Exclude from Culture Amp field.

Ensure that employees you want to exclude are marked as "Yes" in your HRIS.

Click Save mappings
​

Demographic Consistency: When mapping fields, you must map the data to the exact same demographic field you used historically (e.g., mapping to "TEAM" is different from mapping to "TEAM NAME"). Using an incorrect or slightly different title risks discontinuity in your trended survey results.

Recommended Action: To avoid confusion, we recommend navigating to Settings > Employee Data Demographics and deleting the old, unused demographics after your first successful sync. (This won't impact any previous survey results.)

As long as at least one of these remains consistent between Deel and Culture Amp, the sync will successfully update the existing profile rather than creating a new one.

Duplicate Risk: If you change both the Email and the Employee ID simultaneously in Deel, the sync will not find a match and will create a duplicate profile.

When It Happens: The sync is blocked if a combination of an employee's Name, Date of Birth, or Email is changed simultaneously.

Purpose: This prevents one employee from accidentally getting access to another employee's private information (like performance reviews).

Fix: If you've intentionally changed the employee's details, you can run a manual sync to push the change through. Go to Settings > Employee Data > Users, click Import data, and select Sync. Culture Amp will guide you through the rest.