Import and export employees
Zenoti supports bulk employee operations through Excel file import and data export. The import uses a two-phase process (validate then commit) to ensure data integrity. Export supports both the employee listing and PII data export for compliance. This article covers the import and export workflows.
Audience: Administrators who manage employee records and need to add employees in bulk or export employee data for compliance or reporting purposes.
On this page
- Before you begin
- Import employees from Excel
- Export the employee list
- Export PII data
- What the exports do not include
- Tips
- Troubleshooting
- Related articles
Before you begin
- You must have at least one active job designation and center configured before importing employees. The import validates job codes and center codes against existing records.
- Download a fresh Excel template before each import run. Templates may change when new fields are added.
- Review your organization's employee code format before importing. If auto-generate employee codes is enabled, leave the employee code column blank and the system assigns codes automatically.
Permission: Enable Job-employee updates (under Job-employee updates) β Required to run employee import processes. Grant it on the Job-employee updates row in the Employee Manager section of the security role (Configuration > Security > Security roles > the role > Permissions).
Permission: View (under General Settings) β Required to access the employee listing and initiate export operations. The employee list also opens for roles that have Add General Settings or Delete on the Employee row, Edit on the General Settings row, or View All or Edit on the Commission Settings row. If the role has View Self on the Commission Settings row but neither View All nor Edit, the list shows only the signed-in employee. Grant it on the General Settings row in the Employee Manager section of the security role (Configuration > Security > Security roles > the role > Permissions).
Import employees from Excel
Download the import template
- Navigate to Employee > Employees.
- On the employee listing, select the import action.
- Download the Excel template.
- Open the template and review the column headers before entering data.
Always download a fresh template before each import to ensure you have the latest column structure.
Mandatory import fields
The following fields are required for every row in the import file. Rows missing any mandatory field fail validation and are not imported.
| Field | Description |
|---|---|
| First name | The employee's first name |
| Last name | The employee's last name |
| Gender | Male, Female, or Not Specified |
| Job code | The code of an existing job designation in your organization |
| Center code | The code of an existing center in your organization |
The import template supports additional optional fields such as email address, mobile phone, and employee code. When left blank, the system applies defaults from the job designation or generates values automatically based on your organization settings.
Worked example: To import a new employee named Jane Smith who works as a massage therapist at your downtown center, enter
Janein First name,Smithin Last name,Femalein Gender,MASSAGE-01in Job code (the code for your massage therapist job designation), andDT-001in Center code (the code for your downtown center). Leave Employee code blank if your organization uses auto-generated codes.
Two-phase import process
The import runs in two sequential phases to protect data integrity.
Phase 1 β Validation
After you upload the completed Excel file, the system validates every row, checking for:
- Employee code uniqueness (duplicate codes are flagged)
- Mandatory field completeness (first name, last name, gender, job code, center code)
- Valid center and job code references (codes must match existing records)
- Email format
- Phone format
The system displays validation results showing which rows passed and which rows contain errors. Error details include: row number, field name, error type (duplicate, missing, invalid format, or reference not found), and the offending value.
Phase 2 β Commit
After reviewing the validation results:
- Review the list of rows that passed validation and rows with errors.
- Fix any errors in your spreadsheet and re-upload if needed, or proceed with only the valid rows.
- Confirm the import to create employee records for all validated rows.
Rows that fail validation are not imported. The system creates records only for rows that passed all validation checks.
Job-level field import
Availability: Requires the Enable Job Level Employee Fields Import organization setting. Contact your administrator to enable this setting if it is not active.
When this setting is active, the import template includes additional columns for job-level default values:
- Commission rates
- Two-factor authentication settings
- Receipt override permission settings
- Discount limits
These values propagate from the job designation to new employee records when populated. When left empty, the system uses the job designation's configured defaults.
Export the employee list
You can export the filtered employee listing to an Excel file for offline review, reporting, or bulk data management.
- Navigate to Employee > Employees.
- Apply any desired filters to the employee listing to narrow the results.
- Click export.
The system generates an Excel file containing all visible columns, respecting your active filters.
Note: The export respects permission restrictions. Compensation columns are excluded if you do not have compensation view permissions. PII columns respect your organization's PII export restriction settings.
Export PII data
For data portability and compliance purposes, you can export all personally identifiable information stored for a specific employee.
- Navigate to the employee's profile.
- Select the PII export option from the employee profile.
The system generates a file containing all PII stored for the employee across all data stores, including: name, email, phone, address, employee code, employment details, and custom field values.
Note: If your access level is below the employee's configured PII limit, certain PII fields are redacted from the export. Contact your administrator if you require access to redacted fields.
What the exports do not include
The standard employee list export and the per-employee PII export together cover most employee data, but not all fields. The table below describes the known export boundaries.
| Data | Available how |
|---|---|
| Name, email, phone, address, employment details, custom field values | Standard list export and per-employee PII export |
| Commission rates, 2FA settings, discount limits | Standard list export (when columns are visible per your permissions) |
| Date of birth (DOB) | Not available in either self-serve export. DOB is not included in the standard list export or the PII export. Contact Zenoti Support if you need DOB data for compliance purposes. |
| Clinical dot-phrase templates | Not available via self-serve export. Contact Zenoti Support for assistance extracting this data. |
Note: If a field appears to be missing from an export, verify first that your role has the permission to view that field (compensation fields and some PII fields are hidden based on your access level). If the field is visible in the UI but absent from the export, it may be outside the scope of self-serve exports β contact Zenoti Support to request the data.
Tips
- Validate before committing. Always review the Phase 1 validation results carefully before confirming the import. Fixing errors in the spreadsheet and re-uploading is faster than correcting individual employee records after import.
- Use the downloaded template. Do not create your own spreadsheet from scratch. The system maps columns by header name, and custom spreadsheets with renamed or reordered headers cause import failures.
- Test with a small batch first. When importing a large number of employees, run a test import with 5β10 rows to confirm your job codes, center codes, and field formats are correct before uploading the full file.
- Keep job and center codes accurate. The most common import errors are invalid job code and center code references. Export your current job and center lists before preparing the import file to verify the exact codes in use.
- PII export for compliance. Use the PII export when responding to data subject access requests. The export captures all stored personal data across the employee's profile and custom fields in a single file.
Troubleshooting
Rows fail with "Invalid center / job reference" errors even though the codes look correct.
Verify that the codes in your spreadsheet exactly match the codes configured in Zenoti, including capitalization and spacing. Navigate to Employee > Jobs to confirm the exact job codes, and check your center configuration for the exact center codes. A single extra space or different casing causes a reference mismatch.
The import completes but some employees are missing from the listing.
These employees likely failed Phase 1 validation and were not committed. Review the validation error report that appeared after upload. Correct the flagged rows in your spreadsheet and re-run the import for those rows only.
The PII export file is missing some fields or shows redacted values.
Your account's PII access level may be below the employee's configured PII limit. Contact your administrator to review your PII access permissions or to run the export using an account with the appropriate access level.