When getting started, sometimes it's easier to import your list of users or residents through a CSV import process.
👉 Navigate to the All People page and in the upper right select Import.
Download the provided CSV template for best results
Description of each column
Column Name | Description | Req? |
first_name | Resident's first name | Y |
last_name | Resident's last name | Y |
Resident's primary email | n | |
phone | User's Phone | n |
vlge_user_number | *auto-assigned by Vlge (import ignores) | n |
street_address | Property Street Address | n |
city | Property City | n |
state | Property State | n |
zip_code | Property Zip | n |
unit_number | If you use Unit numbers | n |
lot_number | If you use Lot numbers in addition to Addresses | n |
account_number | Vlge Acct Number OR enter your own | n |
mailing_street_address | Mailing address (optional if different) | n |
mailing_city | Mailing address (optional if different) | n |
mailing_state | Mailing address (optional if different) | n |
mailing_zip_code | Mailing address (optional if different) | n |
tags | Comma sep tag values - can create new ones | n |
is_owner | true/false - Can also be left blank and the system will set depending on unit relationship (below). | n |
move_in_date | optional move-in date | n |
notes | Any custom notes on the user | n |
unit_relationship | Accepts your custom display names or the system codes like "designated_contact" | n |
is_primary** | Sets the primary contact for a property when the row has a property or unit match. Person must be an owner (vs renter etc) | n |
*For vlge_user_number - If re-importing users for the purpose of updates, you can include this number for matching and the rows will be UPDATED with the new information.
** Regarding setting the primary contact in import
Requirements:
Row must match a property (street, lot, or account number)
Person must be an owner (
unit_relationship=ownerorowner_occupant)
Behavior:
Sets the gold star - same as clicking it on the All Properties page
Updates
Address.primaryUserIdandUnitOwnership.isPrimaryContacttogetherReplaces an existing primary on multi-owner units
Only one
is_primary=TRUErow per property per upload (conflicts are flagged as errors)Ignored for entity-owned properties (primary is managed on the entity)
Importing Unit Relationships
See Unit Relationships & Roles Articles for details on this feature
⭐️ May 2026: Now accepts Unit Relationships in Import
Accepts:
Machine keys —
owner_occupant,owner,renter,caretaker,guest,occupant,designated_contactOrg display names — e.g.
Tenantif you renamed Renter under Admin → Roles & PermissionsPlatform default labels — e.g.
Owner-OccupantLegacy aliases —
resident→ owner_occupant,tenant→ renter
In the case where the unit relationship value conflicts with "is_owner", Unit Relationship takes precedent.
Example: Relationship is set to "Owner" and is_owner is set to false. is_owner will be changed to true.
NOTE: If you EXPORT users first and see the "id" column included, it is NOT used for import matching on reimports.