Bulk import users and resolve import errors
Prepare a user-account CSV and validate its rows before importing.
Table of Contents
Bulk import creates many people from a CSV file. Quantum checks the rows before saving, so use validation as a review checkpoint rather than assuming a file upload has completed onboarding.
Before you begin
- You need permission to create people and an approved account list.
- The Users importer accepts a CSV file of up to 1,000 rows. Use the current template from the interface.
Steps
- Open Users → Bulk import. Select Download CSV template.
- Populate the template’s columns: email is required; username is optional. Other displayed columns are firstName, lastName, function, and jobTitle. Preserve the template’s header spelling.
- Check that each row represents the intended person, email addresses are accurate, and duplicate or already-existing accounts have been reviewed. Split larger populations into files within the displayed row limit.
- Choose the CSV in the upload area, then select Validate file. Review the validation results before continuing.
- Resolve the errors identified by validation in the source CSV and validate the corrected file. Review the accepted population and the final confirmation before saving the import.
- Return to Users and verify a sample across the imported population, including optional profile fields and intended sign-in handling.

Expected result
Only the reviewed and accepted import population is saved. Uploading a file alone does not finish the import.
Verify the configuration
- Compare the resulting directory population with the approved file and import results.
- Spot-check first/last names, job titles, and usernames.
- Check invitation delivery and intended SSO assignment where applicable.
Troubleshooting and maintenance
- If a column is not recognized, restart from a fresh downloaded template and check delimiter and header spelling.
- If validation rejects rows, use the exact reported reason to correct the file rather than submitting the same file repeatedly.
- Do not assume re-importing is an update or replacement operation; inspect the current validation behavior and existing accounts first.
Distinguish account import from HR synchronization
The Users bulk importer uses the account CSV and validation flow described above. Ongoing HR synchronization uses saved mappings under Data management → HR Sync and has separate validation, login-creation, and unattended-file controls. Use Configure HR data sync and SFTP intake for that process rather than reusing the Users importer as an assumed update feed.
For reissued employee IDs, use the configured HR Sync mapping and matching process. HR Sync can use Previous employee ID where configured. The Users bulk importer has its own supported file format; do not add HR Sync mapping fields to its CSV unless that importer explicitly offers them.