SSO and Access Tokens: Ensure the Namely user account used to create the Personal Access Token is not SSO-enabled. If it is, the sync will fail with an "Invalid access token" error.

Date Format Alignment: You must ensure the Date Format selected in Culture Amp matches the format used in Namely (found under Profile > Settings). Inconsistent formats will cause sync failures for start and end dates.

Employee ID Defaults: If the "Employee Number" field is not populated in Namely, Culture Amp will use the unique Namely ID as the default identifier. If you wish to use your own numbers, you must include the "Employee Number" column in your report.

First and Last Name Cleanup: When creating a report, Namely adds "First Name" and "Last Name" by default. You must remove these in favor of the single Full Name column to meet integration requirements.

Deactivation Options: By default, users left off your sync file are categorized as former employees with an end date. If you prefer these users to be "deactivated" instead, you must contact Culture Amp Product Support to adjust this setting.

How to Add: Click "Add Column" in your Namely report builder to include any desired fields. Because there is no manual mapping screen for Namely, these columns will appear in Culture Amp exactly as they are titled in your report.

Naming Convention: Ensure your Namely column headers match the demographic names you want to see in Culture Amp (e.g., if you want a "Team" demographic, the Namely column should be titled "Team").

System Logic: The sync only "sees" employees who are rows in your report. Any employee filtered out of the report will not be sent to Culture Amp.

Full Import Impact: Because Namely utilizes a "Full Import" process, if an active Culture Amp user is removed from your Namely report, they will be automatically deactivated as a "Former Employee" upon the next sync. Their End Date will be set to the day before the sync.

For Namely, the hierarchy source is the Reports To Email column in your Namely report.

As long as Reports To Email is included in your Namely report and in the file used by the integration, Culture Amp will continue to populate Manager Email correctly from that field.

The Reports To Email column in Namely should hold the manager’s work email address for each employee; this value is what ultimately populates Manager Email in Culture Amp.

If you want manager names in Culture Amp as well, put them in a separate column (e.g., Manager Name) and treat that as a non-hierarchy demographic.

Every manager must be included in the Namely report (and not excluded via filters or Exclude from Culture Amp).

If a manager is missing from the Namely data, their direct reports will appear in Culture Amp with a blank Manager Email, breaking the tree for those employees.

Hierarchies must be keyed on an email identifier (e.g., Manager Email).

Demographics built from names (e.g., Manager Name) can be useful for display, but cannot serve as the primary hierarchy identifier.

Ensure your CEO/top-level leader has no Supervisor value in Namely. This results in a blank Manager Email, designating them as the "root" of your organizational tree when setting hierarchy up for the first time.

This will sync as a blank Manager Email for that person, allowing Culture Amp to treat them as the root of the hierarchy.

For Namely-driven hierarchies, always use the standard Manager Email demographic in Culture Amp.

Do not rename or repurpose this field; if you need a different label or a parallel field for historical reasons, follow the “Existing Hierarchy” options above or contact Support.

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 Namely 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 Namely, 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.