Before you import
1
Create your departments first
The import assigns people to departments by name. A department that doesn’t exist yet can’t be assigned, and fixing it afterwards means editing every affected member by hand.
2
Publish your template first
Same reasoning. Members imported without a template build their own profiles, and pulling them back onto a template later is more work than getting it right first.
3
Check the email addresses
They’re the login, the invitation destination, and the key for CRM owner assignment. Verify them against your CRM’s user list before importing, not after.
Running the import
Members → Import. Upload your file, map your columns to Tap’s fields, and start the import.Reading the import status screen
Imports run in the background — a large file keeps processing after you navigate away. The status screen shows each row’s outcome.Re-importing a file is safe. Rows whose email already exists are skipped rather than duplicated, so fixing a few failed rows and re-uploading the whole file won’t create second copies of everyone else.
Common failures
Invalid email address
Invalid email address
A typo, a missing domain, or a stray space. Spreadsheets are good at hiding trailing spaces — trim the column before exporting.
Department not found
Department not found
The department name in the file must match an existing department exactly, including spelling and case. Create the department, then re-import the failed rows.
Duplicate email in the file
Duplicate email in the file
Two rows with the same address. The first is imported and the second skipped — which is usually correct, but check you didn’t mean to add two different people.
The file is the wrong format
The file is the wrong format
Export as CSV or XLSX. A CSV saved with an unusual delimiter or encoding can import as a single mangled column — if the mapping step shows one column where there should be six, that’s the cause.
