Import Contacts via CSV
Overview¶
This guide walks you through importing your contacts (People) into Grovana.
Before You Start¶
Prerequisites Checklist¶
Success
Your file is CSV, XLSX, or XLS format
Success
File has fewer than 10,000 records
Success
No duplicate email addresses in your file
Success
Companies imported first (if linking People to Companies)
Success
All custom fields exist in Settings → Data Model
Warning
Import Companies Before People
If you want to link People to Companies, import Companies first. The Company must exist before you can reference it.
Step 1: Prepare Your Contact Data¶
Required and Recommended Fields¶
| Field | Required? | Format | Notes |
|---|---|---|---|
| Recommended | [email protected] |
Must be unique | |
| First Name | Recommended | Text | |
| Last Name | Recommended | Text | |
| Company | Optional | Domain or ID | Links to existing Company |
| Phone | Optional | Multiple columns | See below |
| Job Title | Optional | Text | |
| Custom fields | Optional | Varies | Must exist in Data Model |
Email Format¶
- Must be valid email format:
[email protected] - Must be unique — no duplicates in your file or in Grovana
- For additional emails, use the Emails / Additional Emails column:
Phone Format¶
Phone is a nested field requiring multiple columns:
| Column | Example |
|---|---|
| Phones / Primary Phone Number | 4159095555 |
| Phones / Primary Phone Country Code | US |
| Phones / Primary Phone Calling Code | +1 |
Linking to Companies¶
Add a column with the Company's unique identifier:
| Column Name | Format | Example |
|---|---|---|
companyDomain |
URL format | https://acme.com |
companyId |
UUID | c776ee49-f608-4a77-8cc8-6fe96ae1e43f |
Note
Use Domain URL format (https://acme.com), not the label. This matches how Companies are stored in Grovana.
Sample CSV Structure¶
firstName,lastName,email,jobTitle,companyDomain,Phones / Primary Phone Number,Phones / Primary Phone Country Code
John,Smith,[email protected],CEO,https://acme.com,4159095555,US
Jane,Doe,[email protected],CTO,https://widgets.co,2125551234,US
Note
Pro tip: Click Download sample file during import or export a few existing People to see the exact column names Grovana expects.
Step 2: Access the Import Feature¶
Option 1: From the People View
- Navigate to People in the left sidebar
- Click the ⋮ icon on the top right
- Select Import records
Option 2: Using Command Menu
- Press
Cmd + K(Mac) orCtrl + K(Windows) - Type "import"
- Select Import records
- Choose People
Step 3: Upload Your File¶
- Click Select file
- Choose your CSV, XLSX, or XLS file
- Wait for Grovana to analyze your file
Step 4: Map Your Columns¶
Grovana automatically tries to match your columns to fields. Review and adjust:
- Check automatic mappings — verify they're correct
- Fix incorrect mappings — click the dropdown to select the right field
- Skip columns — select Do not map for columns you don't want to import
Important Mapping Rules¶
| Column Type | Map To | Notes |
|---|---|---|
| Company reference | Company relation field | Use domain OR id, not both |
| Primary email address | ||
| Additional emails | Emails / Additional Emails | Array format |
| Phone | Separate columns | Number, Country Code, Calling Code |
Mapping the Company Relation¶
When mapping the company column:
- Find your company reference column (e.g.,
companyDomain) - Map it to the Company relation field
- Grovana will link each Person to the matching Company
Warning
Map only ONE unique identifier for relations.
Don't map both companyId AND companyDomain. Choose one—preferably domain since it's human-readable.
Step 5: Map Select Field Values¶
If you have Select or Multi-Select fields (like Lead Source):
- Grovana shows your values alongside existing options
- Match each value in your file to a Grovana option
- Or create new options if needed
Note
Select options use API names, not display labels. Check Settings → Data Model → Enable Advanced mode to see API names.
Step 6: Review and Fix Errors¶
Before completing the import, Grovana validates your data:
- Click Next Steps
- Rows with errors are highlighted in yellow
- Fix errors directly — click a cell and edit the value
- Remove problematic rows — click the X to skip that row
Common Contact Import Errors¶
| Error | Cause | Solution |
|---|---|---|
| Duplicate email | Email already exists in Grovana or file | Remove duplicate or update existing record |
| Invalid email format | Email format incorrect | Fix to [email protected] |
| Relation not found | Company doesn't exist | Import Companies first or fix the reference |
| Missing required field | Required field is empty | Fill in the value or remove the row |
Step 7: Complete the Import¶
- Review the import summary
- Click Confirm to import
- Wait for the import to complete
- Verify by checking a few records and their Company links
After Importing Contacts¶
Your contacts are now in Grovana! Next steps:
- Verify Company links — open a few People records to confirm they're linked to the right Company
- Import Opportunities — if needed, link them to People and Companies
- Set up email sync — connect your mailbox to see email history on contact records
Updating Existing Contacts¶
To update contacts instead of creating new ones:
- Include the
emailoridcolumn in your file - Grovana matches records by this unique identifier
- Existing contacts are updated; new ones are created
See How to Update Existing Records for details.
FAQ¶
Why can't two People have the same email?
Email is a unique identifier in Grovana. This prevents duplicate contacts and ensures email sync correctly links emails to the right person.
What if I have people without an email?
You can leave the email empty. However, we recommend adding emails when possible for better data quality and email sync functionality.
How do I link People to Companies during import?
Add a column with the Company's domain (e.g., https://acme.com) or ID. During mapping, connect this column to the Company relation field.
What if the Company doesn't exist yet?
Import Companies first, then import People. The Company must exist before you can reference it.
Can I import the ID from my previous CRM?
Yes! Create a custom field marked as "unique" in your data model to store the external ID. Note: the field name id is reserved for Grovana's internal ID.
How do I fix 'relation not found' errors?
The Company you're referencing doesn't exist. Either import the Company first, or check that the domain/ID exactly matches an existing Company.
Troubleshooting¶
Having issues? Check: