If you want to import users into Devad Chat, the safest method is to start with an export from the same tenant first. That exported CSV already contains the correct column names, the correct custom-field labels, and the correct structure expected by the system.
This is the recommended workflow for tenant admins and support teams.
Where To Export Users
To download a user CSV on the test environment, open:
- https://up.chat.devad.io/?area=users
Then press the download/export button in the users area.
For production, use the same users page on your live domain:
- https://chat.devad.io/?area=users
Where To Import Users
To upload a CSV on the test environment, open:
- https://up.chat.devad.io/?setting=users
Then scroll to the end of the Settings page and use:
- Import users
- Import users from a CSV file
For production, use the same settings page on your live domain:
- https://chat.devad.io/?setting=users
Why You Should Export First
A manually created CSV can easily use the wrong column names, miss important fields, or assign the wrong user type. Exporting first avoids that problem.
The exported file includes the main system columns:
- ID
- First Name
- Last Name
- Profile Image
- Type
- Creation Time
It also includes:
- standard fields such as Birthdate, City, Company, Country, Language, Phone, and Website
- any custom fields created for that specific tenant
Because of that, the exported CSV should be treated as the official template for future imports.
If you are not sure which columns are supported, export users first and use that file to see the full list of fields available for your tenant.
Recommended Import Workflow
- Export users from the same tenant.
- Open that exported CSV and edit it instead of building a new file from scratch.
- Keep the first row as the header row.
- Keep custom-field names exactly as exported.
- Test with one or two rows first before importing a large file.
What Happens During Import
During import:
- one user is read per row
- blank rows are skipped
- ID and Creation Time are ignored
- custom fields are matched by the exported header name or the field slug
- duplicate email and duplicate phone rows are rejected
- the result popup shows imported, skipped, and failed counts
- the popup also shows warnings, row-level errors, and import guidance
Minimum Required Data
Each row should contain at least one useful identifier.
Recommended fields:
- First Name
- Last Name
- Phone
Allowed Type Values
CSV import allows only these user types:
- lead
- user
- visitor
Important:
- if Type is missing or empty, the imported row is now safely set to lead
- CSV import does not create admin, agent, or bot accounts
Example Without a Type Column
If the CSV does not include a Type column at all, the imported rows are treated as lead.
Final Recommendation
For the lowest risk:
- always export first
- keep the original headers
- include Type when possible
- if Type is not present, expect the row to become a lead