What can I learn from this page? | The differences between a partial or full import and when is best to use each |
Who is this guide for? | Account Admins |
The Culture Amp Import Wizard provides a seamless way for you to update a fraction — or all — of your employees.
With partial imports, you can use the import wizard to upload, review, and apply updates to a subset of your employees. Employees not included in the upload will remain active and unchanged in Culture Amp. To overwrite all user data already the system, you can still choose a full import.
Partial Import
A partial import updates employee demographic information for a subset of your organization. During the bulk import process, you can upload an employee data file that only includes information from a handful of your employees. Once processed, a partial import will only change that part of your organization. Employees not included in the import will remain active and unchanged in Culture Amp.
Partial imports are only available for CSV or XLSX file uploads.
When to use a partial import
Partial imports are a good option when you want to update demographics for some — but not all — of your employee base. Here are some commons scenarios where a partial import is useful:
Prompt/driver for import | Solution |
Launch onboard surveys to a batch of new starters | Add new starters to Culture Amp in bulk with partial import |
Launch exit surveys to a batch of recent departures | Update records of recent departures with partial import (requires also setting their end date to a future date) |
Pulse survey to a single division/department | Update demographic data for a single department, then create and launch a survey |
Correct inaccurate demographics for a handful of employees | Update troublesome records with partial import |
Full Import
A full import completely overwrites any user data you already have in the system. Any employees missing from the incoming employee data file will become inactive.
Full imports are available for both file uploads and HRIS integration syncs.
When to use a full import
Full imports are a good option when you want to make sure every employee record in your account is up-to-date. Here are some commons scenarios where a full import is useful:
Prompt/driver for import | Solution |
Ask for feedback from the entire company | Update all data in your account with full import |
Sync data using one of our HRIS native integrations | Native HRIS integrations always apply a full import |
Your company undergoes a restructure and the entire company tree changes | Update reporting demographics for your entire company with a full import |
Handling Inactive Employees
You can deactivate employees with both full and partial imports:
Full Import: A full import treats the file as the 'future state' of users in Culture Amp. If the file omits some users who are active in Culture Amp, they will be made inactive in the Culture Amp database. That is, the bulk edit treats a person missing from the user file as an intentional 'removal' of an active user. Any user with an
End Dateset to a date in the past will also become inactive.Partial Import: Users omitted from a partial import will remain active and unchanged in Culture Amp. To deactivate users via a partial import, set their
End Dateto a date in the past.