Custom User Properties allow you to store additional information about users, such as membership details, preferences, or internal tracking fields.
If you are migrating from another system, the Optix Support team can help import user Custom Properties in bulk using a CSV file.
Before the import can be completed, admins must first create all Custom Properties inside the Optix dashboard.
Importing Custom User Properties allows your organization to:
• Preserve user data during migration from another platform
• Centralize important member information inside Optix
• Segment or manage users more easily using custom fields
• Maintain consistency across systems when importing historical data
• Reduce manual data entry when onboarding large user lists
How does the import process work?
How does the import process work?
Once your CSV file is ready:
Prepare the CSV file using the format described above.
Send the file to the Optix Support team.
The Support team reviews the file and checks formatting.
The import is performed after validation is completed.
If formatting issues are detected, the Support team will notify you before the import proceeds.
What must be set up before the import?
What must be set up before the import?
Navigate to:
Settings → User Settings → User Properties
Then, create all Custom Properties that will appear in the CSV file.
Make sure the following requirements are met:
Property labels must be finalized
Each column in the CSV must match the Property Label exactly. Changing the label after preparing the CSV may cause the import to fail.
Property types must be correct
Supported property types include:• Text
• Textarea
• Email
• Phone
• Number
• Date
• Select
• Multiple Select
Select and Multiple Select options must already exist
If a property uses Select or Multiple Select, all possible options must be created in advance. Values in the CSV must exactly match the option labels, including:• spelling
• capitalization
• spacing
If a value does not match an existing option, the import will fail.
What format should the CSV file follow?
What format should the CSV file follow?
Your CSV must contain one row per user.
The first column should typically be the user’s email address so the import can match data to the correct user record.
Each additional column header must exactly match the Custom Property Label in Optix.
Example structure
Email
App - Core Values
App - Event Preferences
App - Growth Goals
Formatting rules by property type
Text / Textarea
Values can be entered as plain text
Long-form answers should be placed inside a single cell
If a value contains commas, line breaks, or quotes, make sure the CSV is properly escaped when exported
Values must be valid email addresses
Phone
Values should be formatted consistently and contain valid phone data
Number
Values must be numeric
Date
Values should use a consistent date format
If possible, use standard datetime formatting such as YYYY-MM-DD HH:MM
Select
The value must exactly match one existing option in Optix
Multiple Select
Multiple values must be separated by commas
Do not add spaces after commas
Example:
Correct: Personal Growth Sessions,Retreats and Stay-Aways ✅
Incorrect: Personal Growth Sessions; Retreats and Stay-Aways ❌
Incorrect: Personal Growth Sessions, Retreats and Stay-Aways ❌
Note: Individual option labels must not contain commas.
Because commas are used as the separator between selected values, any option label that includes a comma may be split incorrectly during import.
Example:
Incorrect: Wellness Activities (Yoga, Breathwork, etc.)❌
Correct: Wellness Activities (Yoga / Breathwork)✅
If needed, update the option labels in the dashboard before preparing the CSV.
General CSV cleanup
Before sending the CSV to Optix, make sure the file has been cleaned up for common formatting issues.
This may include:
removing extra spaces around comma-separated values
removing pasted HTML or markup fragments such as <a class=...>
fixing character encoding issues or garbled text from exports
Example:
Incorrect: I don‚Äôt show up❌
Correct: I don't show up ✅
These issues commonly happen when CSV data is exported from another system or copied from formatted web content.
FAQs
FAQs
Can Optix create the Custom Properties for me during import?
No. All Custom Properties must already exist in the dashboard before Support can complete the import.
Do the CSV column names need to match the property labels exactly?
Yes. Column headers must match the Property Labels in Optix exactly.
Can Select or Multiple Select values be created automatically during import?
No. All Select and Multiple Select options must already exist in Optix before the import.
Can Multiple Select values include spaces after commas?
No. Multi-value properties must be comma-separated with no spaces after the comma.
Example:
Correct: Co-Working Sessions,Outdoor Adventures,Talks and Lectures
Incorrect: Co-Working Sessions, Outdoor Adventures, Talks and Lectures
Can a Multiple Select option contain a comma in its label?
No. Multiple Select option labels should not contain commas, because commas are used to separate values in the CSV.
What happens if one value in the CSV does not match an existing Select option?
The import may fail validation, and Support will ask for the CSV or property options to be corrected before proceeding.
Can Support help validate my file before importing it?
Yes. Support will review the file and flag formatting issues before the import is completed.
Download our demo CSV to see an example of the expected formatting for Custom User Property imports.